Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Run scheduled jobs via workflow_dispatch #57

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

hnez
Copy link
Contributor

@hnez hnez commented Sep 13, 2024

We currently only test the master branch on a regular schedule and not the different release branches (like e.g. scarthgap).

Also testing these other branches is complicated by the following detail in the GitHub action documentation:

Scheduled workflows will only run on the default branch

This means we need some sort of workaround to run scheduled jobs on different branches. This commit adds a scheduled job on the master branch to trigger jobs on other branches via the workflow_dispatch event.

TODO before merging:

  • Update the scarthgap build job to match the master build job (run on self-hosted runner and allow workflow_dispatch)¹.
  • Update the kirkstone build job to match the master build job (run on self-hosted runner and allow workflow_dispatch)¹.
  • Set the SCHEDULE_BUILDS variable to a true-ish value.

¹ The git clone commands for poky and other meta-layers need to be adapted.

…spatch

We currently only test the master branch on a regular schedule and not the
different release branches (like e.g. scarthgap).

Also testing these other branches is complicated by the following detail
in the GitHub action documentation[1]:

> Scheduled workflows will only run on the default branch

This means we need some sort of workaround to run scheduled jobs on
different branches. This commit adds a scheduled job on the master branch
to trigger jobs on other branches via the `workflow_dispatch` event.

[1]: https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule

Signed-off-by: Leonard Göhrs <[email protected]>
Scarthgap is the most recent yocto release.
Scarthgap will also be a LTS release that is supported until April 2028.

Signed-off-by: Leonard Göhrs <[email protected]>
Kirkstone is a yocto LTS release that is supported until April 2026.

Signed-off-by: Leonard Göhrs <[email protected]>
Not anyone who creates a fork of the project may want to run jobs on a
schedule. Gate scheduled runs via a GitHub action variable.

Manual triggering of the job via workflow_dispatch is not affected by the
variable.

Signed-off-by: Leonard Göhrs <[email protected]>
@hnez
Copy link
Contributor Author

hnez commented Oct 18, 2024

Hi, is this something we want?
Then I would prepare PRs against the scarthgap and kirkstone branches to make use of the self hosted runner and to allow workflow_dispatch.

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