
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
I want to be able to configure Cruise Control to do the
following:
- Run CI build during the day and
e-mail results to developers
- At a specific time in the
evening, stop all CI builds and run a nightly build. E-mail the
results to developers and management. Publish the build artifacts to
a file server
- When necessary, on demand be
able to follow the same procedure of the nightly build at some time during
the day
I’d like to be able to do this for several branches of
our source tree.
What is the best way of going about this? If I want different
publishing semantics for the CI and nightly builds, do I need to create two
different projects? If not, how would I achieve the desired publishing
semantics? Also, how do I go about stopping the CI build to start the
nightly build? And, on a related note, if I want to have a nightly build
for two different braches, how do I set it up so all CI builds are stopped and
then the two branches are built in succession?
Thank you for your help!
Scott
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Cruisecontrol-user mailing list
Cruisecontrol-user@...
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user