Details
-
Suggestion
-
Resolution: Invalid
-
P1: Critical
-
None
-
None
-
None
Description
Each cycle of the integration of a repo should start with a self-test stage:
1. Self-test
2. Look for staged patches
3. Move staged patches to integrating
4. Run integration, build, test
5. Go to 1
The self-test can be simple or advanced, but should include stuff like checking that the network-test services are up and running and responding. This would solve issues like the song and dance of re-staging changes due to network-test issues:
https://codereview.qt-project.org/#change,58523
There's absolutely no reason for the CI to waste cycles on building and testing, and wasting developer time for re-staging changes, if the integration can not succeed due to a core infra being down.