Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Portable Pipelines

Portable Pipelines

Avoid vendor lock-in with this pragmatic approach to CICD pipelines (spoiler alerts, it's bash)

mongrelion

March 21, 2019
Tweet

More Decks by mongrelion

Other Decks in Programming

Transcript

  1. @mongrelion - carlosleon.info Carlos León - @mongrelion Strategic Consultant All

    Things Cloud Native, DevOps, Programmable Infrastructure, Automation and Hang Gliding <3
  2. @mongrelion - carlosleon.info Agenda 1 CICD: The Basics 2 The

    Status Quo 3 CICD Tooling 4 Example 5 Portability 6 Q&A
  3. @mongrelion - carlosleon.info The Good • Predictable • Reproducible •

    Visibility • Accountability • Less error prone
  4. @mongrelion - carlosleon.info • Community support • Commercial support •

    Extensions/plugins ecosystem • Well known The Good
  5. @mongrelion - carlosleon.info The Good • Community support • Commercial

    support • Extensions/plugins ecosystem • Well known • Battle tested
  6. @mongrelion - carlosleon.info • Eager for resources • Hard to

    automate • Stateful to the bone The Bad
  7. @mongrelion - carlosleon.info The Bad • Eager for resources •

    Hard to automate • Stateful to the bone • Extensions/plugin ecosystem
  8. @mongrelion - carlosleon.info Issues with this approach • Lots of

    manual steps • Changes are not visible • No track
  9. @mongrelion - carlosleon.info Issues with this approach • Lots of

    manual steps • Changes are not visible • No track • No responsibility
  10. @mongrelion - carlosleon.info Issues with this approach • Lots of

    manual steps • Changes are not visible • No track • No responsibility • Long feedback loops
  11. @mongrelion - carlosleon.info Cons • Hard to bootstrap • Time

    to learn bash • Hard to reuse community components