Skip to content

ci: add daily 15:00 PST kernel build - #29

Closed
Bjordis Collaku (bjordiscollaku) wants to merge 1 commit into
mainfrom
ci/daily-kernel-build
Closed

Bjordis Collaku (bjordiscollaku) wants to merge 1 commit into
mainfrom
ci/daily-kernel-build

Conversation

@bjordiscollaku

@bjordiscollaku Bjordis Collaku (bjordiscollaku) commented Jul 7, 2026 •

Copy link
Copy Markdown
Contributor

Adds a daily scheduled build so the resolute-qcom-devel integration branch gets
a fresh .deb uploaded to S3 every day at 15:00 PST (23:00 UTC).

What it does

A tiny scheduled dispatcher (daily-build.yml) that fires the existing
build-kernel.yml once a day with suite=resolute-qcom-devel. It builds nothing
itself - it just triggers the normal build, exactly like clicking "Run workflow".

  • Schedule: cron: "0 23 * * *" = 15:00 PST.
  • Builds: resolute-qcom-devel HEAD, uploaded to S3 (same path as a manual build).
  • Also exposes workflow_dispatch so the daily build can be run on demand.

Why a dispatcher, not a schedule: on build-kernel.yml

A scheduled event carries no inputs, and build-kernel.yml's S3 upload is
gated on the runner input - which is empty under schedule, so a bare scheduled
run would build but upload nothing (and SUITE would fall back to resolute-qcom,
not the intended branch). Dispatching passes suite explicitly, so the scheduled
build behaves identically to a manual run. It also touches no existing file, so it
does not conflict with the in-flight build-kernel.yml rework in #25.

To change what it builds

Edit the single --field suite=... line - e.g. set resolute-qcom to build the
mirror instead of the integration branch.

Adds daily-build.yml: a scheduled dispatcher that fires build-kernel.yml once a
day (cron 0 23 * * * = 15:00 PST / 23:00 UTC) with suite=resolute-qcom-devel, so
the integration branch gets a fresh .deb build uploaded to S3.

Dispatches rather than adding a schedule trigger to build-kernel.yml directly: a
scheduled event carries no inputs, so build-kernel.yml's S3 upload (gated on the
runner input) would not fire on a bare scheduled run. Passing inputs explicitly
behaves identically to a manual Run workflow, and touches no existing file.

Signed-off-by: Bjordis Collaku <bcollaku@qti.qualcomm.com>
@bjordiscollaku

Copy link
Copy Markdown
Contributor Author

Superseded: folded the daily build into #25 as a 2-line schedule: trigger on build-kernel.yml. Its reworked version handles a no-input scheduled run correctly (defaults to resolute-qcom-devel, null-safe S3 upload), so no separate dispatcher workflow is needed.

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