Skip to content

Latest commit

 

History

History
83 lines (47 loc) · 7.26 KB

cicd.md

File metadata and controls

83 lines (47 loc) · 7.26 KB
Raw
copyright lastupdated keywords subcollection
years
2014, 2023
2023-08-17
openshift, continuous integration and delivery
openshift

{{site.data.keyword.attribute-definition-list}}

Setting up continuous integration and delivery

{: #cicd}

With {{site.data.keyword.cloud_notm}} and other open source tools, you can set up continuous integration and delivery (CI/CD), version control, tool chains, and more to help automate app development and deployment. {: shortdesc}

Continuous integration (CI) can help you detect errors early, ensure early system integration, and improve collaboration in your development process. Continuous delivery (CD) is a practice by which you build and deploy your software so that it can be released into production at any time. By automating your continuous integration and delivery processes through setting up CI/CD pipelines, you can achieve repeatability in code releases and greater predictability in delivery schedules.

Adopt a DevOps approach by using {{site.data.keyword.deliverypipelinelong}}, which includes open toolchains that automate the building and deployment of containerized apps.

Before you begin, make sure that you have at least the following permissions in {{site.data.keyword.cloud_notm}} IAM:

  • Editor platform access role and Writer service access role to the Kubernetes Service cluster. For more information, see User access permissions.
  • Viewer platform access role to the resource group of the cluster where you want to create the toolchain.
  • Editor platform access role to the Toolchain service (note that this service is separate than Continuous Delivery).

To add a continuous delivery pipeline to your cluster,

  1. From the {{site.data.keyword.redhat_openshift_notm}} clusters console{: external}, select the cluster for which you want to set up a continuous delivery pipeline.
  2. Select the DevOps tab.
  3. Click Create a toolchain.
  4. Review the available toolchains. IBM provides pre-defined toolchains that you can use to deploy, test, and monitor Kubernetes-native apps or Helm charts. You can expand each toolchain to find an overview of the tools that are set up for you and to find the scripts in GitHub that are used to configure the toolchain in your cluster. For more information about each toolchain, see Toolchain templates. If you know what tools you want to use, you can create your own toolchain.
  5. Select the toolchain that you want to use and click Create.
  6. Follow the directions in the console to configure your toolchain. Make sure to include the name of your cluster in your toolchain name so that you can easily find the toolchain that is associated with your cluster later. For more information, see Creating toolchains.
  7. Select Delivery Pipeline to review the stages of your continuous integration and continuous delivery pipeline. After you create your toolchain, your pipeline is automatically kicked off and runs through the stages that you configured. Make sure that your stages run successfully and correct any errors.
  8. Modify your toolchain. You can add more tools to your toolchain or change the stages of your delivery pipeline.
    1. From the {{site.data.keyword.redhat_openshift_notm}} clusters console{: external}, select the cluster for which you want to set up a continuous delivery pipeline.
    2. Select the DevOps tab.
    3. Select the toolchain that you want to modify.

For a deep dive into the benefits and specifics of automating continuous integration and delivery, check out Automate continuous integration{: external} and Build and deploy by using continuous delivery{: external} in the IBM Garage Methodology documentation. {: tip}

Other resources

{: #cicd-other}

To automate your CI/CD pipeline, check out the following integrations and tools.

Codeship : You can use Codeship{: external} for the continuous integration and delivery of containers. For more information, see Using Codeship Pro To Deploy Workloads to {{site.data.keyword.containerlong_notm}}{: external}.

Grafeas : Grafeas{: external} is an open source CI/CD service that provides a common way for how to retrieve, store, and exchange metadata during the software supply chain process. For example, if you integrate Grafeas into your app build process, Grafeas can store information about the initiator of the build request, vulnerability scan results, and quality assurance sign-off so that you can make an informed decision if an app can be deployed to production. You can use this metadata in audits or to prove compliance for your software supply chain.

{{site.data.keyword.deliverypipelinelong}} : With your app configuration files organized in a source control management system such as Git, you can build your pipeline to test and deploy code to different environments, such as test and prod. {{site.data.keyword.contdelivery_full}} allows you to automate your app builds and container deployments to Kubernetes clusters by using a toolchain. You can also check out this tutorial on Continuous Deployment to Kubernetes.

Razee : Razee{: external} is an open-source project that automates and manages the deployment of Kubernetes resources across clusters, environments, and cloud providers, and helps you to visualize deployment information for your resources so that you can monitor the rollout process and find deployment issues more quickly. For more information about Razee and how to set up Razee in your cluster to automate your deployment process, see the Razee documentation{: external}.

Kustomize : Use the Kubernetes project Kustomize{: external} to package your apps by both standardizing and customizing your deployments across multiple environments. Kustomize helps you write, customize, and reuse your Kubernetes resource YAML configurations. To get started, see Packaging apps for reuse in multiple environments with Kustomize.

Operators : With operators, you can manage the lifecycle of the apps in your cluster, including third-party software and services that you integrate into your cluster from the OperatorHub{: external}. You can consistently install, update, and monitor system components by using operators or by making operators available to developers that work in specific projects or across projects. To set up operators, see Using Operators in version 4 clusters.