actions
Build Logs to Standard Out
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.
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
+1 for this. To expand a bit, I know that the controller logs end up on stdout and that parts of the runner logs also end up on stdout. If we could also pipe the actual job logs to stdout, then we can export and aggregate them in ELK, Splunk, etc. for longer retention and for analysis. For example, finding test cases that are particularly prone to failure, identifying roughly when a particular test started to fail, etc.
Hi @nikola-jokic and @Link-, hope your day is going well and also hope ya'll don't mind me pulling you into this issue. I would also love this feature, is there anything I can do to help with triaging / moving this forward?
Thanks in advance! 😄
If we add a setting into the runner to let it dump all workflow log into a file, then you can keep reading the file and pump it to anywhere you want in your runner container, will that cover your feature request?
