You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all deployments get the environment PRODUCTION (docu). We would like to also track deployments to other environments and would also be willing to contribute the necessary code. Before we do that We wanted to clarify if there were any reasons not to track other environments, if there were other plans or dependencies or if this was just not priority yet.
Screenshots
If applicable, add screenshots to help explain.
Additional context
Add any other context here.
The text was updated successfully, but these errors were encountered:
Hi @Bermos! I'm here to help with any bugs, questions, or contributions you have. Let's tackle this together!
I found a similar closed issue regarding the configuration of deployment environments. The issue was titled "[Feature][DORA] Allow users to configure the environment of deployments by other attributes rather than 'job/build name'" but no solution was found in the comments [1].
Currently, the environment is set to 'PRODUCTION' using a regex pattern match in the codebase. Specifically, if the data.RegexEnricher is not nil and the ReturnNameIfMatched method matches the devops.ENV_NAME_PATTERN with gitlabDeployment.Environment, then domainDeployCommit.Environment is set to devops.PRODUCTION[2].
There are existing configuration options that could be leveraged to specify different deployment environments. For BitBucket, the deployment environment can be specified using the deployment key in the BitBucket CI .yml file. For GitHub, deployments can be recognized by specifying a regex to identify production environments among all 'GitHub environments' [3][4][5].
If you plan to contribute code to support tracking multiple environments, you might need to update or expand existing tests related to deployment environments, such as those in the backend/plugins/bitbucket/e2e/deployments_test.go file [6].
Question
Currently all deployments get the environment
PRODUCTION
(docu). We would like to also track deployments to other environments and would also be willing to contribute the necessary code. Before we do that We wanted to clarify if there were any reasons not to track other environments, if there were other plans or dependencies or if this was just not priority yet.Screenshots
If applicable, add screenshots to help explain.
Additional context
Add any other context here.
The text was updated successfully, but these errors were encountered: