If a TARGET_FILTER is set only imagebuilder/sdk/rootfs for that target
are created. In case of the SDK multiple valid targets are in the same
row printed via `dump-target-info.pl`. With the previous logic the
"first" target is used expecting all targets to be on the same commit.
However when using TARGET_FILTER the specific target should be used for
the SDK, not just one that supports the same architecture.
A logic is added that if TARGET_FILTER is set, it's used as the SDK
target.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Previously the container would use downloads.openwrt.org aka mirror-02
which has a short delay on images. This would break webhooks since they
fire one ready on mirror-01 while not yet fully transferred to mirror-02.
Signed-off-by: Paul Spooren <mail@aparcar.org>
22.03 snapshots appear to be built on weekends, so shifting builds to
Tuesdays should allow the Docker images to package the newest snapshots
more consistently.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
Continue to accept "master" for manual releases, and add "master"
suffixed tags for main branch images, for backwards compatibility.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
Add the condition on the step level and not the push action. This way
it's clear nothing got pushed from the CI overview.
Signed-off-by: Paul Spooren <paul.spooren@rhebo.com>
Instead of using a definied list with an if condition, use a case
statement with wildcards to match on either `armsr` or `armvirt`
(legacy). This should keep support for both 23.05.x and newer releases.
Signed-off-by: Paul Spooren <paul.spooren@rhebo.com>
* Set the platforms argument to docker/build-push-action.
* Insert a minimal *is it runable* test in between building and pushing
the rootfs images.
Fixes#112.
Those usernames are not really secret but should be possible to set to
whatever value seems suited.
Signed-off-by: Paul Spooren <paul.spooren@rhebo.com>
Docker is sunsetting free stuff so we drop pushing to openwrtorg, use
openwrt instead. Also don't use the `rootfs` for anything real.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Otherwise it would use runner default, which might be unpredictable, as
for example GitLab provided public runners are using `ruby:2.5` as
default container image, but true.cz runners are using `debian:10`. So
lets fix it by using Debian 11 image by default.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Fixes following issue:
+ perl ./scripts/dump-target-info.pl architectures
+ read -r LINE
sh: 1: make: not found
As apparently `make` got removed from the upstream base Debian containers.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Fixes following issue:
+ git clone --depth 1 --branch master https://github.com/openwrt/openwrt.git
./generate_targets.sh: line 7: git: command not found
As apparently `git` got removed from the upstream base Debian containers.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
GitLab schedules use `master` as CI_COMMIT_REF_SLUG which causes
unpredictable behaviour when scheduling multiple releases at the same
time. Recently the 19.07 schedule would use 21.02 images for testing,
which succeeded even though it would fail on actual 19.07 containers.
A simple workaround is to attach the $CI_PIPELINE_ID to the test
containers. This issue won't happen to PRs since the CI_COMMIT_REF_SLUG
would then be set to the PRs branch name.
Signed-off-by: Paul Spooren <mail@aparcar.org>
The tag allows the CI to test runtime behaviour not only for snapshot
builds but also for branches like 21.02.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Node fails to compile with:
In file included from /usr/include/c++/8/memory:62,
from ../deps/v8/src/libplatform/default-foreground-task-runner.h:8,
from ../deps/v8/src/libplatform/default-foreground-task-runner.cc:5:
/usr/include/c++/8/bits/stl_algobase.h:59:10: fatal error: bits/c++config.h:
No such file or directory
#include <bits/c++config.h>
^~~~~~~~~~~~~~~~~~
compilation terminated.
Add g++-multilib to fix this.
Fixes: https://github.com/openwrt/packages/issues/17074
Signed-off-by: Nick Hainke <vincent@systemli.org>
Packages like `python3-pip` are installed within the buildbot containers
but not inside this base container. Add them to allow the CI compilation
of more packages.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Paul Spooren
Jeffery To
Paul Spooren
Brénainn Woodsend
Andrey
Petr Štetiar
Nick Hainke