docker / docker/github-builder
Create a way to adjust BUILDKIT_STEP_LOG_MAX_SIZE
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 83
- Forks
- 23
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
It would be great to be able to specify the log size and rate limits.
env.BUILDKIT_STEP_LOG_MAX_SIZE
env.BUILDKIT_STEP_LOG_MAX_SPEED
About the worst thing you can do when a build is taking longer than expected is to drop the logs that would tell me why. The longer it takes and the more logs, the greater the lost time trying to repeat it to identify the problem.
As it stands, I need a separate job to adjust these unless I am missing something.
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 with .github/workflows/build.yml at lines 529-532 and inspect how the reusable workflow exposes and passes configuration into the BuildKit build. Trace the existing environment setup, then determine how users can provide BUILDKIT_STEP_LOG_MAX_SIZE and BUILDKIT_STEP_LOG_MAX_SPEED. Done means both limits can be configured without a separate job and the workflow remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100