Skip to main content
Use a Jenkins account with the permissions the actions need, because StackOne acts with that user’s own permissions. Reading other users’ full account details and creating users need the Administer permission, putting Jenkins into quiet-down or restarting it needs the Manage permission, and role actions need the Role-based Authorization Strategy plugin.

​
Find your Jenkins URL

Your Jenkins URL is the address you open your Jenkins controller at.

  • Check your browser address bar while signed in to Jenkins.
  • Format: https://{jenkins-host}
  • Example: https://jenkins.example.com
  • Leave off any trailing slash.
  • Paste it into the Jenkins URL field in StackOne Hub.

​
Find your username

Your username is the Jenkins user ID that the API token belongs to.

1

Open your user page

Sign in to Jenkins with the account StackOne will use, then click your user icon in the top right corner of any page.

Jenkins dashboard with the user icon in the top right corner highlighted
2

Copy your username

Your user page shows your user ID next to Username:.

  • Paste it into the Username field in StackOne Hub.
Jenkins user page with the Username value and the Security link highlighted

​
Generating an API token

An API token authenticates StackOne to Jenkins as your user, in place of your password.

1

Add a new token

On your user page, click Security in the sidebar. Under API Token, click Add new token.

  • Shortcut: {your Jenkins URL}/me/security
Jenkins Security page with the Add new token button highlighted under API Token
2

Name and generate the token

In Create new API token, enter StackOne Integration as the Name, choose an Expiration, and click Generate.

  • The default Expiration is 30 Days. When the token expires, the StackOne connection stops working until you add a new token.
  • Choose a longer period, or No Expiration if your security policy allows it.
Create new API token dialog with the Name field, Expiration list and Generate button highlighted
3

Copy the token

Click Copy token and store it securely for use later, then click Done.

  • Jenkins shows the token only once and it cannot be retrieved later. The dialog says “Copy this token now, because it cannot be recovered in the future.”
  • Paste it into the API Token field in StackOne Hub.
New API token dialog with the token value hidden and the Copy token button highlighted
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.

​
Next Steps

Webhooks setup

Configure receiving Events for Jenkins into StackOne.