Continuum

Build environment selection is ignored when releasing with distributed build enabled

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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.

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-2458 Continuum Release should do a checkout if there is no working copy

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-2464 Build environment should be required when releasing in distributed build setup

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-2043 Release should happen on a build agent rather than on the master

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

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

Show
Wendy Smoak added a comment - 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
Hide
Permalink
Jevica Arianne B. Zurbano added a comment -

Fixed in r928598.

  • added check if last used build agent in building is in group to be used for release
  • added method to get the last build agent used in building
  • added unit tests
  • updated documentation
Show
Jevica Arianne B. Zurbano added a comment - Fixed in r928598. added check if last used build agent in building is in group to be used for release added method to get the last build agent used in building added unit tests updated documentation

People

  • Assignee:
    Jevica Arianne B. Zurbano
    Reporter:
    Wendy Smoak
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: