Extending the process to prevent delivering to a stream
![]()
I've been playing around with the Eclipse Way process and I've created a new role called 'support contributor'. What I would like to do is prevent these members of the team from being able to deliver code to a stream, or rather, they can deliver but only in one of the following circumstances:
1. Delivery is deferred until the work item is approved or 2. Temporarily change their role to be a contributor for the duration of the delivery. Is there anyway of doing this? I've played around without success so far -- Richard |
2 answers
![]()
The version of the 'eclipse way' that comes out of the box is open. Most
permissions are granted to the 'default' role, i.e. everybody who can log into your repository. In order to restrict delivery to 'contributor' (and roles other than 'default') you need to remove the permission for the server side scm deliver operation ('com.ibm.team.scm.server.deliver') from the 'default' role and grant it to 'contributor' (and all other roles that should have this right). If you then want to enforce a review for one particular role you can add the 'changes reviewed' precondition ('com.ibm.team.scm.service.advisors.changesReviewed') to the server side scm deliver operation for that role. We are thinking about providing a more sophisticated version of the precondition that would allow to express which kinds of approvals are needed, how many of them, and by which roles they need to be completed. Kai Jazz Process Team richard.daviesr wrote: I've been playing around with the Eclipse Way process and I've created |
![]()
Thanks for that, it's answered my questions.
The process in general is certainly a lot easier to edit when using the experimental team process editor (windows -> preferences -> team process -> Experimental) I still had to resort to a hand-edit of the XML to add the precondition, I've not tested it yet but the comment here is that the documentation just isn't good enough for this job. I've ended up with this, and it seems to work fine (obviously you wouldn't blanket ban scm.server.deliver for this role if you are doing approvals instead), I'm posting this so others can see what you need to do, this has gone inside the behaviour tag of the team configuration: <role id="support contributor"> Regarding your comment: Yes, I think you do need a bit more formality here to match enterprise change&control management tools. Many thanks, -- Richard |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.