You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sharmarke Aden (JIRA)" <ji...@codehaus.org> on 2006/06/30 20:59:40 UTC

[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.

    [ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_68720 ] 

Sharmarke Aden commented on CONTINUUM-509:
------------------------------------------

The priority of this issue shouldn't be "minor" as it is an essential feature of a Continuous Integration Systems. I'd like to fix this bug and would appreciate it if anyone give me a hint as to what components I need to look at to resolve the bug. 

Thanks. 

> Ability to process scheduled builds the same as forced builds.
> --------------------------------------------------------------
>
>          Key: CONTINUUM-509
>          URL: http://jira.codehaus.org/browse/CONTINUUM-509
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>     Reporter: Shinobu Kawai
>     Priority: Minor
>      Fix For: 1.1

>
>
> It would be great if you could configure a build schedule to act like a forced build on the scheduled build.
> The use case for this is when you have two build definitions:
> - One will be set to default for a forced, light build.  For example, install the artifact.
> - Another will be set to a scheduled, heavy build.  For example, deploy the artifact and the project site.
> If the default build is triggered, the other build will be skipped since nothing has been updated since the forced build.  And we do not want to do heavy stuff in the default build.

-- 
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