Skip to content

[Question][Framework] Tracking different deployment environments #8348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Bermos opened this issue Mar 20, 2025 · 1 comment
Open

[Question][Framework] Tracking different deployment environments #8348

Bermos opened this issue Mar 20, 2025 · 1 comment
Labels
devops Something about CI/CD (devops) type/question This issue is a question

Comments

@Bermos
Copy link

Bermos commented Mar 20, 2025

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.

@Bermos Bermos added the type/question This issue is a question label Mar 20, 2025
@dosubot dosubot bot added the devops Something about CI/CD (devops) label Mar 20, 2025
Copy link

dosubot bot commented Mar 20, 2025

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].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Something about CI/CD (devops) type/question This issue is a question
Projects
None yet
Development

No branches or pull requests

1 participant