Upcoming runner-admin / broker / run / results / launch service support

[ChristopherHX]

Based on GitHub Changelog actions/runner#886 (comment), they aim to make the breaking change on July 31, 2023 end of August / early September timeframe and start to send the new RunnerJobRequest message.

actions/runner protocol changes

github/actions-runner-admin

• Update runner to handle Dotcom/runner-admin based registration flow actions/runner#2487
• Parse runners and send publicKey actions/runner#2490
• Register Runners against V2 servers actions/runner#2505

broker

• Listen directly to Broker for messages actions/runner#2500

github/actions-run-service (written in go source)

• server wrapper for pulling full job message actions/runner#1933
• changes to support specific run service URL actions/runner#2158
• start calling run service for job completion actions/runner#2412
• Run service: send more stuff as part of job completed actions/runner#2423
• call run service renewjob actions/runner#2461
• the new protocol isn't fully implemented yet on the actions/runner, some code only works with the old protocol, seems to change shortly

github/actions-results-service (written in go source(1) and source(2))

• Use results for uploading step summaries actions/runner#2301
• Always upload to avoid issues actions/runner#2334
• Uploading step logs to Results as well  actions/runner#2422
• Add job log upload support actions/runner#2447
• Update Runner to send step updates to Results actions/runner#2510
• Bypass job server when run service is enabled actions/runner#2516
• Also send in conclusion for steps actions/runner#2531

launch service (github/actions-dotnet based)

• Resolve Actions Directly From Launch for Run Service Jobs actions/runner#2529

This runner changes

• Handle RunnerJobRequest ( Experimental ) #71
• Experimental handle RunServiceUrl #87
• Adjust RunnerJobRequest support #99
• Renew job requests
• Send final step state in job completed message
• Send step state updates to results service
• Send step and job logs to the results service
• Support runner-admin registration #165

This change could make all current github-act-runner releases unusable and you are forced to update from old releases.

[ChristopherHX]

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 #126 I assume it should work.

[ChristopherHX]

There has been an update to the timeline of the breaking change: actions/runner#886 (comment)

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.

[ChristopherHX]

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.

[ChristopherHX]

⚠️ Release <= v0.6.4 has a bug, which prevents uploading logs via results service.

Partial testing now possible, results receiver endpoint now defined.

[github-actions]

Warning github-act-runner may stopped working!, please investigate (resolved)

[nwf-msr]

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.

[ChristopherHX]

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)

[ChristopherHX]

Status Update

They seem to officially target Q1 2024 for this change now...

• Log lines for an active step are inaccessible actions/runner#886 (comment)
• GitHub Roadmap entry for Q1 2024 GitHub Actions: Streaming Logs & Scrollback github/roadmap#839

Long waiting to be hit by announced backend changes

[ChristopherHX]

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.

[ChristopherHX]

Release v0.6.8 fixes the live log issue, consider updating to resolve the regression using the beta backend

[ChristopherHX]

(Test) Rollout for a breaking service change has been seen in the wild #186

Waiting for beeing affected to implement and test this change in the runner

Resolved in v0.8.0, the next wave is ahead

[github-actions]

Warning github-act-runner may stopped working!, please investigate

[ChristopherHX]

False alarm, GitHub removed my 1 year old regression runner registration deliberately.

They should fix their service!, saw a GitHub Issue before

My backup regression voter on private repo still working...