Continuous Integration Lecture
Continuous Integration, Delivery, and Deployment are important devOps practices and we often hear a lot about them. These processes are valuable and ensures that the software is up to date timely.
- Continuous Integration is an automation process which allows developers to integrate their work into a repository. When a developer pushes his work into the source code repository, it ensures that the software continues to work properly. It helps to enable collaborative development across the teams and also helps to identify the integration bugs sooner.
- Continuous Delivery comes after Continuous Integration. It prepares the code for release. It automates the steps that are needed to deploy a build.
- Continuous Deployment is the final step which succeeds Continuous Delivery. It automatically deploys the code whenever a code change is done. Entire process of deployment is automated.
The continuous integration activities focus around Tekton the integration platform. These labs will show you how to build pipelines and test your code before deployment.
These tasks assume that you have:
- Reviewed the continuous integration concept page.
- Installed Tekton into your cluster.
|Deploying Applications From Source||Using OpenShift 4||S2I||30 min|
|Try It Yourself|
|Tekton Lab||Using Tekton to build container images||Tekton||1 hour|
|IBM Cloud DevOps||Using IBM Cloud ToolChain with Tekton||Tekton on IBM Cloud||1 hour|
|Jenkins Lab||Using Jenkins to build and deploy applications.||Jenkins||1 hour|
Once you have completed these tasks, you will have an understanding of continuous integration and how to use Tekton to build a pipeline.