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
: 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
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: 99.
But this is not foolproof. Is there an option I can set?
--
Thanks and
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 [EMAIL PROTECTED] wrote:
Hi Continuum
Hi - Can somebody please help me a bit?
Thanks,
Anoop
On 9/11/06, Anoop kumar V [EMAIL PROTECTED] 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.
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
I don't think this feature is available currently.
On 9/12/06, Anoop kumar V [EMAIL PROTECTED] wrote:
Hi - Can somebody please help me a bit?
Thanks,
Anoop
On 9/11/06, Anoop kumar V [EMAIL PROTECTED] wrote:
Actually - the other way I have tried (not sure if it works yet) is to
just disable
