In this guide, a pipeline refers to two things:
- A Continuous Integration (CI) pipeline
- A Jenkins pipeline
A CI pipeline is the sequence of steps in a CI flow. An example CI pipeline consists of running some unit tests, and verifying that they pass every time they merge code to version control. Your CI pipeline is to build the software, test the software, then merge the software in version control. A Jenkins pipeline is a suite of different plug-ins that enable Jenkins to script CI pipelines. In this guide, you can assume that the term pipeline refers to a CI pipeline, unless we refer to these Jenkins plugins.
Jenkinsfile defines each step in
the pipeline, and can be managed and tracked in source control, just like any
other code. This enables you to use CI best practices with the CI pipeline
configuration file itself. Blue Ocean provides a GUI interface to edit the
pipeline code and the
Follow these steps to create a pipeline:
- Click on Open Blue Ocean on the left of the Jenkins GUI.
Navigate to the New Pipeline button, if you do not see a prompt to create a new pipeline. The New Pipeline button will be in the top right, as shown in this screenshot:
- Select your source control repository. We recommend SSH, which works well with both Jenkins and git. When you enter your repository URL, Jenkins will generate a public SSH key, which you can include in your own git server.
- Select Create Pipeline to open a new screen, which is the Jenkins Blue Ocean Pipeline editor.
Depending on whether you are using Docker to run the Fast Models, or running locally on Linux, you will configure slightly different Jenkins pipelines. Both steps and outputs are detailed in Set up simulation in Docker.