Continuous Integration / Continuous Delivery (CI/CD) with Gitlab CI
Details
Continuous integration and continuous delivery are fundamental practices in modern software development. When implemented correctly, they can be all three things: better, faster, and cheaper.
Why better?
Let's assume that "better" means code quality. When you're integrating smaller changes faster, you're going to find bugs earlier. It's easier to revert a change if you need to, because it's smaller. When you're delivering your changes faster, you're able to incorporate feedback sooner. So you reduce the risk of delivering the wrong thing.
Why faster?
When you amass a collection of changes in an isolated environment (a bunch of code you haven't pushed to the server), any conflicts will take longer to deal with. Any bugs will be harder to find. And because CI leads toward CD (continuous delivery|deployment), your smaller changes can deliver value faster.
Why cheaper?
Code has value. There's a cost to changing an idea into working code. If you've developed code that's not in production, you've poured investment into something that's not providing any value. CI/CD allows you to minimize your carrying costs. And because you're incorporating feedback sooner, you'll get to the right thing faster and mitigate the cost of rework.
About the Teacher:
Aaron Brown is the VP of DevOps at Flowhub, Inc. He has more years experience in the tech industry than he wants to disclose. His career has evolved from systems administration/engineering to cloud infrastructure, processes, and automation for web-scale technologies.
Objectives:
- Build a light CI/CD framework
- Develop a general understanding of Gitlab CI
- Demonstrate CD capabilities with Gitlab Pages
Requirements:
- Laptop
- git
- Code/text editor
- Gitlab.com account
Price: $128 or PWYW
Continuous Integration / Continuous Delivery (CI/CD) with Gitlab CI