Marica Tan wrote:
On Wed, Feb 10, 2010 at 6:50 AM, Wendy Smoak <[email protected]> wrote:
On Tue, Feb 9, 2010 at 3:39 PM, Marica Tan <[email protected]> wrote:
In non-distributed build, not selecting a build environment means it
will use the "default" environment, whatever Continuum is running in.
That doesn't seem to make sense in a distributed environment, since
nothing builds on the master where you are pressing the buttons.
Therefore, I think selection of a build environment should be
mandatory in distributed builds.
Any arguments to the contrary?
[This decision will have effects on the scheduled/forced build
features as well as configuration and UI.]
+1
We should create another issue for making it mandatory in distributed builds
and document this too.
+1
for making the build environment selection mandatory and for documentation
Marica Tan wrote:
On Wed, Feb 10, 2010 at 12:19 AM, Wendy Smoak <[email protected]> wrote:
That is, if I select a build environment for the release, I would be
unpleasantly surprised to have Continuum decide to use an agent that
is not part of that build env. (not included in the agent group
assigned to that build env.)
It should prefer the last-used agent *if* it is in the build env, to
save time by not having to do another checkout.
How does the 'selected agent' get selected from the agent group?
(This may be documented elsewhere as it's probably the same as for
scheduled builds.)
+1
I think the selection should go like this:
1. last-used agent
2. agent with the least build load.
wiki updated.
The definition of the default build agent as the one that was last
used to build the project doesn't work if we accept that a previous
successful build is not necessary to do a release. (But I see that's
under future enhancements, so okay.)
If we implement this, we could just add a check if there's a previous build
and if none then do a checkout in the selected build agent, which is the
agent with the least build load. And I think this could work on both
with/without selected build environment.
This is added in the "Future Enhancements". IMHO, this should be
discussed separately since it concerns a different feature of Continuum.
And, this might affect some other features.
--
Thanks,
Jev
