Skip to content

pipeline_working.md

Latest commit

 

History

History
81 lines (51 loc) · 3.96 KB

pipeline_working.md

File metadata and controls

81 lines (51 loc) · 3.96 KB
copyright
years
2015, 2026
lastupdated 2026-05-08
keywords IBM Cloud, build types, build jobs, deployment job, build script, create pipeline,
subcollection ContinuousDelivery

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

Working with pipelines

{: #pipeline-working}

{{site.data.keyword.contdelivery_short}} will be discontinued in the following regions on 12 February 2027: au-syd, ca-mon, ca-tor, us-east. Code Risk Analyzer and {{site.data.keyword.DRA_short}} will also be deprecated in all regions on that date. However, if a region has no active usage of these features, the features in that region may be discontinued earlier and stop accepting new instances. Learn more {: important}

To automate your builds and deployments to {{site.data.keyword.cloud}}, use {{site.data.keyword.contdelivery_full}} pipelines. {: shortdesc}

With pipelines, you can choose from several build types. You provide the build script, and {{site.data.keyword.contdelivery_short}} runs it; you don't need to set up build systems. Then, with one click, you can automatically deploy your app to one or many {{site.data.keyword.cloud_notm}} spaces or Docker containers on the {{site.data.keyword.containerlong}}.

Build jobs compile and package your app source code from Git repositories. The build jobs produce deployable artifacts, such as WAR files or Docker containers for the {{site.data.keyword.containerlong_notm}}. In addition, you can run unit tests within your build automatically. You can set up your build jobs so that each time a commit is pushed, a build is triggered.

A deployment job takes output from a build job and deploys it to the {{site.data.keyword.containerlong_notm}}.

You can deploy to one or many regions and services. For example, you can set up your {{site.data.keyword.deliverypipeline}} to use one or more services, test in one region, and deploy to production in multiple regions.

Creating a pipeline

{: #creating-pipeline}

You can use any of the following methods to create a pipeline:

From your {{site.data.keyword.deliverypipeline}}, change your configuration; check the status of builds, the deployed app, and recent deployments; see the most recent logs and deployment details; or delete your pipeline.

Viewing a pipeline by using the CLI

{: #viewing-pipeline-cli}

To get the details that are required to invoke a pipeline, run the **ibmcloud dev toolchains** command to view the name of the toolchain. If you already know the name of the toolchain, run the **ibmcloud dev toolchain-get [toolchain-name]** to view the toolchain details.

  • To get the details of a pipeline and its stages, identify the pipeline and its ID to run the following command:

    ibmcloud dev pipeline-get [pipelineID]

    {: codeblock}

  • Using the pipeline ID from the previous command, you can now run the pipeline:

    ibmcloud dev pipeline-run [pipelineID]

    {: codeblock}

    This command invokes an execution of the stage and its jobs. A successful execution results in the job execution for each job in the selected stage.

Viewing pipeline logs by using the CLI

{: #viewing-pipeline-logs-cli}

You can view detailed output of each stage during a pipeline's execution.

  • To view the logs from a pipeline's execution, run the following command:

    ibmcloud dev pipeline-log [pipelineID]

    {: codeblock}

  • To filter the logs by stage, apply the previous command and add the stage ID:

    ibmcloud dev pipeline-log [pipelineID] --stage-id [stageID]

    {: codeblock}