Continuous Integration
Sentry uses a variety of continuous integration services to help ensure we don't accidentally break the application.
Deployments
GoCD is used for deployments. Please refer to the internal user guide.
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.
Docker images
We primarily use a composite GitHub action 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.
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
CI workflow for testing changes with getsentry
See Workflow.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").