I think the reasons why it needs to have a previous successful build are: 1. to make sure there is a working copy 2. to make sure we have a successful build before we tag. there is no sense to release a project if the build failed because the release will fail as well.
Thanks, - Marica On Wed, Feb 3, 2010 at 9:14 AM, Wendy Smoak <[email protected]> wrote: > I had a long conversation with myself about this on the drive home, > and I keep going in circles. I don't know how much of the existing > behavior is intentional vs. incidental. > > In non-distributed build, it will not let you do a release unless the > projects are in 'build success' state. Obviously, the release happens > on that working copy. > > Carrying that over to distributed build, you still have to have a > previous successful build. IF the release has to happen on that > working copy, then you don't get to pick the build agent. And since > the build agent is part of the build environment... > > So, can someone explain why you have to have a previous successful > build in order to do a release? It's not a requirement at the maven > command line. The release might fail, but you are not prevented from > trying it. > > Is this a real requirement, or can we go with Brett's idea that > Continuum Release should do a checkout, which would mean it could > happen anywhere? > > Honestly I think this work should be delayed until the architecture > changes are sorted out. It shouldn't be this complicated. > > -- > Wendy >
