Continuous Integration (CI) is a DevOps software development practice that allows developers to check their code into shared repositories, using Source Control Management (SCM) tools such as GitLab or Bitbucket. CI tools invoke the jobs and automatically build and run unit tests on the latest code changes, helping you quickly find and address bugs, improve software quality, reduce time to validate, and enhance software updates.
With CloudBees Release Orchestration SaaS, you can configure your CI tool in your environment. You can configure your access credentials to the tool to access the repository. All authentication and credentials to the tools are captured and maintained in the admin backend, which runs in the cloud, maintained by CloudBees Release Orchestration SaaS. This is maintained in a separate cloud namespace specific to a client. All information except credentials is saved in the cloud database maintained by CloudBees Release Orchestration SaaS. This information, along with the credentials, is sent to the agent running on the client’s premise.
Configuring the continuous integration tool
You can configure any CI tool with CloudBees Release Orchestration SaaS.
To configure a CI tool:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Continuous Integration (CI) on the left pane.
-
Enter a Tool Name.
-
Select a Tool Type from the options.
-
Enter the Tool URL.
-
Enter the API Token to access the tool in the specified format.
-
Select SAVE.
Your CI tool configuration is saved and listed on the right pane.
Configuring GitHub Actions
GitHub Actions is a CI/CD platform that you can configure in CloudBees Release Orchestration SaaS.
To configure GitHub Actions:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Continuous Integration (CI) on the left pane.
-
Select GitHub Actions from the Tool Type options.
-
Enter a Name.
-
Enter the Tool URL.
-
Enter the API Key to access the tool in the specified format.
-
(Optional) Select Include all repositories.
-
Select SAVE.
Figure 1. Configuring GitHub Actions
Your GitHub Actions configuration is saved and listed on the right pane.
Updating a configuration
You can update the CI configuration.
| Select RESET to clear your selection at any time. |
To update your CI configuration:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Continuous Integration (CI) on the left pane.
-
Select a configuration on the right pane.
-
Make any updates.
-
Select Update.
Your CI configuration is updated.
Deleting a configuration
To delete your CI configuration:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Continuous Integration (CI) on the left pane.
-
Select a configuration on the right pane.
-
Select
Delete. -
Select DELETE.
Your CI configuration is deleted.
Accessing the CI tool as a developer
CloudBees Release Orchestration SaaS enables developers to manage pipelines as needed for development and testing. These pipelines are not considered in any of the metrics in the CloudBees Release Orchestration SaaS dashboard and are often referred to as "developer pipelines" or "pre-merge pipelines".
Developers don’t have to manage a completely different set of CI tools for this purpose, as a user with the administrator role manages these tools, while controlling access to a specific set of CI tool jobs, or allowing developers to define pre-merge pipelines for development.
To grant developer access to a CI job:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Continuous Integration (CI) on the left pane.
-
Select a CI tool on the right pane.
Figure 2. Developer access -
Select Provide Developer Access.
-
By default, the developer has access to all jobs in the selected CI tool, but you can limit access to specific jobs. To limit developer access to specific jobs:
-
Select Specific Jobs.
-
Select jobs from the options. These are the jobs the developer can access.
-
-
Select SAVE.
Access to a CI job has been granted to a developer.
Integrating CloudBees CI and Jenkins
CloudBees CI and Jenkins can be included as CI tools along with other available CI tools.
You can access these tools two ways, either Public or Private:
-
If you choose Public for the Access Type, you must provide a username and password or an API token.
-
If you choose Private for the Access Type, you can connect by downloading and installing the provided plugin.
To integrate CloudBees CI and Jenkins:
-
Download the plugin from the CloudBees CI System Configuration page.
Figure 4. The CloudBees CI system configuration page -
To install the plugin on a controller of operations center instance (Jenkins also follows the same steps), select .
Figure 5. Plugin upload -
For plugin configuration, select and search for CloudBees Release Orchestration SaaS.
CloudBees CI and Jenkins are integrated with CloudBees Release Orchestration SaaS. Once uploaded and configured, the plugin instance is displayed in .