Skip to content

General Wrynose, KAS, GitHub Workflows, Pre-Commit maintenance on repo - #220

Merged
mikehaller merged 16 commits into
wrynosefrom
cleanup-kas-configs
Oct 23, 2026
Merged

mikehaller merged 16 commits into
wrynosefrom
cleanup-kas-configs

Conversation

@mikehaller

Copy link
Copy Markdown
Contributor
  • Removing unnecessary and obsolete GitHub Workflows, as required infrastructure is no longer available (e.g. persistent caching on Azure, selfhosted GitHub runners and bitbake hashserv container)
  • Cleaning up obsolete KAS configs, e.g. for EOL Yocto releases (honister, kirkstone). Dropping Yocto 5 Scarthgap compatibility in this wrynose branch.. For scarthgap, use scarthgap branch.
  • Adding pre-commit hooks for linting typical files (markdown, toml, json, yaml, shellcheck etc.)
  • Evaluating oelint_adv for advanced BitBake linting of recipes

Validate the kas and GitHub workflow YAML and the Markdown documentation
before they are committed. The rule set is relaxed for prose style rules that
clash with the Eclipse boilerplate, see docs/pre-commit.md.
The scarthgap dry-run fails: packagegroup-sdv-core pulls crun -> wasmedge,
which DEPENDS on lld, and no lld recipe exists in oe-core or meta-clang for
scarthgap. meta-virtualization for scarthgap has no containerd recipe either,
so the meta-leda bbappends for lld and containerd are left dangling.

Remove the scarthgap kas config and list only wrynose in LAYERSERIES_COMPAT,
document the resulting release and machine matrix in docs/ci-build-matrix.md.
Keep the working curated rulefile, the layer constants file and the recorded
findings in docs/oelint-adv-eval so the evaluation can be repeated. The
linter itself stays out of pre-commit and CI for now.
Installing pre-commit with sudo pip3 into the interpreter of the runner fails on the ubuntu runners: pip there is patched to uninstall the packages the distribution ships first, and pre-commit depends on packaging, which is shipped as python3-packaging. That uninstall has no RECORD file to undo, so pip exits with an error and the job aborts. The upstream action installs into the interpreter of actions/setup-python instead, and caches ~/.cache/pre-commit.
A push to a branch that has an open pull request fires both the push and the pull_request event, so the unscoped push trigger started a second identical run of the job. The pull_request trigger already covers every push to a pull request, including the ones from forks, and workflow_dispatch covers the cases where a maintainer wants a run for a branch. A direct push to a release branch (main, wrynose, scarthgap, ...) is not checked in CI any more: the maintainer runs the same commands locally before pushing, and the change is checked by the next pull request that touches it. The docs of both workflows are updated to match.
@mikehaller
mikehaller marked this pull request as ready for review October 23, 2026 15:31
@mikehaller
mikehaller merged commit 005e835 into wrynose Oct 23, 2026
3 checks passed
@mikehaller
mikehaller deleted the cleanup-kas-configs branch October 23, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant