On some RPi3 images, e.g Ubuntu Server there is no resize init script,
and these commands would fail trying to convert such an image.
This can also be useful on Raspbian images, if they have been booted
once before they are converted using "mender-convert"
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@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
And drop the workaround.
This includes only one change:
2a8a20f01d4 Disable addition of simple-framebuffer by U-boot
Fixes: MEN-2685
Changelog: Fix "yellow" HDMI output on Raspbian Buster
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
This includes only one change:
2a8a20f01d4 Disable addition of simple-framebuffer by U-boot
Fixes: MEN-2685
Changelog: Fix "yellow" HDMI output on Raspbian Buster
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
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>
Current logic actually fails when no '-c/--config' options are provided, with this error:
$ MENDER_ARTIFACT_NAME="test-1" ./mender-convert --disk-image input/Armbian_5.95_Tinkerboard_Debian_buster_next_4.19.69_minimal.img
Running mender-convert-extract: --disk-image input/Armbian_5.95_Tinkerboard_Debian_buster_next_4.19.69_minimal.img
2019-10-02 12:46:39 [INFO] [mender-convert-extract] Using configuration file: configs/mender_convert_config
2019-10-02 12:46:39 [INFO] [mender-convert-extract] Using configuration file: ''
modules/config.sh: line 28: '': No such file or directory
The 'configs' array is actually not empty when passed to modules/config.sh
as it will contain "''", which will be translated as a array element and
hence the above failure.
This commit ensures that we set a valid default value to 'configs',
which is the 'mender_convert_config'. This is moved from modules/config.sh,
to the calling scripts that define the array of configs.
Fixes: 9b944615a8 ("configs: Support multiple config files on command line.")
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 reason for having a bind mount is unknown. In order to be able to
run this container fom inside another, the directory must be a volume.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
The current support for this fails due to incorrect use
of bash arrays.
Also, use the printf '%q' formatting code to add proper quotes
to the config file names to ensure that it works properly
with spaces in the file names.
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
Changelog: Title
This can be used for local config settings intended to override the defaults in
configs/
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
Changelog: Title
So that GitLab CI script (or any user, really) can customize the name of
the resulting Docker image.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
It was pointing to a resource on mender.io, which duo to recent
website updates was moved/removed.
Update the URL to use the logo that is present in mendersoftware/mender,
which hopefully will not move as much.
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
It was pointing to a resource on mender.io, which duo to recent
website updates was moved/removed.
Update the URL to use the logo that is present in mendersoftware/mender,
which hopefully will not move as much.
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@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>
Use losetup's automatic allocation mode to atomically find and allocate loop devices. This should make mender-convert safer to use concurrently with itself and other applications allocating loop devices.
Changelog: Title
Signed-off-by: Simon Guigui <fyhertz@gmail.com>
Current stable version 3.0.x should be the transition, as for future
versions we will be releasing the binary in a linux/darwin folder.
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>
This file needs to be present for state-scripts to work as the format
version will be validated using the information provided in this file
and the version in the Mender Artifact.
"3" means that it will only accept state-scripts created using
Mender Artifact version 3.
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>