CloudBees CI provides a number of enterprise-grade features and capabilities which help organizations scale continuous integration and delivery (CI/CD). This "Getting Started" section assumes that: CloudBees CI is up and running within the organization and the Administrator(s) have a functional CloudBees CI configured.
To follow the example in this document, do the following:
On the operations center main page, click the Teams link on the left menu:
On the following screen, click on Create a team button. On the next screen:
Name your team - you will be able to change it whenever you like;
Select an icon and a color;
Add new team members by entering their Jenkins username or group id; you may use the default value
Select your team controller creation recipe.
Here is an example:
You are then prompted to create a Pipeline. The Create Pipeline wizard will prompt you for the following pieces of information:
Where do you store your code (use "GitHub")
Your GitHub access token (use the token that you created earlier)
Which Organization and Repository (use the
pipeline-examplesrepository that you cloned earlier)
The system will take some time to create this pipeline. By default, the Pipeline system expects a file
by the name of
Jenkinsfile at the root directory of the repository; you will need to customize the Pipeline job
to point to a file that is located in a sub-directory.
If you do not see the
pipeline-examples item that you just created, refresh the browser. When you see
the following screen, click on the gear icon.
Click on the Build Configuration tab and enter
pipeline-examples/parallel-from-list/parallelFromList.groovy in the Script Path text box. Then, click Save.
CloudBees CI scans the repository, which has two branches, and automatically creates two build jobs, one for each branch.
Congratulations on your first Multi-Branch Pipeline!