Status: To Do
Fix Version/s: None
Multi-package merges can cause master to be in an inconsistent state when CI runs. I can think of two solutions:
- If it's possible to have a "pause" button for Jenkins to hold all timer-based jobs until manually released, that would be a relatively simple and failure-free solution.
- We could wait for stability on all master branches (e.g. no merges in the last 10-30 minutes) before starting a job. This could still have potential failures if merges do not happen in a timely fashion (e.g. due to Travis delays).
Solution #1 seems like a Jenkins infrastructure task, so I'm assigning this to SQuaRE.