Flow Designer has a Jenkins Events trigger and built-in Jenkins steps to help you integrate Jenkins into your alert management and incident response flows.

Jenkins steps

  1. To add a Jenkins step to your flow, go to the Apps panel in the palette, expand the Jenkins section and drag the step onto the canvas.
  2. Connect the step to the previous step in the flow. This lets you access any alert properties and outputs of previous steps when configuring the inputs.
  3. Double-click the step to edit it, and use the Setup tab to configure the inputs. You can use plain text, input variables, or a combination of both. See the sections below for detailed information on the inputs.
    • If you include request parameters in the Build Parameters Query String input, make sure you URL-encode the string.

  1. On the Run Location tab, set where you want the step to run: in the cloud or on an xMatters Agent installed behind your firewall.
  2. On the Endpoint tab, configure an endpoint that points to your Jenkins instance (or, if you already have one, select it from the list).
  3. To configure a new endpoint:
    • Enter the base URL of your Jenkins instance (for example,
    • In Authentication, add the credentials of a user with permissions to build the project: enter their Jenkins username in the Username field and an API token created for that user in Jenkins in the Password field. You must use an API token as the password; using the user's Jenkins login password will result in errors. If you want to authenticate using the login password, check out the Jenkins step over on xMatters Labs.
    • Make sure Preemptive is selected before saving the endpoint configuration.

Build Project

Use the Build Project step to automatically start a build in Jenkins in response to previous steps in the flow. You can map outputs from previous steps to the inputs to dynamically set the values at runtime.

Jenkins Events Trigger

  1. Go to the Triggers panel in the palette, expand the App Triggers section and drag the trigger onto the canvas.
  2. Double-click the trigger (or click the pencil icon).
  3. Set the authentication method and authenticating user. Alternatively, you can create an integration user to use as the authenticating user.
  4. Copy the URL — you'll use this to set up the webhook in Jenkins.

  5. Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
  6. Click Done.
  7. On the flow canvas, connect the steps you want to run when xMatters receives a request to that URL.

Configure Jenkins to send requests to the trigger URL

To have Jenkins send alerts to the flow trigger, you need to install a notification plug-in and set it to use the trigger URL.