[
http://jira.codehaus.org/browse/CONTINUUM-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak updated CONTINUUM-2306:
-----------------------------------
Fix Version/s: Reviewed
I agree, it should not be possible to release if the project is being built,
and starting a release should disable any scheduled builds.
The release is a two step process so you might end up with scheduled builds
being disabled if the user doesn't *finish* the release (or if it fails.)
I think the release process should be simplified to one step though-- there's
probably already a feature request for that, or at least we discussed it on irc
once.
> Continuum starts scheduled build definition on a releasing project
> ------------------------------------------------------------------
>
> Key: CONTINUUM-2306
> URL: http://jira.codehaus.org/browse/CONTINUUM-2306
> Project: Continuum
> Issue Type: Bug
> Components: Release
> Affects Versions: 1.2.3
> Reporter: Yanke
> Fix For: Reviewed
>
>
> Continuum is configured to hourly (cron is "0 0 * * * ?") run mvn clean
> install for all my projects
> I manually started a release for project AVZ @ 04:00:10 PM (see "Release
> Result row" below)
> At 4 o'clock countinuum started to build all my projects and @ 04:00:27 it
> started building the AVZ project I was versioning (see "Build results for
> avz" below)
> Since both Maven runs work on the same working-directory, they conflicts and
> the release fails.
> Possible solutions:
> 1. Continuum should not start a scheduled build when a project is being
> versioned.
> 2. The mvn release:prepare is executed in an different directory
> {panel:title=Release Result row}
> avz prepare Jul 22, 2009 04:00:10 PM CEST Jul 22, 2009 04:02:04 PM CEST ERROR
> View Result
> {panel}
> {panel:title=Build results for avz }
> 511 Jul 22, 2009 04:00:27 PM CEST Jul 22, 2009 04:02:41 PM CEST Duration : 2
> min 14 sec Default Maven 2 Build Definition Result
> {panel}
--
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
