A call to action to avoid orphaned code! With great power comes great responsibility and uploading modules to the Puppet Forge means that other community members will depend on you. This talk will show an opinionated workflow using free tools and examples so you can make your Puppet modules better and more open to collaboration!.

1. From git push to the Puppet Forge.
An opinionated CI Pipeline.

2. sgtpepper @ irc.freenode.net

4. Disclaimer:
or: http://www.urbandictionary.com/define.php?term=Opinionated
In Short: No Pupet logo, no Puppet opinion

5. Why do you write software?
FUN PROFIT
TO ANNOY
PEOPLE

6. Who maintains your code?

7. Caveats vs. “It’s your own fault”
- Don’t need to release (as in no
new functionality was added)
- The product hasn’t changed
- Stability
- Forking
- Ignoring PR’s
- Orphaned
- Code unreleased in Version Control
- Don’t need to maintain it anymore
- Don’t want to maintain it anymore
- Don’t care

11. When do I test ?
Master
Feature Branch PR

12. What does Travis do:

13. What does Travis do:
• Syntax tests: Your code makes sense
• puppet parser validate
• ruby -c
• yaml
• Linting: Your code is readable
• Puppet
• Metadata
• Unit Tests: Your code meets the requirements
• rspec

17. Too lazy to do it yourself?