Re: Publishing only some builds

> Hi Scott,
>
> many questions, so I try to keep them in order:
>
> >
> >    1. Run CI build during the day and e-mail results to developers
> >    2. 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
> >    3. When necessary, on demand be able to follow the same procedure
> >       of the nightly build at some time during the day
> >
> this is really no big deal. You can configure one project as time-build
> and all others with a <pause> at that time. BTW if you run with one
> thread only no other builds will take place during your nightlybuild.
> >
> > What is the best way of going about this?
> >
> see above.
> >
> >   If I want different publishing semantics for the CI and nightly
> > builds, do I need to create two different projects?
> >
> Depends on your differences. If you do not have different publishers or
> email-recipients, you can just run another target or start another
> build-script in the same project. If you have differences in the config,
> I would configure two projects on the same workingcopy.
> >
> > Also, how do I go about stopping the CI build to start the nightly build?
> >
> On multiple threads, use the <pause>-configuration (see
> http://cruisecontrol.sourceforge.net/main/configxml.html#pause)
>
> So, hope this helps a bit
>
> Cheers,
> Michael
>
>
> -------------------------------------------------------------------------
> 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
>