continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-2548) SCM changes per build definition
Date Fri, 06 Aug 2010 06:29:33 GMT


Brett Porter updated CONTINUUM-2548:

    Fix Version/s: 1.4.2 (Beta)

> SCM changes per build definition
> --------------------------------
>                 Key: CONTINUUM-2548
>                 URL:
>             Project: Continuum
>          Issue Type: Improvement
>          Components: SCM
>    Affects Versions: 1.3.6
>            Reporter: Nicolas Garin
>             Fix For: 1.4.2 (Beta)
> Hi All,
> Today, when a project gets two (or more) build definition like theses:
> 1/ Default build - scheduler HOURLY_SCHEDULE - no fresh build - set as default
> 2/ Site and/or Q/A build - scheduler NIGHTLY_SCHEDULE - no fresh build
> > the first build def. is run every hour if a scm change is found since its last build
(last hour)
> > the second build def. is run every night if a scm change is found since its last
build (last night)
> During day, scm changes appears normally in every hour build results: for each build,
we can see respective scm changes.
> Problems appear at night:
> All scm changes appearing previously on hourly builds have moved to the nightly build
result; no more scm change appear on build results of the day before.
> A workaround is to flag "build fresh" to "true" for the nightly build def. Thus, no scm
change will be detected. But, as "build fresh" implies "always build", a nightly build is
run even without scm change.
> Could it be possible to have scm changes per build definition or is there another workaround
> Regards,
> Nicolas

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message