[
http://jira.codehaus.org/browse/CONTINUUM-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169066#action_169066
]
Wendy Smoak commented on CONTINUUM-2043:
----------------------------------------
I think that's going to raise an issue similar to the one on the Queues page --
if a person doesn't have permission to see a project group, then NO
information about that group can be exposed.
I currently have a couple of "private" continuum instances for this reason. If
consolidating them to a single master in order to use distributed build means
that other users will be able to see that the private projects exist, I won't
be able to do it.
I think on the Queues page the decision was to mask the name of the project and
just show "Other".
If it can't be secured, then it probably needs to be visible only to the System
Administrator role (or some new role that only admin has by default.)
> 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
