Skip to content

fix(ci): Improve Continuous Improvement Docs #15373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
+6 −10
Draft

fix(ci): Improve Continuous Improvement Docs #15373

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bb1fb7
updated some language for continuous integration
kenzoengineer Oct 31, 2025
daf11a0
remove redundant block
kenzoengineer Oct 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 6 additions & 10 deletions develop-docs/development-infrastructure/continuous-integration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,23 @@
---
title: Continuous Integration
description: Sentry uses a variety of continuous integration services to help ensure we don't accidentally break the application.
description: Continuous Integration at Sentry automatically tests code changes to ensure reliability, helps build images to be deployed to production, and more.
sidebar_order: 80
---

## Deployments

[GoCD](https://deploy.getsentry.net) is used for deployments. Please refer to the [internal user guide](https://www.notion.so/sentry/GoCD-User-Guide-4f8456d2477c458095c4aa0e67fc38a6).

## GitHub Actions

GitHub actions is our primary CI system and runs our tests on every pull request and on merges to master. It is required that tests pass before changes can be merged.
We use Github Actions as our primary CI system. With it, we run many quality checks, including but not limited to testing, linting, and code coverage. We only run front end tests if there are front end changes, and vice versa for back end tests. These actions run in pull requests and also merges into `master`. Pull requests must successfully run all actions in order to be merged into `master`.

## Docker images

We primarily use [a composite GitHub action](https://github.com/getsentry/action-build-and-push-images) for building and pushing images. This ensures that the workflows for building and publishing images are standardized, and appropriate metadata is available in the images. The standard for artifact management can be found [here](https://www.notion.so/sentry/Standard-Spec-Artifact-Management-22a8b10e4b5d80ecb6dcca3eb4558f5b).

We use GHCR (github container registry) for images that are used in CI, self-hosted, and local development. GAR (google artifact registry) is used for images that are used in prod.

## Fast-Revert
In order to facilitate quick changes to unblock failures on default branches, many of our repositories have a fast-revert workflow. In order to use it, PR's can be automatically reverted once a label `Trigger: Revert` is applied. More details found [here](https://www.notion.so/sentry/Standard-Spec-Fast-Revert-2388b10e4b5d8019bc98d863703d1b17?pvs=25)
## CI workflow for testing changes with getsentry

See [Workflow](/development/workflow/) for information on testing and reverting.

## CI workflow for testing changes with getsentry
## Deployments

See [Workflow](/development/workflow/).
At Sentry we use [GoCD](https://deploy.getsentry.net) for our deployments. Please refer to the [internal user guide](https://www.notion.so/sentry/GoCD-User-Guide-4f8456d2477c458095c4aa0e67fc38a6) for more information.
Loading