Pipelines Introduction

Last updated
Tags クラウド Server v3.x

This page provides information on CircleCI pipelines, how they are triggered, and what they include. For further information on pipeline processing, and the features available within your pipelines, refer to the Pipeline Processing doc.


CircleCI pipelines are the highest-level unit of work, encompassing a project’s full .circleci/config.yml file. Pipelines include your workflows, which coordinate your jobs. They have a fixed, linear lifecycle, and are associated with a specific actor. Pipelines trigger when a change is pushed to a project that has a CircleCI configuration file included, and can also be scheduled, triggered manually through the CircleCI app, or using the API.

Pipelines are not available on installations of CircleCI server v2.x.

When visiting your CircleCI dashboard, you are shown a list of recently triggered pipelines for your organization/account.

Screenshot of the pipelines dashboard in the CircleCI app

Triggering a pipeline

Pipelines can be triggered in several ways. Each method is described below.

Trigger a pipeline on push to your code repository

Each time a commit is pushed to one of your projects, on a branch that has a .circleci/config.yml file included, a pipeline is triggered.

Trigger a pipeline from the CircleCI app

In the CircleCI app, when you have a specific branch selected, the Trigger Pipeline button becomes enabled. Click Trigger Pipeline, choose if you want to specify any pipeline parameters, and click Trigger Pipeline again.

Trigger a pipeline using the API

You can trigger a pipeline for a project using the Trigger a New Pipeline endpoint.

Pipeline architecture

パイプラインはワークフローで構成され、ワークフローはジョブで構成されます。 パイプライン中のいずれかのジョブに移動すると、ジョブ出力、テスト結果、アーティファクトに各タブからアクセスできます。

Further, the output of each job can be opened in a new tab (in either raw or formatted styling) with a unique link, making it share-able between team members.


このガイドは、CircleCI の他のドキュメントと同様にオープンソースで、GitHub で使用できます。 ご協力いただき、ありがとうございます。