Administering CloudBees Jenkins Enterprise 2.x
This guide is an old version of Getting Started with CloudBees Jenkins Enterprise 2.x, and is superseded by Getting Started with CloudBees Core on Modern Cloud Platforms.
Please refer to Getting Started with CloudBees Core on Modern Cloud Platforms for updated content.
CloudBees Jenkins Enterprise 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 Jenkins Enterprise is up and running within the organization and the Administrator(s) have a functional CloudBees Jenkins Enterprise 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 master 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 Jenkins Enterprise scans the repository, which has two branches, and automatically creates two build jobs, one for each branch.
Congratulations on your first Multi-Branch Pipeline!
Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.
CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center and DEV@cloud are trademarks of CloudBees, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about.
Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.
Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.