CircleCI integration
Connect CircleCI to service workflows so engineers can rerun builds, approve jobs, and manage contexts through a request.
What it connects
- Retrieve organizations, projects, and groups to identify the right CircleCI target for a request.
- Pull pipeline and workflow status to explain failed or stuck builds in a ticket.
- Pull job details and test metadata when a developer asks why a job failed.
- Retrieve contexts and project settings before any change is made to them.
What it automates
- Trigger pipelines for a project when a developer requests a fresh build.
- Rerun or cancel workflows so failed or stuck builds are handled from a support ticket.
- Create contexts and add or update context variables for teams that need shared build settings.
- Approve held jobs and manage pipeline schedules after the right people sign off.
In practice
- A developer asks in Slack to rerun a failed workflow. STLabs finds the pipeline, reruns the workflow, and replies in the thread with the new status.
- A team needs a new shared variable for its builds. After approval, STLabs adds it to the right CircleCI context and records the change on the ticket.
- A release is waiting on a held job. When the release manager approves the request, STLabs approves the job in CircleCI so the workflow continues.
- A runaway workflow is tying up build capacity. STLabs cancels it from the request and notes the cancellation on the ticket for the owning team.
