coreos / coreos/coreos-assembler
support logging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 193
- Avg merge
- 17h 6m
- Merged PRs (30d)
- 5
Description
This is strongly related to https://github.com/coreos/coreos-assembler/issues/668
I think we should at least optionally support co-locating logs with our builds. As of today we don't really have a "configuration file" for cosa; could be an enviroment variable like env COSA_LOG=true or so?
And we'd need to bikeshed a bit about the log file layout; is there one buildlog.txt or is there logs/$artifact.txt etc. Today the RHCOS pipeline at least invokes cosa buildextend-$x concurrently so that argues for separate logs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading related issue #668 and tracing the cosa buildextend-$x entry point, especially how concurrent invocations currently handle output. Define the optional logging configuration and log layout, including whether concurrent artifacts need separate files. Done means the behavior and file layout are agreed and documented by tests or examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100