What do you want to see in the API?
Jenkins currently doesn't accept MFA requests for whatever reason. Nobody currently has access to Jenkins further, it can only run unit tests and the rest of the CI workload just fine, but admin access is currently revoked for an unknown reason.
It's been discussed that this server should switch back to GitHub Actions instead of Jenkins. Looking at the Actions runners, the latest activity there was from May 2025 exactly one year ago. Thus this is completely possible, just the costs need to be investigated and addressed first before-hand.
How do you think this should work?
Make a plan of how to pull this off and what else to actually take into account. This touches the repo's deepest settings so we need a clear action plan and steps to achieve this with 0 downtime, if possible.
Any additional info?
Currently only Mikhail as the original lead has access to the repo settings, on top of @jpetays and nobody else has access. This should be addressed further as it's been discussed in the past already. The new person with VIP repo access should either be me and/or @tickBit as the leads.
What do you want to see in the API?
Jenkins currently doesn't accept MFA requests for whatever reason. Nobody currently has access to Jenkins further, it can only run unit tests and the rest of the CI workload just fine, but admin access is currently revoked for an unknown reason.
It's been discussed that this server should switch back to GitHub Actions instead of Jenkins. Looking at the Actions runners, the latest activity there was from May 2025 exactly one year ago. Thus this is completely possible, just the costs need to be investigated and addressed first before-hand.
How do you think this should work?
Make a plan of how to pull this off and what else to actually take into account. This touches the repo's deepest settings so we need a clear action plan and steps to achieve this with 0 downtime, if possible.
Any additional info?
Currently only Mikhail as the original lead has access to the repo settings, on top of @jpetays and nobody else has access. This should be addressed further as it's been discussed in the past already. The new person with VIP repo access should either be me and/or @tickBit as the leads.