The publishing variables have no prefix, and the tmp storage ones have
a TMP_STORAGE prefix, so adapt to that.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This is a bit unfortunate, but our converted image does not work for
all of them, like the original.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
The current execution of the acceptance tests is too long, in some cases
reaching the GitLab timeout of this project of 2 hours.
Rework the Pipeline to use a template and rework the script to allow
running tests for only one device type.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
The "high privileged" keys will only be available in protected branches,
so we won't be able to publish from a PR even if we run the manual job.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
It turns out we will not use this after all, because the artifact
won't work properly without `mender setup`, which requires a live
device. We will revisit this and use a different approach once the
`mender snapshot` feature has been developed and merged.
This reverts commit 4cfc7bc648.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This makes it a bit more explicit that it is part of the testing
files. It follows the same pattern as in meta-mender with pulling
automatically, and using `--no-pull` to disable it.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This avoid problems when running the tests locally. Technically it
will run the Raspberry Pi test twice on Gitlab, once with the prebuilt
image, and once with a test image, but the two configurations are not
identical, so I reckon that's alright.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This also means using the new mender-gitlab-tmp-storage bucket to
transfer artifacts between stages, because the built in artifact
mechanism has a size cap that we are exceeding.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
Basically install dependencies and modify pytest call. This repo is
using meta-mender master test framework, so the actual tests are already
converted and working fine.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
This is the "new way" to perform such checks, so that any change in the
testing repo does not require an update in local licenses checksum file.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Created a new test_acceptance stage that will execute in our private
runners. This stage will execute scripts/run-tests.sh and collect the
now produced xml/html reports for each device type.
Removed the build from the test script, so that we make sure that CI
tests the exact same image build in "build" stage.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
So there are other arguments that need to be passed to docker build,
namely toolchain related, therefore it is better to use the default
script and just override the image name.
Also, removing the Mender version from the GitLab pipeline (and hence
using the one defined in build-docker) removes one point of
inconsistency.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>