These workshop labs demonstrate how to effectively use CI/CD practices, manage feature flags, and orchestrating releases with CloudBees' Core, Rollout, and Flow products.
- Internet access to include access to https://github.com and to include the ability to access and use the GitHub File Editor.
- Access to https://app.slack.com
- An account on https://github.com and a basic understanding of how to use GitHub to do things like fork a repository, edit files in the web UI, and create pull requests.
- A basic understanding of Docker: https://docs.docker.com/get-started/
- A basic understanding of Kubernetes: https://kubernetes.io/docs/tutorials/kubernetes-basics/
- A basic understanding of Jenkins Pipelines: https://jenkins.io/doc/book/pipeline/getting-started/
- A basic understanding of feature flags: https://rollout.io/blog/ultimate-feature-flag-guide/
- Finally, we highly recommend using the Google Chrome browser to work through the lab content.
Workshop Setup for all workshops
https://cloudbees-days.github.io/core-rollout-flow-workshop/core/
- Lab 1 - Core Workshop Setup
- Lab 2 - Configuration as Code (CasC) for CloudBees Core
- Lab 3 - Pipeline Template Catalogs
- Lab 4 - Pipeline Policies
- Lab 5 - Cross Team Collaboration
- Lab 6 - Hibernating Masters
NOTE: If you are returning to the workshop cluster to complete a lab please review this lab on Un-hibernating a Master.
https://cloudbees-days.github.io/core-rollout-flow-workshop/rollout/
If you did not attend the Core Workshop or go through the above labs, please follow these instructions before proceeding to Lab 1 below.
- Lab 1 - Rollout Workshop Setup
- Lab 2 - Gating Code with CloudBees Feature Flags
- Lab 3 - Controlling the Value of a Feature Flag
- Lab 4 - User Targeting
- Lab 5 - Rollout Configuration as Code
- Lab 6 - CloudBees Rollout and Analytics
Coming soon...
- Lab 1 - Create release pipeline from a service catalog
- Lab 2 - Add gates to the release pipeline
- Lab 3 - Merge into master and run through release pipeline
- Lab 4 - Check out the live app, close the ticket, observe flow Dashboard