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.

Sign up for GitHub

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

Jump to bottom

Regression detection should provide possible culprits based on git history #275

Open
fjetter opened this issue Aug 23, 2022 · 0 comments
Open

Regression detection should provide possible culprits based on git history #275

fjetter opened this issue Aug 23, 2022 · 0 comments
Labels
dx Developer experience enhancement New feature or request infrastructure Work related to infrastucture regression

Comments

@fjetter
Copy link
Member

fjetter commented Aug 23, 2022

If we detect a regression, it would be great if the CI job can already check the git histories of our most important upstream packages and print possible changes that could cause a regression in a given timewindow

See also #271 (comment)
@fjetter fjetter added enhancement New feature or request infrastructure Work related to infrastucture regression dx Developer experience labels Aug 23, 2022
@ncclementi ncclementi mentioned this issue Aug 25, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dx Developer experience enhancement New feature or request infrastructure Work related to infrastucture regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fjetter