I accidentally rolled out the wrong version of CI to production. In
deploying the staging environment, I did not notice that the container
build had been pushed to production, which caused a redeploy of
production using the staging code:
https://github.com/linux-system-roles/test-harness/pull/103 - I fixed
this and redeployed the correct code to production, but in the meantime
several system role PRs were tested with this new code. The main effect
is that the testing status will be in the form
platform-version/ansible-2.9
rather than the old format
linux-system-roles-test/platform-version
The following PRs are affected:
https://github.com/linux-system-roles/certificate/pull/38
https://github.com/linux-system-roles/network/pull/262
https://github.com/linux-system-roles/storage/pull/153
https://github.com/linux-system-roles/network/pull/234
https://github.com/linux-system-roles/storage/pull/121
https://github.com/linux-system-roles/storage/pull/142
https://github.com/linux-system-roles/network/pull/267
https://github.com/linux-system-roles/network/pull/261
https://github.com/linux-system-roles/logging/pull/166
I don't think there will be any issues, it's just that the above PRs
will have statuses that should ignored. I'm not sure if the number of
statuses in any of the above PRs has increased enough that we will hit
the github page size for statuses (note that we have fixed this issue in
staging, but it has not yet been rolled out to production), or any rate
limit problems. And unfortunately the github API provides no way to
remove statuses. I will continue to monitor.