secrets: inherit can only be used with workflows that call reusable
workflows in the same organization. In this case since we reuse a
workflow from 96boards, we need to be more explicit.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Add an additional OE RPB build for each new meta-qcom PR, to ensure
that the PR is not breaking the OE RPB build.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
artifacts now accepts a list of path relative to deploy_dir
to publish after the build. All the files from deploy_dir
are published if artifacts field is an empty list.
Signed-off-by: Vishal Bhoj <vishal.bhoj@linaro.org>
Tux had a convenient bug that allowed us to use a 'ref' type with a
SHA. This bug was fixed, so we need to make sure that we use a type
'sha' in the Tux plan when we use a SHA value.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
As per Github Actions documentations, "Scheduled workflows run on the
latest commit on the default or base branch". So let's implement the
daily build in the default branch which triggers plans for all
supported branches.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
For daily builds, using the 'schedule' trigger, the default branch is
being used only. So we need to be able to trigger builds by 'branch'
instead of by 'ref'. ref_type is a new input parameter, so that
calling jobs can decide to use a ref (SHA) or a branch.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
When testing github workflows, it's convenient to use a secondary repo
fork, so let's make sure we don't hardcode the repo name in the
workflow, so that they work in a forked repo (such as meta-qcom-test).
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Use TuxOE plans to submit multiple jobs at once, instead of matrix
build since it uses one Github Action job for each build.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
In addition to testing pull_request events, also test push events. In
order to effectively reuse the template job, a few additional changes
were made, especially the addition of a couple of input params.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Add initramfs-rootfs-image and initramfs-firmware-image to test that occasional changes do not break them too.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Instead of duplicating the same workflow on each branch, let's create
a resuable workflow in the main branch, and reuse it from here.
We leave a few parameters as inputs which need to be set by jobs using
this reusable workflow.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
When using pull_request event, the workflow is run in the context of
the PR, so it's potentially untrusted code from a third party. As such
Github Action secrets are not available for security reason. The PR
build test workflow requires a secret (TUXSUITE TOKEN). So instead, we
can use pull_request_target which ensures the workflow runs in the
context of the base of the PR, e.g. trusted/merged code. In this case
the repo secrets can be used in the workflow.
We just need to carefully set the 'ref' we use in the tuxOE job
definition, which needs to refer to the PR.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
This CI has been implemented on Linaro CI so far, let's migrate to
GitHub Actions. The build uses Linaro Tuxsuite for OE/YP which
provides a cloud based infrastructure.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
