Can we expect more flexible environment handling for the activity feed soon?

Steffen Opel [Utoolity]

Given there's a dedicated 'Environment' column in the activity feed, and your sneak peak into "new event types and timeline view" within Kelvin's excellent recent update on Compass and our journey so far, I realize that this is likely in the works already, just to point out the impact of the current environment naming constraint:

We are using parallel Bitbucket Pipelines production environments with custom names to differentiate various flavors of our artifacts, e.g. 'prd-jira', 'prd-confluence', prd-compass' for a semantically cross-product Forge app, so the strict deployments activity limitation on Bitbucket environments with a name rather than a type 'production' results in our deployment activity not showing up in Compass at all (it works as expected for another service where the environment is indeed called 'production').

Can we expect Compass to differentiate environments by type rather than just the name in the near future?

Andrew Freedman

Hi Steffen,

Thanks for sharing your experience with our environments model.

Our intent is to filter based on the environment type, not the name — exactly as you're describing actually. There could be a bug here that you've run into so hopefully we can reproduce it.

If I set up a quick test and add three prod environments (albeit as a serial pipeline rather than in parallel):

pipelines:
  branches:
    master:
      - step:
          name: One for Jira
          deployment: prd-jira
          script:
            - echo "Jira deployment"
      - step:
          name: One for Confluence
          deployment: prd-confluence
          script:
            - echo "Confluence deployment"
      - step:
          name: One for Compass
          deployment: prd-compass
          script:
            - echo "Compass deployment"

It seems to be working okay — but you're getting a different result from your setup?

(Also, we're starting things off with a focus on production environments, but we certainly do have plans to enrich our handling of non-prod environments over time.)

— Andrew