Set up "my" workspace for personal builds.
3 answers
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
Could you also please point me to documentation that can help me set this up? I did set it as public but I am still having permissions problem as I pointed out above. It seems that the only thing that works would be to give ownership of 'my' work space to the build manager account. I can't do that as then I lose my workspace
Thanks
Quite disappointing to hear that. This is a well listed functionality but there is no documentation support on how to set it up. What are we supposed to do to take advantage of this functionality?
Hi Evan,
Andrea, you don't lose your workspace, you can search and find it again.
you should be able to make it public, or create a team area where you AND the build user share access.
I know we had to do this on one of our projects to enable personal build.
I looked around the doc on the actual steps, but they all just show checking the box, and selecting the personal workspace. None discuss the access rights requirements
I'm not aware of internal docs on running personal builds. The public documentation is all there is.
Comments
I believe the correct link for the 3429E error is https://jazz.net/help-dev/CLMErrorMessages/index.jsp?topic=%2Fcom.ibm.rational.rtc.messages.doc%2FCRRTC3529E.html
>>update the build user's permissions so they can load the workspace
With the workspace set to public and the build user able to see it, you should be able to run a personal build.
You could try logging in as the build user and loading the workspace to see if any problems arise.
Comments
Evan Hughes
JAZZ DEVELOPER Nov 10 '14, 4:53 p.m.