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

From git to forge

Embed Size (px)

Citation preview

Page 1: From git to forge

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

Page 2: From git to forge

sgtpepper @ irc.freenode.net

Page 3: From git to forge
Page 4: From git to forge

Disclaimer:

or: http://www.urbandictionary.com/define.php?term=Opinionated

In Short: No Pupet logo, no Puppet opinion

Page 5: From git to forge

Why do you write software?

FUN PROFIT

TO ANNOY PEOPLE

Page 6: From git to forge

Who maintains your code?

Page 7: From git to forge

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

Page 8: From git to forge
Page 9: From git to forge
Page 10: From git to forge
Page 11: From git to forge

When do I test ?

Master

Feature Branch PR

Page 12: From git to forge

What does Travis do:

Page 13: From git to forge

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

Page 14: From git to forge
Page 15: From git to forge
Page 16: From git to forge
Page 17: From git to forge

Too lazy to do it yourself?

Page 18: From git to forge