Currently we run Jenkins on the branch as well as on the merged PR. If the tests on the branch fail (it might be due to environment issue) the change is marked as "CI failed". Though we don't care about it, if the merged change passes. There's also no way to rerun those tests, so they stay "red".
GitHub doesn't provide an API to remove statuses. Disabling the branch tests also isn't an option as it would break Greenkeeper.
How do you think it can be solved?
Trigger the branch tests only if the branch name starts with greenkeeper/.
How many hours per week do you waste thanks to this time sink?
It's more nerves than hours :)
How important do you think this is to fix?
I find it important as on Github it looks like we constantly merge things although CI failed.
What is the time sink?
The CI is red although things a ready to merge.
Currently we run Jenkins on the branch as well as on the merged PR. If the tests on the branch fail (it might be due to environment issue) the change is marked as "CI failed". Though we don't care about it, if the merged change passes. There's also no way to rerun those tests, so they stay "red".
GitHub doesn't provide an API to remove statuses. Disabling the branch tests also isn't an option as it would break Greenkeeper.
How do you think it can be solved?
Trigger the branch tests only if the branch name starts with
greenkeeper/.How many hours per week do you waste thanks to this time sink?
It's more nerves than hours :)
How important do you think this is to fix?
I find it important as on Github it looks like we constantly merge things although CI failed.