This change required some changes to the current test scripts. Most notably, the
whole conversion is now run two times. One for the compressed input image, and
one for the already decompressed image.
Also, the test framework was cleaned up significantly, and the number of
arguments passed to the 'convert_and_test' function has been decreased to remove
the redundancies that were present (like passing the image name, and the image
name with the extension, in two separate parameters).
These changes are a result of the changes introduced with:
* MEN-3052: https://tracker.mender.io/browse/MEN-3052
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
This may not be correct in all use cases but for the files that are currently created,
they should be owned by root. At a minimum they should not have the UID of the user
invoking mender-convert.
Changelog: Title
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
This image is old enough to have a U-Boot version from before the boot
problems in MEN-2404 were introduced (>= v2018.09). At the time of
writing, no image has been released which has a U-Boot from after the
problem was fixed (> v2019.07), but we expect it will eventually be
released, and then we can bump to that version.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This change retains the name of the converted input image, and adds the device
type and a mender suffix, so that the user can both recognize the converted
image, and is aware of what the device the converted image supports.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@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>
This is done to aling with the internal naming conventions we are using when
testing other images of the same type, which has the `.sdimg` naming extension
in our Yocto setup.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@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>
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>
Previously there was a mix between two, and four spaces.
This commits unifies all scripts to use two-spaces for indentation.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@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 mirrors the way it is handled in Yocto with the demo server, the production
server, and hosted mender.
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
Changelog: Title
With these changes we will additionally cover test with:
- MENDER_COMPRESS_DISK_IMAGE set to 'y' and 'n'
- multiple --config files
- no external configuration files (no '--config' options)
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
The images are very big, and the default donwload withouht TTY (used by
CI) adds a lot of noise in the logs.
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>
The goals of the re-write was to achieve the following:
1. It should be easy to extend the tool to support other boards or distributions
2. We should not compile code in the tool (rely on binaries built elsewhere)
compiling code increases complexity, due to requirement of toolchains etc.
3. The tool shall not be designed around specific hardware/platform types
- This is the case today with the usage of --device-type flag
4 The tool should be to convert images without knowing anything about the hardware/platform
relates to above 3.
5. Configuration interface should be simplified
- command line flags -> configuration files
6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code
7. It shall be easy to extend functionality
- support for rootfs overlay to inject user applications/configurations
- ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts)
8. Code structure should be modular
- Eases Maintenance and possibility of making isolated changes
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Peter Grzybowski
Ole Petter
Drew Moseley
Kristian Amlie
Lluis Campos
Alf-Rune Siqveland
Mirza Krak