Jenkins

What is Jenkins?

Jenkins is an open-source automation server that helps developers build, test, and deploy software efficiently. It enables continuous integration and continuous delivery (CI/CD), allowing teams to automate workflows and improve software quality.

How is this integration useful?

Integrating Jenkins with Entitle simplifies access management by automating permissions, ensuring the right users have access when needed. This improves security, reduces manual administration, and enhances compliance while supporting seamless DevOps workflows.

Through this integration, Entitle can manage the following resource types in Jenkins:

• Global roles
• Node roles
• Item roles

Prerequisites

• You must have an Admin account in Entitle.
• The user that will integrate with Entitle must have Admin privileges in Jenkins and have a role-based plugin installed.

  ℹ️

  Note

  For further details, see the Install role-based plugin step in this guide.

• Access to your Jenkins host, port, username, and API token.

Install a role-based plugin in Jenkins

ℹ️

Note

If you have already installed the role-based plugin, move on to the next step in this guide.

1. Log in to Jenkins.

   The Jenkins homepage displays

2. Navigate to Manage Jenkins on the left-side menu.

   

   The Manage Jenkins page displays

3. Click Configure Global Security > Manage Plugins.

   

4. Locate the Role-based Authorization Strategy plugin, and enable it.

   

Create a new API token

1. On the Jenkins homepage, locate the People tab in the left-side navigation bar.

   

2. Click on the Admin user > Configure.

   

3. In the Configure page, locate the API Token section.

4. Click Add new Token.

   

   A new API Token adds

5. Copy your new API Token for the configuration later on in this guide.

Create the Jenkins integration in Entitle

1. Sign in to Entitle.

2. Navigate to the Integrations page.

3. Click Add Integration.

4. In the Application field, enter Jenkins.

5. In the Save on dropdown, select Entitle cloud or your hosted agent.

   

6. In the Connection field:

   1. ssl: set to false or true depending on how you configured your Jenkins server.
   2. host:
      1. If SSL is set to false, insert your instance host. Make sure to not include the https:// prefix.
      2. If SSL is set to true, insert your domain.
   3. port: The port you configured on your Jenkins server:
      1. Normally, if SSL is set to true, insert 433.
      2. If SSL is set to false, insert 8080.
   4. username: Insert the Jenkins Admin’s username.
   5. api_token: Insert the new API Token you created earlier.

Example Connection JSON:

{
 "ssl": "<true>" or "<false>",
 "host": "<YOUR_HOST>" or "<YOUR_DOMAIN>",
 "port": "<443>" or "<8080>",
 "username": "<YOUR_ADMIN_USERNAME>",
 "api_token": "<YOUR_API_TOKEN>"
}

7. Click Save.
   The Entitle integration with Jenkins saves