Some javascript/style in this post has been disabled (
why?)
Hi Tom
The way we do it is to build the job periodically at night.
But before that, we change the job configuration (config.xml) to run the
extended tests and other stuff. After the nightly build, we change it back (or
rather, restore it from a backup). So the nightly build is part of the build
history of the job.
Probably (I don't use Ant with Hudson), you would have to
change the Ant targets with that preparation script.
Best regards,
Eric
Is there any way to to do the following?
I want a CI build triggered by changes in SCM that compiles the code then
runs a small set of smoke tests (of course this can all be done within the ant
target). However I'd like to use a second trigger on the same job to run once
overnight to do a promotion on a either a newly built or the last built job
based on a successful execution of the full regression suite. But I do not
want to run the full regression test suite (due to very long run times) on
every build.
It's important that we use the same build number counter for both CI and
nightly builds otherwise I'd just use separate jobs.
The dual trigger part works fine however I can't seem to determine the type
of trigger that caused the build. However, even if I knew that it seems that I
can't do a conditional promotion process based on a parameter to invoke the
ant target for the fuller regression test.
Any thoughts on alternatives to having two jobs with separate build
numbers?
Thanks! Tom
