Set up "my" workspace for personal builds.
Hello,
If I am a developer and I want to be able to use the personal builds, how do I need to set up my workspace, the "build user" role etc..?
I keep getting the error:
com.ibm.team.build.common.TeamBuildException: CRRTC3529E: The user, bm02, does not have read access to the workspace with the following UUID: _QbcDIFkxEeS16IOVPhIigg.
I set up my workspace to be public (Do I need to do that?)
What else?
Thanks
3 answers
Andrea, in the Collaborative Lifecycle Management messages information center on Jazz.net (https://jazz.net/help-dev/CLMErrorMessages/index.jsp), the user response for message CRRTC3529E (https://jazz.net/help-dev/CLMErrorMessages/topic/com.ibm.rational.rtc.messages.doc/CRRTC3529E.html) is to either update the user's permissions so that they can access the workspace, or change the permissions of the workspace to allow access to the user. Your user bm02 apparently have access to the workspace. Do the workspace permissions include bm02 as a user ID that can access the workspace?
Comments
The build user needs to be able to see the contents of your repository workspace, so the workspace must be public or scoped to a project area that contains the build user.
I suggest public, since your component permissions protect the files/folders contained in the workspace.
Comments
showing 5 of 6
show 1 more comments
Even though this is an old thread:
When submitting a personal build (with the "personal build" checkbox activated), user selects one of his own repository workspaces that satisfies the following one criterium:
That's it.
If you think you need to edit the build definition in order for this to work, you're mistaken.
How do I make sure the build user has read access:
- Visibility of my workspace is set to either public or project scoped (to a project area that the build user also is a member of).
Just in case anyone stumbles over this...
When submitting a personal build (with the "personal build" checkbox activated), user selects one of his own repository workspaces that satisfies the following one criterium:
- The build user needs read access to that workspace. In contrast to a "normal" build it won't accept any changes so it doesn't have to alter the content of the workspace and thus it doesn't have to be the owner of it.
That's it.
If you think you need to edit the build definition in order for this to work, you're mistaken.
How do I make sure the build user has read access:
- Visibility of my workspace is set to either public or project scoped (to a project area that the build user also is a member of).
Just in case anyone stumbles over this...
Comments
Evan Hughes
JAZZ DEVELOPER Nov 10 '14, 4:53 p.m.