*tl;dr* what is the officially endorsed way to leverage beaker to run tests
against PE (sp. 2016/7.x) in a CI type of setup?
I've beaten my head against beaker-{pe,rspec} etc. enough that I assume
others may be running into similar problems or guesswork, so bear with me:
Thus far I've been able to leverage beaker/beaker-rspec and so on to run
continuous integration against modules across a wide variety of
distributions (and distribution versions). Previously this has worked
equally well with Puppet Enterprise, but as 2016.x and now 2017.x come down
the pipe, the reliability of the beaker suite of CI tooling has begun to
falter.
Based upon my reading of some of the beaker-pe retooling, there's a greater
degree of support for later versions of PE, but concrete examples are
somewhat lacking: for example, are there nodeset yaml file somewhere that
show a valid PE node to test against? I suspect that there's a valid
commercial reason for not simply fetching PE tarballs given that it seems
pe_dir needs to point to a PE tarball the user has acquired ostensibly
through official channels, but where does that leave module developers' CI
pipelines?
I'm hopeful that I might have simply overlooked a good example in a
third-party module somewhere and the beaker(-pe) docs may just be lacking
some documentation for how to repeatably perform acceptance tests against
the 201x suite of PE versions. I would assume that everyone involved here
(both module developers and Puppet Labs, Inc.) would benefit by the ability
to test modules against Enterprise in a reproducible manner.
(Forgive me if my first post here seems to be complaining, beaker and
beaker-rspec have made my life *so* much easier, so thank you!)
Cheers,
Tyler
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f452d732-88b4-4317-b75f-1c25b2d2b7a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
