actions / actions/actions-runner-controller

Build Logs to Standard Out

Open
#2,478 7 comments 24 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs triage
Dominant language
Go
Stars
6.5k
Forks
1.5k
Avg merge
2d 2h
Merged PRs (30d)
27

Description

What would you like added?

I would like to be able to collect the build logs, which show up in the GHA UI, in the pods standard out. This would allow me to store the build logs in my own logging solution.

It would be fine if this was achieved through catting out the build log at the end of the runner's lifecycle, or with a unique format compared to the runner's own internal logging.

I scanned through the helm chart looking for some way to achieve this but was unable to find anything that would make the build logs available to me.

Why is this needed?

The GHA UI for accessing build logs can be clunky and more difficult for us to query against than our standard logging solution for our Kubernetes clusters.

Additional context

It seems typical for CICD solutions to allow build log storage through custom logging solutions through standard out.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Helm chart and the runner lifecycle or logging configuration to determine where build logs from the GitHub Actions UI could be exposed through pod standard output. Check how runner logs are currently emitted and define a distinguishable format for build logs. Done means build logs are available in pod stdout for collection by a Kubernetes logging solution.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go, kubernetes
Domain
ci-cd, infrastructure, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.