You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The developers on our project feel safe to merge a PR when all of the commit checks are green, including usually our Jenkins run.
However, if the Jenkins plugin asks for permission to test a PR, it doesn't update the commit status, and so a developer may miss that the tests weren't run. (For example, this recently happened on kubernetes/kubernetes#11379.)
If the plugin would mark a commit as pending while waiting for permission to run tests, it would make it very obvious that tests hadn't run yet. (Extra bonus if the commit status mentioned that it was waiting for permission.)
The text was updated successfully, but these errors were encountered:
The developers on our project feel safe to merge a PR when all of the commit checks are green, including usually our Jenkins run.
However, if the Jenkins plugin asks for permission to test a PR, it doesn't update the commit status, and so a developer may miss that the tests weren't run. (For example, this recently happened on kubernetes/kubernetes#11379.)
If the plugin would mark a commit as pending while waiting for permission to run tests, it would make it very obvious that tests hadn't run yet. (Extra bonus if the commit status mentioned that it was waiting for permission.)
The text was updated successfully, but these errors were encountered: