This commit moves containerd, cri-tools, docker, docker-cli and
docker-proxy from app-emulation to app-containers.
Also move app-emulation/docker-runc to app-containers as runc. The
docker-runc name seems to be an artifact from the older versions of
docker, where it needed to use a fork of runc instead of upstream. But
now, docker-runc was actually using upstream code, so simplify the
name now.
Adapt all the other files to the new package names.
This change includes 2 unrelated small fixes to the "PR comment command"
build+test feature:
1. The concurrency group now contains the PR number, ensuring that
builds for multiple PRs can run in parallel. This addresses an issue
in which starting a build on a PR would cancel a running build of
another PR.
2. Post test results to the PR where the build command was issued on.
The add-pr-comment step's condition was not updated when switching
to PR comment commands for starting builds, so the step would only
run if the action was triggered by a PR change event. Since we now
trigger on issue_comment, the step never ran.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
This change updates dispatching of SDK and OS image builds from changes
to a PR to an explicit comment. PRs will only be built if that comment
was added by a member of the Flatcar maintainers team.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
This change is a building block for PR builds triggered by PR commands.
It checks for membership of the commenter in the Flatcar Maintainers
team.
Note that the "issue comment" event (which is also triggered on PR
comments) is only emitted to workflows in the "main" branch. So in order
to test / trigger this workflow, a transient "PR update" event is used,
and the "commenter" user's login is hard-coded for testing.
This will be updated to using the actual commenter's login before merge.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
This change adds a github actions workflow to build a new SDK container
based on an existing SDK container. This can be used for CI testing
intrusive changes that also affect the SDK without bootstrapping a whole
new SDK.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
git show-ref in check_remote_branch is not working at all, because the
GitHub Actions checkout fetches a git repo with only depth 1 by default.
That means only main branch is available, not any other remote branches.
As a result, git show-ref always fails.
Fix that by checking for remote branches by git ls-remote.
