Open ChristopherHX opened 1 year ago
I wonder how I could test the new protocol, until it is live.
Theoretically jobs from RunnerJobRequest
can work right now in the main
branch, but maybe I made a mistake.
At least with https://github.com/ChristopherHX/github-act-runner/pull/126 I assume it should work.
There has been an update to the timeline of the breaking change: https://github.com/actions/runner/issues/886#issuecomment-1669631425
Thank you all for being patient with us. 🙇🏼♂️ As bryanmacfarlane mentioned earlier, we are almost there for this feature, since this involves some pretty significant changes on our end, we are being careful in the process, and we are currently addressing a few scale concerns. We'd like to do some load testings as well. The current ETA for beta testing this feature is end of August / early September timeframe. Again thank you very much for using Actions and being patient while we make these changes.
The next weeks are safe from the coming breaking change.
Another update, self-hosted runners can be affected (if that date is actually correct and they don't postpone it again) starting with 12. September 2023 on github.com src: https://github.blog/changelog/2023-08-29-github-actions-review-network-access-settings-for-the-self-hosted-runners/. At least the changelog entry reads to imply some server change like moving the protocol over to the new backend.
:warning: Release <= v0.6.4 has a bug, which prevents uploading logs via results service.
Partial testing now possible, results receiver endpoint now defined.
Warning github-act-runner may stopped working!, please investigate (resolved)
FWIW, I just ran our snmalloc
workflow that uses github-act-runner
and things look fine, so that alert may just be a local thing in the regression test.
It was an outage of the deb repository used for installing the runner, until now we are still using the good old protocol. The only thing changed is that the GitHub Actions Services are now powered by .net (core) and Kestrel (a new http header appeared)
Status Update
They seem to officially target Q1 2024 for this change now...
Long waiting to be hit by announced backend changes
Alert Regression Public beta of Actions streaming logs with backscroll seem to break live logs.
Logs still appear if the job finished and you refresh the page.
Maybe this runner need to start to also do dual upload of step updates to both old and new backed like the official runner.
Release v0.6.8 fixes the live log issue, consider updating to resolve the regression using the beta backend
(Test) Rollout for a breaking service change has been seen in the wild https://github.com/ChristopherHX/github-act-runner/issues/186
Waiting for beeing affected to implement and test this change in the runner
Resolved in v0.8.0, the next wave is ahead
Based on
GitHub Changeloghttps://github.com/actions/runner/issues/886#issuecomment-1669631425, they aim to make the breaking change onend of August / early September timeframe and start to send the newJuly 31, 2023
RunnerJobRequest
message.actions/runner protocol changes
github/actions-runner-admin
broker
github/actions-run-service (written in go source)
the new protocol isn't fully implemented yet on the actions/runner, some code only works with the old protocol, seems to change shortlygithub/actions-results-service (written in go source(1) and source(2))
launch service (github/actions-dotnet based)
This runner changes
This change could make all current github-act-runner releases unusable and you are forced to update from old releases.