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>
That special case tries to tag a sdk container with `x86/64` where th
`/` is not allowed in a name. Replace it via `tr`.
Signed-off-by: Paul Spooren <mail@aparcar.org>
THe recent changes were a bit short-sighted, not putting into
consideration all labels and different behaviour during testing. This
final commit should fix building for all versions, be it snapshot, a
release snapshot or a regular point release.
Signed-off-by: Paul Spooren <mail@aparcar.org>
GitLab CI seem to lose some variables when creating downstream jobs,
revert the changes back to use the job name for target/arch and apply
the rule to SDK testing.
Remove leading `deploy` from build jobs so they are better readable in
the GitLab UI. Use the leading build name as TYPE variable, so that SDKs
are not labeled on target base and imagebuilder/rootfs is not labeled
based on arch.
For `generate_targets.sh`, instead of exporting BRANCH as env variable,
use functions.sh to set it automatically. Export the `VERSION` one
globally instead of for each downstream job. This works after removing
the `gitlab-ci.yml` variable which would previously overwrite
(strangely) the downstream job settings.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Instead of extracting ARCH/TARGET from the build name explicitly export
the variables to simplify the code. If not, it requires extra handling
for tagging which nulls the "simplification".
Signed-off-by: Paul Spooren <mail@aparcar.org>
* add a functions.sh file containing functions used by all three
container types, ImageBuilder, SDK and rootfs.
* allow SDK branch tags for other branches than `master`. This allows
testing of release SDK versions
* Fix handling of special snapshot versions like `21.02-SNAPSHOT`
Future commits will move `docker-download.sh` and `docker-build.sh` do
`functions.sh`.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Paul Spooren
Paul Spooren
Andrey
Petr Štetiar
Nick Hainke