Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Jenkins spoke

Log in to subscribe to topics and get notified when content changes.

Jenkins spoke

Manage builds, users, settings, and jobs on the Jenkins server. Retrieve Jenkins data to use in a flow.

The Jenkins spoke requires an IntegrationHub subscription. To learn more about the IntegrationHub product, see IntegrationHub.

Supported versions

All versions between 1.651.1 and 2.150.3.

Spoke actions

The Jenkins spoke provides actions to automate Jenkins tasks when events occur in ServiceNow. Available actions include:

Category Action Description
Build Management Delete Build Deletes a build from a Jenkins server job.
Get All Builds Retrieves all the builds for a given Jenkins server job. Returns the URL, build number, and class of each build.
Get Build History Retrieves a range of build history for a given job from Jenkins Server.
Get Build Information Retrieves the build timestamp, build status, and complete build information of a given job from the Jenkins server.
Get Build Number Retrieves the build number for a Jenkins server job based on a pre-defined build filter, such as last successful build.
Perform a Build Executes a job on the Jenkins server.
Configuration Management Create Jenkins Credentials Creates Jenkins server credentials.
Create Node Creates a node that you can launch with Java Web Start software. A node is a machine that is part of the Jenkins environment and capable of executing jobs.
Delete Node Deletes a node from the Jenkins server.
Get CSRF Token

Retrieves a CSRF token if your Jenkins server has the "Prevent Cross Site Request Forgery exploits" option enabled.

Note: If your Jenkins server has CSRF protection enabled, use this action to retrieve a token for use by the rest of the flow. The action outputs the token as a data pill for use in other actions in the flow.
Get Version Retrieves the Jenkins server version.
Restart Jenkins Restarts the Jenkins server.
Test Connection Tests the connection to the Jenkins server.
Job Management Copy Job Creates a job by copying an existing Jenkins server job.
Create Folder Creates a Jenkins server folder to organize jobs.
Create Job Creates a Jenkins server job from an XML file.
Delete Folder Deletes an existing Jenkins server folder.
Delete Job Deletes a Jenkins server job.
Get All Jobs From Folder Retrieves all the jobs from a given Jenkins server folder. Returns the class and name of each job up to the specified number of levels.
Get Build Timestamp Retrieves the build timestamp of a specified Jenkins server job.
Get Console Output Retrieves the build console output of a specified Jenkins server job.
Get Job Configuration Retrieves the XML configuration for a Jenkins server job.
Reload Job Reloads a Jenkins server job.
Rename Job Renames a Jenkins server job.
User Management Create User Creates a Jenkins server user.
Delete User Deletes an existing Jenkins server user.
View Management Add Job To View Adds a job to the Jenkins server view. Views are containers to organize jobs. As a Jenkins instance grows, you can create views for appropriate groups and categories. For example, you may want to create a Build view, which only displays build-specific jobs.
Create View Creates a Jenkins server view.
Delete View Deletes a Jenkins server view.
Get All Jobs From View Retrieves all jobs from a Jenkins server view. Returns the class and name of top-level jobs.
Remove Job From View Removes a job from a Jenkins server view.

Support for CRSF tokens

If your Jenkins server has the "Prevent Cross Site Request Forgery exploits" option enabled, certain actions require a unique token. Use the Get CSRF Token action to retrieve a token for use by the rest of the flow. The action outputs the token as a data pill for use in other actions in the flow.

Connection and credential requirements

IntegrationHub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see Credentials and connection information.

This spoke uses the Jenkins Connection & Credential Alias record to authorize actions. To use the spoke connection alias, create an associated Connection record and an associated Credential record.

MID Server requirements

These actions use REST calls, which run on a MID Server. Use the connection record associated with the Jenkins alias to configure where actions run as well as set MID Server selection attributes.

Feedback