The issue we are running into is that after integrating Bitbucket to Compass to show component events, the results are publishing fine but the events appear in all deployment environments. We're looking for documentation or guidance on how to categorize results from different environments (like prod, staging) so they show up in the relevant buckets of deployment environments in Compass activity.
Also, we are looking for options on how to control publishing results for different divisions.
For deployment events, Compass reads the environment from bitbucket environment type. Deployment events will only be ingested to compass from staging or production environments https://support.atlassian.com/compass/docs/integrate-compass-with-bitbucket-cloud/ Read more about setting up environments in bitbucket here: https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-monitor-deployments/
However, bitbucket build events are detected from pipeline builds on the main branch, and as such, do not have a set environment, so currently we will show them for all selected environments in the activity feed. I believe this is what you are talking about.
What environments you would like them to show up in specifically? Does your main branch build impact multiple environments? To maintain visibility, we show other events even when environment is toggled, but I am curious what you would like to occur. I will take your feedback to our team. Thank you!
Hey @nagaramachandramurthy_sathiraju ,
Have you tried this Set up and monitor deployments?
Specifically, to set deployment property in your Bitbucket Pipelines configuration. The allowed environment names are flexible, but commonly used ones are "test", "staging", and "production."
So, something like this:
pipelines:
default:
- step:
name: Deploy to production
deployment: production
script:
- python deployscript.py prod
These resources might help as well:
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.