(1) a compile test is good, really good. make sure cheap tests happen first
(and fail fast) before expensive ones.
(2) I have a strong bias for having the automated jobs just run bundle
exec rake test or something like that, so that you can use the same job
for multiple modules
On Thu, Aug 7,
Pre-commit hooks are great but Github and github enterprise won't enforce
them(arbitrary code on the server is uncool for some reason), so if you
want to be 100% and use either they still need to be run as part of your
jenkins build task.
On Aug 6, 2014 7:11 PM, John Warburton jwarbur...@gmail.com
I'm setting up a jenkins server to perform continuous integration on my
puppet codebase, and I'm interested in running at least the following tests:
- puppet parser validate
- puppet lint
- rspec-puppet
- test-kitchen
Have I overlooked any other worthwhile tests, and has the
Also check to see that your templates compile and that ruby can read all your
yaml files without erroring?
We just have the checks which we run intermittently, currently there's no
snazzy integration beyond jenkins failing a run and us getting a sad email, and
I have other priorities right
I've started to use beaker instead of test-kitchen, especially with docker
instances.
This should let me test specific roles/profiles for functionality rather
than just syntax correctness.
On Wed, Aug 6, 2014 at 10:00 AM, Christopher Wood
christopher_w...@pobox.com wrote:
Also check to see
On 7 August 2014 02:17, Bernard Clark berniecla...@gmail.com wrote:
I'm setting up a jenkins server to perform continuous integration on my
puppet codebase, and I'm interested in running at least the following tests:
- puppet parser validate
- puppet lint
These are cheap to do. Give
