posit-dev / posit-dev/images-shared
feat: parallelize hadolint execution across Containerfiles
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 22
Description
Summary
HadolintSuite.run() (posit-bakery/posit_bakery/plugins/builtin/hadolint/suite.py) groups hadolint commands by unique Containerfile, then runs subprocess.run(...) serially in a for loop — one lint invocation per unique Containerfile. This is a straightforward candidate for the tool-agnostic posit_bakery/parallel/ module (ParallelShellExecutor/ShellTask) introduced in #588 for parallel dgoss execution.
Scope
- Port
HadolintSuite.run()to buildShellTasks from the groupedHadolintCommands and dispatch throughParallelShellExecutor, following the pattern inplugins/builtin/dgoss/suite.py. - Add a
--jobs/-jflag to the hadolint lint command, matching thedgoss run --jobsconvention (BAKERY_MAX_CONCURRENCYenv /SETTINGS.max_concurrency, default 4). - Preserve existing per-Containerfile report/result-file writing and error aggregation (
BakeryHadolintError,BakeryToolRuntimeErrorGroup) exactly as-is; only the dispatch mechanism changes. - Update/extend the live progress table behavior to match dgoss (auto-disable on non-TTY/CI/
--quiet/single-task runs).
Out of scope
- Changing hadolint's actual lint rules or output format.
Part of the investigation started in #584. See #588 for the reference implementation pattern (dgoss).
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 posit_bakery/plugins/builtin/hadolint/suite.py, then read posit_bakery/plugins/builtin/dgoss/suite.py and the posit_bakery/parallel/ module, especially ParallelShellExecutor and ShellTask. Run the hadolint lint command to inspect current behavior; done means grouped Containerfiles execute with configurable --jobs/-j concurrency while report writing, error aggregation, and dgoss-aligned progress behavior remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100