Skip to content
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

[Feature][CICD] Add an original_environment field to cicd_deployments and cicd_deployment_commits #6854

Closed
7 of 8 tasks
Startrekzky opened this issue Jan 19, 2024 · 0 comments · Fixed by #6889
Closed
7 of 8 tasks
Assignees
Labels
type/feature-request This issue is a proposal for something new
Milestone

Comments

@Startrekzky
Copy link
Contributor

Startrekzky commented Jan 19, 2024

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Use case

Many community users asked why the environments of some deployments are converted to PRODUCTION. This is because the Scope Config has been used to standardize the values of field environment in all cicd tables, e.g. https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema#cicd_deployments

To make the transformation logic more open, I suggest adding an original_environment field to all CI/CD tables.

Description

  • Add an original_environment field to cicd_deployments
  • Add an original_environment field to cicd_deployment_commits
  • Value assignment logic
    • If the deployments are from GitHub/GitLab/BitBucket/Bamboo's deployments, set the original_environment with the deployments's value in the source tool
    • If the deployments are from CI pipelines such as GitHub workflow run and Jenkins builds and so on, set the original_environment to an empty string

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Startrekzky Startrekzky added the type/feature-request This issue is a proposal for something new label Jan 19, 2024
@Startrekzky Startrekzky added this to the v1.0 milestone Jan 19, 2024
@d4x1 d4x1 self-assigned this Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature-request This issue is a proposal for something new
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants