Best way to capture job details on self-hosted ARC runners? #174509
Replies: 3 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
ARC (Actions Runner Controller)
Discussion Details
Hi team,
We have a use case where we’d like to capture details of jobs that are scheduled on our self-hosted (ARC) runners (like Job ID, Job name, Workflow details, commit details, etc).
Right now, our approach is to patch pod labels with these details after retrieving details from
events.json(from _temp/_github_workflow/event.json) using a sidecar container, which picks up the file and patch the pod labels once a job is scheduled on a runner.Is there a better or more recommended way to achieve this? Does the ARC Controller natively support this, or is there a plan for it in the future?
Any suggestions or insights would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions