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

Analysis: Use github workflow as quality gateway in release pipeline #480

Open
acn-sbuad opened this issue Jan 26, 2024 · 2 comments
Open
Assignees
Labels
kind/chore Non functional, often repeating tasks. status/blocked Further work depending on the completion of some other task/PoC/issue

Comments

@acn-sbuad
Copy link
Contributor

acn-sbuad commented Jan 26, 2024

Description

We want quality gateways as a part of our journey towards CD.
We need to investigate if regression tests could be used as quality gates for our deployments.

In scope

No response

Analysis

No response

Conclusion

No response

@acn-sbuad acn-sbuad added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/chore Non functional, often repeating tasks. and removed status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Jan 26, 2024
@SandGrainOne SandGrainOne transferred this issue from Altinn/altinn-platform Apr 5, 2024
@SandGrainOne
Copy link
Member

Turned this into an issue specifically for Notifications as a start. Can create separate issues for other products based on the experiences from the work here.

@olebhansen olebhansen added the status/blocked Further work depending on the completion of some other task/PoC/issue label Aug 5, 2024
@olebhansen
Copy link

olebhansen commented Aug 5, 2024

Pending Flux (Altinn/altinn-platform#721). Need to add a requirement for quality-gates for the Flux process

@olebhansen olebhansen self-assigned this Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Non functional, often repeating tasks. status/blocked Further work depending on the completion of some other task/PoC/issue
Projects
None yet
Development

No branches or pull requests

3 participants