Publishing only some builds

View: New views
5 Messages — Rating Filter:   Alert me  

Publishing only some builds

by Scott Goldstein-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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:

 

  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

 

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

Re: Publishing only some builds

by Michael Kloss-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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

Re: Publishing only some builds

by Nelz :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am going to throw my own little bit in here, too...  Hopefully this
doesn't confuse the issue.

When I was setting up Nightly builds in addition to the "continuous"
builds (e.g. triggered by a check-in), I found it helpful to have two
entirely separate projects between the two.

I did this because I wanted the Nightly report to show any changes
that had been made since the LAST nightly had been run, not just since
the last CONTINUOUS build.  This meant having two separate clientspecs
(we use Perforce) so I could get the distinct reports.

Hope that helps!

- nelz

On 12/24/06, Michael Kloss <cc@...> wrote:

> 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
>


--
"Protect your digital freedom and privacy, eliminate DRM, learn more
at http://www.defectivebydesign.org/what_is_drm"

-------------------------------------------------------------------------
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

Re: Publishing only some builds

by kv :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Please let me know your suggestions how to setup the ccnet.config for thses two operations inorder to perform the subversion builds.
Thanks
Nelson Carpentier wrote:
I am going to throw my own little bit in here, too...  Hopefully this
doesn't confuse the issue.

When I was setting up Nightly builds in addition to the "continuous"
builds (e.g. triggered by a check-in), I found it helpful to have two
entirely separate projects between the two.

I did this because I wanted the Nightly report to show any changes
that had been made since the LAST nightly had been run, not just since
the last CONTINUOUS build.  This meant having two separate clientspecs
(we use Perforce) so I could get the distinct reports.

Hope that helps!

- nelz

On 12/24/06, Michael Kloss <cc@clau-mich.de> wrote:
> 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>


--
"Protect your digital freedom and privacy, eliminate DRM, learn more
at http://www.defectivebydesign.org/what_is_drm"

-------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user

Re: Publishing only some builds

by Jeffrey Fredrick-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This is the mailing list for the Java version of CruiseControl.  For
CC.Net questions you'll need to try their mailing list:

http://confluence.public.thoughtworks.org/display/CCNET/Mailing+Lists

Jtf

On 1/12/07, kv <vkrishnasamy@...> wrote:

>
> Please let me know your suggestions how to setup the ccnet.config for thses
> two operations inorder to perform the subversion builds.
> Thanks
>
> Nelson Carpentier wrote:
> >
> > I am going to throw my own little bit in here, too...  Hopefully this
> > doesn't confuse the issue.
> >
> > When I was setting up Nightly builds in addition to the "continuous"
> > builds (e.g. triggered by a check-in), I found it helpful to have two
> > entirely separate projects between the two.
> >
> > I did this because I wanted the Nightly report to show any changes
> > that had been made since the LAST nightly had been run, not just since
> > the last CONTINUOUS build.  This meant having two separate clientspecs
> > (we use Perforce) so I could get the distinct reports.
> >
> > Hope that helps!
> >
> > - nelz
> >
> > On 12/24/06, Michael Kloss <cc@...> wrote:
> >> 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
> >>
> >
> >
> > --
> > "Protect your digital freedom and privacy, eliminate DRM, learn more
> > at http://www.defectivebydesign.org/what_is_drm"
> >
> > -------------------------------------------------------------------------
> > 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
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Publishing-only-some-builds-tf2876361.html#a8305224
> Sent from the CruiseControl - User mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> 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
>


--

http://www.developertesting.com/

-------------------------------------------------------------------------
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