Managing and viewing your CI jobs

This describes how to manage and view your CI jobs, as well as how to temporarily disable any CI job that you have.

Charlie Palenciano Middleton avatar
Written by Charlie Palenciano Middleton
Updated over a week ago

Managing and viewing your CI jobs

The Continuous integration dashboard displays all your current CI jobs, the source and target for each, when the job was last run, and its outcome. When you click on a job, the Job type will be displayed: either Deployment or Validation. For jobs you own, you can manually start a CI job on-demand by clicking on the play button in the actions column. To see the details of every time the CI job ran, click on View history.

If you are a Pipelines user, at times you will find the settings you need to use in the CI dashboard. The creation of your pipeline starts at the CI job dashboard, from here you edit the jobs which ultimately make up your pipeline.

Managing notifications on your CI job

Setting your notification preferences for CI jobs

  • Select the CI job and click Edit settings...

  • Select the Notification settings tab.

  • Choose whether to get notified after every CI job run, irrespective of the outcome, or only if the CI job fails.

  • Enter the email address(es) of who to notify of the result.

  • Gearset also supports:

    • SMS notifications (US, UK and Australia only),

    • Slack or Microsoft Teams integration via webhooks, into a specific channel,

    • and/or Chatter integration, straight into your org.

Temporarily disabling CI jobs

When a CI job is created, it is added in an Enabled state. This means it will automatically run using the trigger you specified - either every 4 hours, every 24 hours, or when the source branch is updated.

You can stop CI jobs from running automatically by switching their status to Disabled. A disabled job will not run unless you click the Run now button (only available if you are the job owner), regardless of any webhooks or timing options set during creation. To switch a job between enabled or disabled, click the slider into the desired state.

(Please Note: Only a team owner or the creator of the CI job will be able to change the state of the CI job, or to edit its settings.)

Within the CI dashboard there are various other settings that are very useful for customizing each individual CI job. More information on creating webhooks can be found here. If you are looking for documentation regarding transferring CI job ownership, you can find it here. Finally, when looking to set up a CI job for the first time you can find information here.

You can also create outgoing webhooks for CI jobs to trigger third party services.

Transferring a CI job between owners can also be done from here with a few steps.

How are CI jobs used in Pipelines? Watch our short demo video.

Based on Gearset's powerful CI jobs, Pipelines brings some new functionality to help you manage where changes are in your release process, and helps give your entire team visibility and control over the workflow.

Did this answer your question?