continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Vanbiervliet" <>
Subject Re: continuum scheduled "forced" build
Date Wed, 22 Feb 2006 09:10:56 GMT
I've just seen that there was an open issue about this...
Anyway, your suggestions are welcome :-)

On 2/22/06, Matthew Vanbiervliet <> wrote:
> Hi,
> Is there a way to force Continuum to build a project even if there are no
> changes in the source repository ?
> What I try to achieve is to have Continuum build a snapshot using a
> different profile every night, even if there were no changes. I have two
> schedules attached to the project :
> - The default one which runs every hour
> - A second one that runs at 1 AM every night.
> Now the problem is that, when I commit changes, let's say at 7:35 PM, the
> scheduled build at 8 pm will detect these changes and perform a build.
> At 1 AM, a cvs update is run, but no changes are detected since there
> weren't any new commits since 7:35 PM...
> I'd like to have this specific build, build a snapshot and deploy it on
> our private repository, so that we always have a latest snapshot deployed
> every day (and an up to date doc).
> To be able to achieve this, the second schedule should start a "forced"
> build...(using a argument ? )
> A workaround would be to have the project twice in continuum, one copy
> with the default schedule and one copy with the second schedule, but i'd
> prefere to avoid this overhead...It still has an advantage though : if no
> changes were made at all one day, then there wouldn't be an unnecessary
> deployment the next night.
> Do you see how I can do that ? Or any better suggestion ?
> Thanks for your help
> --
> Matthew Vanbiervliet
> Accelior Consulting

Matthew Vanbiervliet
Accelior Consulting

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message