[
http://jira.codehaus.org/browse/CONTINUUM-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208950#action_208950
]
Wendy Smoak commented on CONTINUUM-2386:
----------------------------------------
Thinking about this further, I don't think just disabling the Build Environment
selection will work.
The release will fail if the last-used build agent is not available anymore.
And I would like to control the Build Environment at release time, just as I
can for a scheduled build.
See also dev@ discussion:
http://old.nabble.com/Thoughts-on-build-environment-selection-when-releasing-in-distributed-build-setup-td27399430.html
> Build environment selection is ignored when releasing with distributed build
> enabled
> ------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2386
> URL: http://jira.codehaus.org/browse/CONTINUUM-2386
> Project: Continuum
> Issue Type: Bug
> Components: Distributed Builds, Release
> Affects Versions: 1.3.4
> Reporter: Wendy Smoak
> Assignee: Jevica Arianne B. Zurbano
> Fix For: Backlog
>
>
> To reproduce,
> 1. configure distributed builds and agents
> 2. force a build which is successful
> 3. release the project and select a Build Environment with a different agent
> than was used to build the project before
> I would expect that the Build Environment selection is used with whatever
> Installations and Build Agent Group is configured.
> The actual behavior is that it goes the the last agent that was used to build
> the project.
> Reading the comments on CONTINUUM-2043, this is apparently correct, but the
> UI does not match the behavior.
> I suppose the Build Environment selection needs to be disabled and the
> documentation clarified to explain this.
--
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
