The Jenkins plugin can display build information from a GitHub Organization project in your Jenkins instances.
ℹ️ NB: Other Jenkins project types like Freestyle project and Pipeline are not supported yet.
This page explains how to configure it in Roadie Backstage.
- You must be an admin in Roadie. By default, all users are admins. Learn how to designate certain users as admins here.
- Your Jenkins instance must be accessible by Roadie backend instances. To allow list Roadie access you can check our IPs here.
Roadie requires an API token to be able to connect to Jenkins.
You can generate an API token for your user by visiting Jenkins UI at
<your-Jenkins-instance>/user/<your-account>/configure/ and by clicking “Generate” in the “API Token” section.
Visit the Roadie Secrets page (show me how) and enter the token into the
Enter your Jenkins instance API endpoint and username into Roadie.
- Click “Administration” in the sidebar, then “Settings” in the tabs.
- Find “Jenkins” in the Configuration sidebar.
- Enter your Jenkins instance URL and the username your Jenkins API token is owned by and click “Save” then “Apply & Restart”.
The Jenkins plugin provides two type of UI elements.
EntityLatestJenkinsRunCard displays the latest runs for an entity.
This card can be added to component dashboards.
EntityJenkinsContent presents a job folder in Jenkins and jobs it contains. It also display details of each job within the folder.
This component can be added as a tab to component layouts.
The Jenkins plugin uses
jenkins.io/job-full-name annotation to determine the correct GitHub organization folder and job name within your Jenkins instance.
You can configure it as follows:
// catalog-info.yaml metadata: annotations: jenkins.io/job-full-name: [github-organization-project-name/job-name]
More information how to configure the plugin for your component can be found from the plugins documentation.
If you require integrating with multiple Jenkins instances contact Roadie via the in-app chat widget and we will enable it for you.