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
Notificationtab.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.
User-owned CI jobs: FAQs on access level and permissions
Does this apply to team-shared CI jobs?
If you have configured team-shared CI jobs, then delegating access to these jobs can be configured in Pipelines & CI jobs page in Gearset app.
More information in this article:
User permissions for team-shared orgs, CI jobs and pipelines
Do multiple members on your team require access to CI job(s)?
If multiple members on your Gearset team require access to user-owned CI job(s), Gearset recommends to consider setting up a team-shared CI jobs instead.
Check our guidance on converting a CI job to team-shared CI job.
Which permission does a team member need to have access to run a CI job?
Which permission does a team member need to have access to run a CI job?
If a team member is not the owner (creator) of the CI job, they need either:
Option 1: CI job owner can assign
Deploymentaccess level for a target org of the CI job to any member on their Gearset team. This can be done directly from the Delegate org access page in our app.
More details in: Assigning Salesforce orgs to Members.Note:
ComparisonorValidationaccess level doesn't allow members to run a CI job, but it allows them to run either a comparison or a validation in our 'Compare and deploy' feature with the use of org(s) delegated to them.Option 2: Team member can be assigned a Team Owner role on the Gearset team (see Managing new team members for guidelines on how to configure it).
Team Owner roles gives team members access to edit settings of all the user-owned CI jobs displayed on the CI dashboard.Option 3: Alternatively, if required, the whole CI job ownership can be transferred directly from the current CI job owner to a new member on the Gearset team.
More details in: Transferring CI job ownership.
Which permission need to be enabled to grant access to edit settings of specific CI job(s)?
Which permission need to be enabled to grant access to edit settings of specific CI job(s)?
If a Team Owner on the Gearset team gives a member a Team Owner role, they'd be able to access edit settings for all the user-owned CI jobs across the Gearset team.
It isn't possible to give a specific team Member access to edit settings of a particular (e.g. only one) CI job.
If you have any other questions related to access level to user-owned CI jobs in our app, and we have not addressed them in this article, let us know via in-app chat!