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

To Go Where No One Has Gone Before...

To Go Where No One Has Gone Before...

In 2015 we started to use GitLab-CE at STRABAG. After using OpenVZ containers since 2006 my team and I decided to move to Docker in 2017. We ran our first GitLab pipeline job in 2018 and now we are running more than 50k jobs per month.

With our first CI/CD run, we decided to fully commit ourselves to the GitOps philosophy and during the upcoming years, we hit a lot of obstacles. But, these experiences welded us together even more. By using GitLab we invented a lot of new tools but the most important thing was that we have built it up together, bottom-up, with us as individuals.

981461e0f9a0fb00cd5d5b762ce99c27?s=128

Mario Kleinsasser

August 10, 2020
Tweet

Transcript

  1. #GitLabCommit To Go Where No One Has Gone Before...

  2. #GitLabCommit A B O U T M E Mario Kleinsasser

    Team Leader / Solution Engineer @STRABAG BRVZ Source: Icons by Freepik (flaticon.com) @m4r10k gitlab.com/m4r10k linkedin.com/in/mario-kleinsasser
  3. #GitLabCommit Launch calendar

  4. #GitLabCommit #GitLabCommit T-3 years (2014) • GitLab since 2014 •

    GitLab for developers “Git” only • OpenVZ environment • Semi automatic deployments To Go Where No One Has Gone Before... Source: https://images.nasa.gov/details-6754387
  5. #GitLabCommit C O M I C Source: self made

  6. #GitLabCommit C O M I C Source: self made

  7. #GitLabCommit #GitLabCommit T-1 year (2016) • Start using Docker •

    Manual builds • Containers are nice… but… hard to tackle if you do it manually First transition Source: https://images.nasa.gov/details-MAF_19671005_S1C_ViewtoWest
  8. #GitLabCommit #GitLabCommit T-0 Ignition (2017) • TOGETHER, Dev and Ops!

    • 2017-04-28 08:04:48 (GMT) Lift off Source: https://images.nasa.gov/details-6864722
  9. #GitLabCommit #GitLabCommit T+1 second • First pipeline run - canceled

    • Next runs - canceled! • Run #9 - Successfully failed! • Run #14 - First success! Hmmmm… failures Source: https://www.nasa.gov/images/content/618280main_LAS_apolloaborttest.jpg
  10. #GitLabCommit P I P E L I N E S

    Source: self made
  11. #GitLabCommit #GitLabCommit T+3 months • More pipelines • More jobs

    • More projects • More of everything Faster, Further, Higher Source: Apollo 2, Apollo 3, Apollo 5, Apollo 6, Apollo 7 launch taken from Wikipedia NASA public domain
  12. #GitLabCommit Pipelines Jobs S T A T S Source: self

    made
  13. #GitLabCommit #GitLabCommit T+4 months • Houston we’ve a problem! •

    Going meta! • Care about the Doers! GitLab metagame Source: https://images.nasa.gov/details-s70-34986
  14. #GitLabCommit T R A N S I T I O

    N Source: self made
  15. #GitLabCommit #GitLabCommit T>4 months • Recreate everything • More backends

    • More Docker Swarm (true!) • More GitLab projects • More Load Balancers • GitLab includes (10.2018) Reboot from scratch Source: https://www.flickr.com/photos/spacex/40126460511/
  16. #GitLabCommit #GitLabCommit T>2 years • GitOps! • For us the

    only way • Hundreds of projects • Different knowledge • Different software stacks GitOps Source: https://www.youtube.com/watch?v=bvim4rsNHkQ
  17. #GitLabCommit #GitLabCommit T>2 years • Kanban board • Talk with

    each other • Listen to and learn from other people Structure work Source: https://www.youtube.com/watch?v=bvim4rsNHkQ Source: self made
  18. #GitLabCommit N O W 2 0 2 0 Source: self

    made
  19. #GitLabCommit #GitLabCommit Now! (2020) • Thank you team! Impossible without

    the people Source: Self made image collage
  20. #GitLabCommit Thank You! @m4r10k YOU(!) Can Go Where No One

    Has Gone Before! Attempt To Automate Wherever It’s Appropriate! Source: Icons by Freepik (flaticon.com)