5 - v2.0.x Pipeline Documentation

Note: This section describes the pipeline feature as implemented in Rancher v2.0.x. If you are using Rancher v2.1 or later, where pipelines have been significantly improved, please refer to the new documentation for v2.1 or later.

Pipelines help you automate the software delivery process. You can integrate Rancher with GitHub to create a pipeline.

You can set up your pipeline to run a series of stages and steps to test your code and deploy it.

• Pipelines
• Contain a series of stages and steps. Out-of-the-box, the pipelines feature supports fan out and in capabilities.
• Stages
• Executed sequentially. The next stage will not execute until all of the steps within the stage execute.
• Steps
• Are executed in parallel within a stage.

Enabling CI Pipelines

• Select cluster from drop down.

• Under tools menu select pipelines.

• Follow instructions for setting up github auth on page.

Creating CI Pipelines

• Go to the project you want this pipeline to run in.

• Select workloads from the top level Nav bar

• Select pipelines from the secondary Nav bar

• Click Add pipeline button.

• Enter in your repository name (Autocomplete should help zero in on it quickly).

• Select Branch options.

  • Only the branch {BRANCH NAME}: Only events triggered by changes to this branch will be built.

  • Evertyhing but {BRANCH NAME}: Build any branch that triggered an event EXCEPT events from this branch.

  • All branches: Regardless of the branch that triggered the event always build.

Note: If you want one path for master, but another for PRs or development/test/feature branches, create two separate pipelines.

• Select the build trigger events. By default, builds will only happen by manually clicking build now in Rancher UI.

  • Automatically build this pipeline whenever there is a git commit. (This respects the branch selection above)

  • Automatically build this pipeline whenever there is a new PR.

  • Automatically build the pipeline. (Allows you to configure scheduled builds similar to Cron)

• Click Add button.

By default, Rancher provides a three stage pipeline for you. It consists of a build stage where you would compile, unit test, and scan code. The publish stage has a single step to publish a docker image.

• Add a name to the pipeline in order to complete adding a pipeline.

• Click on the ‘run a script’ box under the ‘Build’ stage.

Here you can set the image, or select from pre-packaged envs.

• Configure a shell script to run inside the container when building.

• Click Save to persist the changes.

• Click the “publish an image’ box under the “Publish” stage.

• Set the location of the Dockerfile. By default it looks in the root of the workspace. Instead, set the build context for building the image relative to the root of the workspace.

• Set the image information.

The registry is the remote registry URL. It is defaulted to Docker hub.Repository is the <org>/<repo> in the repository.

• Select the Tag. You can hard code a tag like ‘latest’ or select from a list of available variables.

• If this is the first time using this registry, you can add the username/password for pushing the image. You must click save for the registry credentials AND also save for the modal.

Creating a New Stage

• To add a new stage the user must click the ‘add a new stage’ link in either create or edit mode of the pipeline view.

• Provide a name for the stage.

• Click save.

Creating a New Step

• Go to create / edit mode of the pipeline.

• Click “Add Step” button in the stage that you would like to add a step in.

• Fill out the form as detailed above

Environment Variables

For your convenience the following environment variables are available in your build steps: