Skip to content

Commit

Permalink
Add more information in README
Browse files Browse the repository at this point in the history
Also allow triggering manual runs.
  • Loading branch information
danobi committed Jan 2, 2025
1 parent c0a7f0d commit 63ca1b7
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 1 deletion.
3 changes: 2 additions & 1 deletion .github/workflows/kernels.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
name: Kernels

on:
push:
workflow_dispatch: # Manual trigger
push: # Automatic trigger
branches: [ "master" ]

concurrency:
Expand Down
28 changes: 28 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,31 @@
# kernels

This repository holds both infrastructure and assets for bpftrace's CI kernels.

We use a [dummy release][1] as an object store.

## Adding a new kernel

To add a new kernel, update [KERNELS][0] with the upstream tag of the version
you want. Examples:

* `v6.12`
* `v6.12-rc7`

Once the change is checked in, automation will build and upload any kernels not
already present in the [Assets Release][1] to the assets release.

## Changing already-built kernels

Automation is not yet smart enough to rebuild and reupload existing assets
affected by a config or infra change. If you want to change an already-uploaded
kernel, delete the impacted kernel from the release assets and trigger a new
run.

You can trigger a new run by going to [the workflow page][2] and following
[these docs][3] to trigger a manual run.

[0]: ./KERNELS
[1]: https://github.com/bpftrace/kernels/releases/tag/assets
[2]: https://github.com/bpftrace/kernels/actions/workflows/kernels.yml
[3]: https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow

0 comments on commit 63ca1b7

Please sign in to comment.