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

Add a force option #120

Open
kutschke opened this issue Jun 3, 2024 · 0 comments
Open

Add a force option #120

kutschke opened this issue Jun 3, 2024 · 0 comments

Comments

@kutschke
Copy link
Collaborator

kutschke commented Jun 3, 2024

The CI refuses to rerun the CI if, since the last CI run, there are neither intervening commits on the PR not changes to the HEAD of the repo. This means that if there is an external issue, such as a change to mu2e_trig_config or the DB server going down, we cannot rerun the CI.

We should add syntax to the CI launch command that forces the CI to run even if it would be blocked by those tests. I think it's OK if anyone who can relaunch the CI can also use the force option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant