Puppet users - Dec 2008 - Puppet Continuous Integration - your help needed

Hi all

We''re implementing a Hudson Continuous Integration server for Puppet
and
Facter.  The CI server will monitor the current development repositories
- currently 0.24.x and master.  When new commits are detected it will
run the unit and rspec tests on build slaves.

Why all this?

Well as Puppet and Facter are cross-platform tools a lot of bugs and
issues we encounter are because a change has unexpected consequences on
a particular platform.  This diversity of platforms also means the
development team can''t test sufficiently broadly.  By having
tests run on many platforms we hope to quickly identify and correct any
cross-platform bugs before they get into a release.

So why Hudson and what does it do?

Hudson monitors executions of repeated jobs, such as building a software
project or jobs run by cron. Among those things, current Hudson focuses
on building/testing software projects continuously, just like
CruiseControl or DamageControl. In a nutshell, Hudson provides an
easy-to-use so-called continuous integration system, making it easier
for developers to integrate changes to the project, and making it easier
for users to obtain a fresh build. The automated, continuous build
increases the productivity.

So what are build slaves?

Build slaves are installations of particular operating systems and
versions on which we want to run our tests after committing.

So what do you need in order to submit a slave?

See http://reductivelabs.com/trac/puppet/wiki/PuppetContinuousIntegration

So what slaves do we need?

This is a short list of the slaves we''d like (and multiple slaves of
differing versions across a platform are also welcome).  But if you''re
running Puppet on a platform and are you able to contribute a build
slave for that platform we''d very much appreciate it.

OSX
HP-UX
AIX
NetBSD
OpenBSD
FreeBSD
Gentoo
Ubuntu
SuSE
Red Hat
CentOS
Solaris - Open and Solaris 8/9/10

So if you are able to provide a slave - email me the required details.
Fleshing out the documentation on the wiki for your specific platform
would also be most welcome.

Thanks

James Turnbull

-- 
Author of:
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com
To unsubscribe from this group, send email to
puppet-dev+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

James Turnbull wrote:
> Hi all
> 
> We''re implementing a Hudson Continuous Integration server for
Puppet and
> Facter.  The CI server will monitor the current development repositories
> - currently 0.24.x and master.  When new commits are detected it will
> run the unit and rspec tests on build slaves.
> 
> Why all this?
> 
> Well as Puppet and Facter are cross-platform tools a lot of bugs and
> issues we encounter are because a change has unexpected consequences on
> a particular platform.  This diversity of platforms also means the
> development team can''t test sufficiently broadly.  By having
> tests run on many platforms we hope to quickly identify and correct any
> cross-platform bugs before they get into a release.
> 
> So why Hudson and what does it do?
> 
> Hudson monitors executions of repeated jobs, such as building a software
> project or jobs run by cron. Among those things, current Hudson focuses
> on building/testing software projects continuously, just like
> CruiseControl or DamageControl. In a nutshell, Hudson provides an
> easy-to-use so-called continuous integration system, making it easier
> for developers to integrate changes to the project, and making it easier
> for users to obtain a fresh build. The automated, continuous build
> increases the productivity.
> 
> So what are build slaves?
> 
> Build slaves are installations of particular operating systems and
> versions on which we want to run our tests after committing.
> 
> So what do you need in order to submit a slave?
> 
> See http://reductivelabs.com/trac/puppet/wiki/PuppetContinuousIntegration
> 
> So what slaves do we need?
> 
> This is a short list of the slaves we''d like (and multiple slaves
of
> differing versions across a platform are also welcome).  But if
you''re
> running Puppet on a platform and are you able to contribute a build
> slave for that platform we''d very much appreciate it.
> 
> OSX
> HP-UX
> AIX
> NetBSD
> OpenBSD
> FreeBSD
> Gentoo
> Ubuntu
> SuSE
> Red Hat
> CentOS
> Solaris - Open and Solaris 8/9/10
> 
> So if you are able to provide a slave - email me the required details.
> Fleshing out the documentation on the wiki for your specific platform
> would also be most welcome.
> 
I may be able to provide a slave for FreeBSD if there aren''t any
objections on my side.

Mike? Joe?

-- 
Russell A. Jackson <raj@csub.edu>
Network Analyst
California State University, Bakersfield

The difference between America and England is, the English think 100
miles is a long distance and the Americans think 100 years is a long time.

I can provide a CentOS 3,4, and 5.

-L

On Dec 5, 8:20 pm, Russell Jackson <r...@csub.edu>
wrote:
> James Turnbull wrote:
> > Hi all
>
> > We''re implementing a Hudson Continuous Integration server for
Puppet and
> > Facter.  The CI server will monitor the current development
repositories
> > - currently 0.24.x and master.  When new commits are detected it will
> > run the unit and rspec tests on build slaves.
>
> > Why all this?
>
> > Well as Puppet and Facter are cross-platform tools a lot of bugs and
> > issues we encounter are because a change has unexpected consequences
on
> > a particular platform.  This diversity of platforms also means the
> > development team can''t test sufficiently broadly.  By having
> > tests run on many platforms we hope to quickly identify and correct
any
> > cross-platform bugs before they get into a release.
>
> > So why Hudson and what does it do?
>
> > Hudson monitors executions of repeated jobs, such as building a
software
> > project or jobs run by cron. Among those things, current Hudson
focuses
> > on building/testing software projects continuously, just like
> > CruiseControl or DamageControl. In a nutshell, Hudson provides an
> > easy-to-use so-called continuous integration system, making it easier
> > for developers to integrate changes to the project, and making it
easier
> > for users to obtain a fresh build. The automated, continuous build
> > increases the productivity.
>
> > So what are build slaves?
>
> > Build slaves are installations of particular operating systems and
> > versions on which we want to run our tests after committing.
>
> > So what do you need in order to submit a slave?
>
> >
Seehttp://reductivelabs.com/trac/puppet/wiki/PuppetContinuousIntegration
>
> > So what slaves do we need?
>
> > This is a short list of the slaves we''d like (and multiple
slaves of
> > differing versions across a platform are also welcome).  But if
you''re
> > running Puppet on a platform and are you able to contribute a build
> > slave for that platform we''d very much appreciate it.
>
> > OSX
> > HP-UX
> > AIX
> > NetBSD
> > OpenBSD
> > FreeBSD
> > Gentoo
> > Ubuntu
> > SuSE
> > Red Hat
> > CentOS
> > Solaris - Open and Solaris 8/9/10
>
> > So if you are able to provide a slave - email me the required details.
> > Fleshing out the documentation on the wiki for your specific platform
> > would also be most welcome.
>
> I may be able to provide a slave for FreeBSD if there aren''t any
objections on my side.
>
> Mike? Joe?
>
> --
> Russell A. Jackson <r...@csub.edu>
> Network Analyst
> California State University, Bakersfield
>
> The difference between America and England is, the English think 100
> miles is a long distance and the Americans think 100 years is a long time.
>
>  signature.asc
> < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi James,

My team at DISA and the Forge.mil project is looking to setup a
Puppet/Hudson/Cobbler driven setup for our CI. I was hoping you may
have some pointers you would be willing to share.

Thanks,

Aaron

On Mon, Dec 1, 2008 at 10:19 PM, James Turnbull <james@lovedthanlost.net>
wrote:
>
> Hi all
>
> We''re implementing a Hudson Continuous Integration server for
Puppet and
> Facter.  The CI server will monitor the current development repositories
> - currently 0.24.x and master.  When new commits are detected it will
> run the unit and rspec tests on build slaves.
>
> Why all this?
>
> Well as Puppet and Facter are cross-platform tools a lot of bugs and
> issues we encounter are because a change has unexpected consequences on
> a particular platform.  This diversity of platforms also means the
> development team can''t test sufficiently broadly.  By having
> tests run on many platforms we hope to quickly identify and correct any
> cross-platform bugs before they get into a release.
>
> So why Hudson and what does it do?
>
> Hudson monitors executions of repeated jobs, such as building a software
> project or jobs run by cron. Among those things, current Hudson focuses
> on building/testing software projects continuously, just like
> CruiseControl or DamageControl. In a nutshell, Hudson provides an
> easy-to-use so-called continuous integration system, making it easier
> for developers to integrate changes to the project, and making it easier
> for users to obtain a fresh build. The automated, continuous build
> increases the productivity.
>
> So what are build slaves?
>
> Build slaves are installations of particular operating systems and
> versions on which we want to run our tests after committing.
>
> So what do you need in order to submit a slave?
>
> See http://reductivelabs.com/trac/puppet/wiki/PuppetContinuousIntegration
>
> So what slaves do we need?
>
> This is a short list of the slaves we''d like (and multiple slaves
of
> differing versions across a platform are also welcome).  But if
you''re
> running Puppet on a platform and are you able to contribute a build
> slave for that platform we''d very much appreciate it.
>
> OSX
> HP-UX
> AIX
> NetBSD
> OpenBSD
> FreeBSD
> Gentoo
> Ubuntu
> SuSE
> Red Hat
> CentOS
> Solaris - Open and Solaris 8/9/10
>
> So if you are able to provide a slave - email me the required details.
> Fleshing out the documentation on the wiki for your specific platform
> would also be most welcome.
>
> Thanks
>
> James Turnbull
>
> --
> Author of:
> * Pulling Strings with Puppet
> (http://www.amazon.com/gp/product/1590599780/)
> * Pro Nagios 2.0
> (http://www.amazon.com/gp/product/1590596099/)
> * Hardening Linux
> (http://www.amazon.com/gp/product/1590594444/)
>
>
>
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13/02/10 11:28 AM, Aaron Lippold wrote:
> Hi James,
> 
> My team at DISA and the Forge.mil project is looking to setup a
> Puppet/Hudson/Cobbler driven setup for our CI. I was hoping you may
> have some pointers you would be willing to share.
> 
Hi - sure can - depends on what you need to know.  So feel free to
email me queries off-list.

I have also been meaning to put together some proper notes and a
modules for the Hudson set-up.  Teyo may already have done some of
this but if he hasn''t I''ll bump it up the priority list. :)

Regards

James

- -- 
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS3ZHMCFa/lDkFHAyAQIh6ggAqCxNylBH785SnCXe4n+iEJi5AKl3X0Lv
z47HZW0YIsCcE46bPTp77VrhAaLFgLM/ewNUIGVNbnE/UoDPIKyrpLSYIGof3pt7
Vibgdzy2rzSwvCkXxBzSeVNWD4x0GI9qSBURpuTuq+6YjAKlTbXwIV+8ULh8RjYW
IyKBtbvEEOyVGNYpO7BBgOwPQeJZvSIahwUpeyKGEHJztJv5sst2naACR9Y/wLws
T93KGkVyBMhgrO7NzNifT7BCR+efVCjViD3OCcq8887IY1w1JvG4Ee40rPdFOJqG
O1eeiJc9Ccx8WVj0PeWv5268PZErHzaVAXhzSydLsHMtLlAFR4Wt2w==wA2d
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.