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>
The VERSION variable is still missing in downstream jobs even though the
documentation states it could be added like that. Add the VERSION to the
trigger job and also quote it, to avoid possible YAML parsing issues.
Adding a *depend* to the triggered job makes the CI report the
downstream success state instead of instantly marking the upstream job
as success. Meaning, if a downstream SDK or IB job fails, the upstream
job is marked as failed.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Neither pipeline nor global variables are passed to downstream jobs, add
them individually per job even if it is always the same version.
Signed-off-by: Paul Spooren <mail@aparcar.org>
GitLab calls dynamically created jobs "downstream". They don't seem to
inherit any env variables from the main CI job, therefore add the
VERSION variable specifically.
Signed-off-by: Paul Spooren <mail@aparcar.org>
The `dumpinfo.pl` script is now part of upstream openwrt.git but was
renamed to `dump-target-info.pl` to have a more verbose name.
Reflect that in the `gen_targets.sh` scripts.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Instead of having a hard coded list of available targets, this approach
makes use os the dumpinfo.pl script that automatically finds available
targets existing in the OpenWrt buildroot. The advantage is to
automatically adapt to available targets in different branches.
Additionally the tagging of SDK containers is improved. While it is
still possible to use SDK based on target tag, it is now also possible
to chose the target based on architecutre. This way less SDK container
are build as one architecutre covers multiple targets.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Paul Spooren