The latest package does not have the Debian version suffixed.
Therefore, simply remove it in the case where it is needed.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
The 'latest' tag is always pointing to the latest released Mender-client.
Therefore it is no longer necessary to update the client version on release.
Changelog: Package latest released Mender-client by default
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
This new keyword of GitLab allows for jobs in further stages start as
soon as their dependencies are done.
This should speed-up this pipeline, starting most of the acceptance
testing without finishing to the raspberrypi conversions.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
This commit adds all necessary bits to be able to execute runtime tests
for mender-convert'ed QEMU x86_64 image. Namely:
* Install SSH key as an authorized one on the device using an overlay,
and pass the private one to be use by the test framework.
* Create a QEMU launcher wrapper, similar to the one in meta-mender, for
the test framework to use in order to start/stop the virtual device.
* Exclude the test_update tests for all configurations but Ubuntu QEMU
one using a pytest filter 'not test_upate'.
* Copy from meta-mender the keys required for test_signed_updates.
* Install mender-artifact in CI to be used in tests.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
As the test framework copies files from meta-mender into the submodule
directory.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
As probe_initrd_in_boot_and_root indicates, this is not always required.
Adding the check for the ln not to throw an error.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Respecting this way always the input type (compressed or not) by
default, allowing the user to override behaviour if desired.
For the tests, removed the unnecessary duplication on rerunning all
tests on uncompressed versions, and added instead an explicit test only
for qemu-x86_64.
Changelog: Title
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
The default behavior is not changing, but splitting the arguments in
prepend/append allows the user to override the output image compression.
Changelog: Title
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Remove all the logic for the special handling of this submodule, and
treat it instead a regular Git submodule.
This commit updates the submodule to latest, removes the --no-pull
functionality, and removes the ignore of the submodule to make
developers aware
To ease maintenance, add also dependabot to pay attention to the future
updates of the submodule.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Originally the intention was to fix the U-Boot integration for
Beaglebone, but this seems to have been broken for a long time, almost
a year, and no one has complained about it. The problem appears to be
connected to this commit [1], but it's not entirely clear to me what
the fix should be, and there are a lot of patches for our U-Boot fork.
However, since the U-Boot integration is supposed to be the backup
solution, rather than dig into U-Boot I decided to just fix the UEFI
path instead. This method doesn't require any patching, but there is
a problem with the specific image which is available for download at
the time of writing. So just grab the boot loader and kernel pieces
from a later, yet unbuilt, image, and it all works again.
Changelog: Title
Changelog: beaglebone: Remove U-Boot integration, which has not worked
for a long time. U-Boot will still be used for booting, but GRUB will
be used for integration with Mender, by chainloading via UEFI.
[1] e88d5dbf01
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
Sounds scary, but it happens at build time, not runtime, so it cannot
brick devices. However, it was a frustrating exercise to uncover it,
as it is not entirely deterministic. This has been there for quite a
long time and I honestly cannot tell why it happened to me now.
Perhaps the exact location of the sparse holes on the filesystem makes
a difference. Or perhaps some versions of mkfs can handle it, others
not. All I know for sure, is that with `sparse` enabled I got massive
filesystem corruption (though sane enough to be somewhat readable) on
the rootfs. Without it, it's clean.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
... not just for EFI configuration. This doesn't fix any immediate
problems, but some U-Boot configurations seem to make a reference to
this, so this is just being proactive.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
Because we hardcode the name in the boot loader script, you can never
upgrade to a kernel with a different version string. Fix by using a
generic name and symlinking instead.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
So that we clean the deprecation warning and the multiple errors when
calling this command from CI.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
oleorhagen
Lluis Campos
Kristian Amlie
Kristian Amlie
Alin Alexandru
Drew Moseley