If you notify Rollbar every time you deploy or release your app, you'll unlock several features that will help your debugging process.
NOTE: Deploy tracking is enabled by config changes made outside of Rollbar; you will need to send API calls from your CICD tool to the Rollbar API to notify the platform of your deploy actions. They will not be detected automatically.
Instructions for reporting deploys in specific tools are in the links to the left.
The deploy screen shows a detailed view of all deployments made to a particular environment.
The entry for each deploy includes:
- Start & finish time
- Deploy status
- Deploying user (if known)
- Target environment
- Code version (typically a Git SHA or a version number)
- Deploy comments
- List of commits included (if you've connected Rollbar to a git repository)
If you've connected Rollbar to a git repository, then your deploys page will show all commits that have not yet been deployed to production.
When deploys are reported to Rollbar, we'll attempt to identify a 'Suspect Deploy' for each error.
The suspect deploy is one of the following:
- The last deploy prior to the first occurrence of the error (if the item has never been resolved).
- The last deploy prior to the reactivation of the error (if the item was previously resolved).
We are planning to improve our suspect deploy algorithm in the future to improve its accuracy.
Deploys will appear in your live item feed so you can quickly see whether a recent deploy might be responsible for new errors.
You may want to resolve all active items every time you deploy, so that only new occurrences of errors and messages will appear in your live feed. This can be configured via the instructions here.
If a deploy is reported with
started, the deploy must be updated to have status of
timed_out within a certain time period (default is 1 minute), otherwise the system will set the status to
timed_out. The timeout period for each project can be set at Settings → Deploys.
Updated 10 months ago