continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LECAN Damien" <Damien.LE...@B2i.fr>
Subject RE: How to set: No Scheduled build | Only triggered build
Date Tue, 12 Sep 2006 07:37:50 GMT
Create a disabled schedule ! (uncheck "enable")
Call it "No schedule", and project won't be build anymore.


Damien

> -----Message d'origine-----
> De : Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Envoyé : mardi 12 septembre 2006 09:27
> À : continuum-users@maven.apache.org
> Objet : Re: How to set: No Scheduled build | Only triggered build
> 
> 
> If you set the year of the schedule to something in the 
> future like 2050, the schedule won't be 
> executed.
> 
> Emmanuel
> 
> Anoop kumar V a écrit :
> > Ohh really....??
> > 
> > I have this issue - we have a dev env and a test env. The 
> DEV is more or
> > less like an integration environment for all developers. 
> The TEST env is
> > where we finally push code for testing by a separate testing team
> > 
> > We have set these 2 envs as 2 different projects in 
> Continuum. The latest
> > from CVS is picked up and a build is made for each.
> > 
> > But if a release is going on, and the test team is testing 
> a release (ON
> > TEST), we wouldnt want to build / deploy into TEST (and 
> mess up the env) -
> > but it is ok if a build happens on DEV. So we all agreed 
> (TEST and DEV
> > teams) that we will henceforth use Continuum to do only 'on 
> demand' builds
> > (only if triggered by the user)....and there would be no 
> scheduled builds.
> > 
> > How can I work around this issue? One way as I have 
> mentioned below is to
> > specify a very large quiet period....
> > The other option maybe is to maintain a branch in CVS which 
> will be used
> > only for TEST, and merge from HEAD into this BRANCH just 
> when we want to
> > build / deploy into stuff..
> > 
> > Is there some other easier way that I might not have 
> thought about? (like
> > maybe I can tweak the cron intervals to ensure that a build 
> never happens??
> > Our testing cycle never goes beyond a week!)
> > 
> > Thanks a lot,
> > Anoop
> > 
> > On 9/12/06, Barrie Treloar <baerrach@gmail.com> wrote:
> >>
> >> I don't think this feature is available currently.
> >>
> >> On 9/12/06, Anoop kumar V <anoopkumarv@gmail.com> wrote:
> >> > Hi - Can somebody please help me a bit?
> >> >
> >> > Thanks,
> >> > Anoop
> >> >
> >> > On 9/11/06, Anoop kumar V <anoopkumarv@gmail.com> wrote:
> >> > >
> >> > > Actually - the other way I have tried (not sure if it 
> works yet) 
> >> is to
> >> > > just disable all the schedules that I have. So that 
> would only let a
> >> user
> >> > > click on the build-now link to build. Otherwise a 
> build would never
> >> happen.
> >> > >
> >> > > -Anoop
> >> > >
> >> > > On 9/11/06, Anoop kumar V <anoopkumarv@gmail.com> wrote:
> >> > > >
> >> > > > Hi Continuum users,
> >> > > >
> >> > > > What is the best way to set the build schedule as 
> never. Only 
> >> when a
> >> > > > user triggers, should the build happen??
> >> > > >
> >> > > > As of now, I have created a new schedule with the 
> quiet period as a
> >> very
> >> > > > large time: 999999.
> >> > > >
> >> > > > But this is not foolproof. Is there an option I can set?
> >> > > >
> >> > > > --
> >> > > > Thanks and best regards,
> >> > > > Anoop
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Thanks and best regards,
> >> > > Anoop
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Thanks and best regards,
> >> > Anoop
> >> >
> >> >
> >>
> > 
> > 
> > 
> 
> 

Mime
View raw message