Yelken Docs

Appearance

Pipeline ​

A Pipeline defines a set of dependent tasks that are executed in an order until either all of them succeed or a failure happens. Depending on the pipeline's definition, it expects some arguments to pass to its tasks such as commit hash while building your project.

Most of the time, a Workflow creates the pipeline according to its own definition when a triggering event happens. You may also create a pipeline from a workflow inside its details page by specifying necessary arguments.

To view the pipelines of a project:

  • Open a project by choosing it in Projects page,
  • Use hammer icon at the top right corner to open the dropdown which shows running pipelines,
  • Additionally, use Show All Pipelines link to view all the pipelines.

When you use the Show All Pipelines page, you will be navigated to Pipelines page where you can list the project's pipelines. By choosing a pipeline from the list, you can view its details such as commit info if it is a GitHub pipeline. You can also inspect the logs of running task such as build logs.

Concurrency ​

To prevent excessive resource consumption, Yelken limits number of concurrently executed pipelines to 1 per project. If there is already a running pipeline, any pipeline that is created in the project will be queued and wait until the running pipeline gets completed.

States ​

A pipeline or its tasks can be in one of these states:

  • Pending: A pipeline starts its life in this state. If there is no running or queued pipeline in the project, it should quickly turn into Running state.
  • Running: Indicates that pipeline started executing its task.
  • Success: Pipeline has been completed successfully.
  • Failed: Pipeline has failed for some reason. For more information, please look at the logs inside the pipeline's details page.

GitHub Pipelines ​

The pipelines created by GitHub Workflow have 2 tasks:

  1. Build: Main job of Build Task is to clone the GitHub repository at a commit specified by workflow and build a container image from the Dockerfile.
  2. Deploy: After building a container image, Deploy Task creates a new deployment with the image and updates the service specified by the workflow.

INFO

Since build task needs compute resources, it is run as container on Yeklen infrastructure with the smallest plan g-0.125c-256m. Only duration of build task is considered while calculating the cost of the pipeline. For more information about plan's price, please look at Pricing page.

Unfortunately, it is not possible to use a higher plan for more compute resources. Though, it is planned to let user specify the plan for the pipeline in the future.