When you create an account in CloudBees Release Orchestration SaaS, you are given the option to integrate an existing CI tool. For onboarding, CI tool options are limited to Jenkins open-source automation server, CloudBees Jenkins Operations Center (CJOC), and CloudBees CI, but you can configure other CI tools after onboarding.
You can choose either public or private access for your CI tool:
-
Choose Public access if the CI tool instance is accessible from the internet, and configure your tool with a username and either an API token or a password.
-
Choose Private access if the CI tool instance is behind a firewall and an outbound call to the CloudBees Release Orchestration SaaS server is possible. You must install the CloudBees Release Orchestration plugin.
| You can select Skip Setup to access the main CloudBees Release Orchestration SaaS navigation and configure CI tools later, in . Refer to Continuous integration for more information. |
To configure your CI tool during onboarding:
-
Select the Tool Type from the two options.
-
If you have selected CloudBees CI, Do you have CJOC currently implemented displays. Select Yes or No accordingly.
-
Select the Access Type from the options, and then:
-
For Public access:
-
Enter a Name.
-
Enter a URL.
-
Select your login method from the two options.
-
Enter a Username.
-
Enter either an API Token or a Password, according to your login method.
-
Select Connect.
-
-
For Private access:
-
Select Download Plugin.
-
Copy the Authentication code and paste it into your plugin installation.
-
Select Proceed.
-
-
-
If you selected CJOC, select the controllers you want to connect from the options, and then select Next.
You have configured your CI tool, as shown in Added Instances with a 
, and it is now integrated with CloudBees Release Orchestration SaaS.
If you encounter errors in the integration, select the  Error icon to view the logs.
|