[
http://jira.codehaus.org/browse/CONTINUUM-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169013#action_169013
]
Maria Catherine Tan commented on CONTINUUM-2043:
------------------------------------------------
1. Source code is no longer checked out from the master
2. Release will happen in the build agent where the last build of the project
was performed.
3. Can release concurrently
4. Clicking the releases button will show all releases that are happening.
- all users will be able to view the list of releases
- you need to have a build permission for that group to be able to view a
particular release
I don't think it's possible to add a security restriction for a certain
resource in the Releases button because it's in the Menu side, but I can add a
new role 'continuum-view-releases' for the project developers only. Still,
project developers who don't belong in the group can still see the list of
releases.
> Release should happen on a build agent rather than on the master
> ----------------------------------------------------------------
>
> Key: CONTINUUM-2043
> URL: http://jira.codehaus.org/browse/CONTINUUM-2043
> Project: Continuum
> Issue Type: Improvement
> Components: Distributed Builds
> Affects Versions: 1.3.1
> Reporter: Wendy Smoak
> Assignee: Maria Catherine Tan
> Fix For: 1.3.2
>
>
> When the distributed builds feature is enabled, releases should happen on a
> build agent instead of the master.
> Will need to reverse the change made for CONTINUUM-2035 which checks out code
> on the master.
> Related to CONTINUUM-2042, Ability to control which build agent a project
> builds on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
