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

Make the merge queue more flexible to flipping our favorite Jenkins instance #139

Open
gilles-peskine-arm opened this issue Nov 4, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@gilles-peskine-arm
Copy link
Contributor

We have two Jenkins instances (OpenCI and Internal CI), and we keep changing which one is set as a required status check on Jenkins. We also have DCO and readthedocs as required status checks on Jenkins, but those don't run on the merge queue: instead we fake them from one of the Jenkins instance. This has to be the Jenkins instance that actually runs in the merge queue.

On Thursday 2023-11-02 we flipped the required check from Internal CI to OpenCI on GitHub. But we forgot to update the Groovy code that fakes DCO and readthedocs, so for a while the merge queue only ran the Jenkins job but eventually timed out because there was no response to the DCO and readthedocs status checks. (Happened on Mbed-TLS/mbedtls#8464, Mbed-TLS/mbedtls#8462 and many more.)

The emergency fix #138 flips the merge queue fake to OpenCI.

The goal of this issue is to make our setup more robust so that we don't forget again. Can't we have both CIs fake the checks?

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

No branches or pull requests

2 participants