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

Don't run full integration tests on trivial changes (e.g. ci changes, renovate changes etc) #112

Open
cafkafk opened this issue Feb 4, 2025 · 0 comments · May be fixed by #114
Open

Don't run full integration tests on trivial changes (e.g. ci changes, renovate changes etc) #112

cafkafk opened this issue Feb 4, 2025 · 0 comments · May be fixed by #114

Comments

@cafkafk
Copy link
Member

cafkafk commented Feb 4, 2025

We should use a path specification for the workflows so that some files wont trigger the full integration tests. This will also require separation of the flake checks into their own jobs, since we may want to run e.g. formatting checks for json/yaml/toml changes, but not actually run the full vault tests when unnescesarry.
cafkafk added a commit that referenced this issue Feb 4, 2025
@cafkafk
ci: separate jobs, make vault tests only run on real changes
0a5c839 
Closes: #107 #112
Signed-off-by: Christina Sørensen <[email protected]>
@cafkafk cafkafk linked a pull request Feb 4, 2025 that will close this issue
fix(renovate): config issues + refactor CI to be less tedious #114
Open
@cafkafk cafkafk linked a pull request Feb 4, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(renovate): config issues + refactor CI to be less tedious DBCDK/faythe
1 participant
@cafkafk