You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2006/03/24 18:59:11 UTC
[jira] Closed: (CONTINUUM-636) Multiple build definitions pr
project makes no sense
[ http://jira.codehaus.org/browse/CONTINUUM-636?page=all ]
Emmanuel Venisse closed CONTINUUM-636:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.3
You can now assign several build definition to a project and scm activity will be found from last execution of current build definition and not an other.
> Multiple build definitions pr project makes no sense
> ----------------------------------------------------
>
> Key: CONTINUUM-636
> URL: http://jira.codehaus.org/browse/CONTINUUM-636
> Project: Continuum
> Type: Improvement
> Reporter: Jarl Petter Kvalsvik
> Assignee: Emmanuel Venisse
> Fix For: 1.0.3
>
>
> In my Continuum setup I want to run contiluous builds during daytime and once every night I want to also create extensive reports.
> It is a problem that if I create several build definitions these share SCM state and thus will prevent each other from running.
> In my scenario the daytime build will run fine, but since there is no SCM activity between the last daytime build and the nightly build, the nightly build will be skipped (becaus no SCM changes are detected).
> I would have preferred that unique "project numbers" are assigned to a build definition to prevent sharing of SCM state.
--
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