Tree: 69da759609

1.0.x

1.1.x

1.2.x

2.0.x

2.1.x

2.2.x

2.3.x

2.4.x

2.5.x

2.6.x

2.7.x

3.0.x

4.0.x

automatic_bootstrap_artifact

change-dependabot-prefix

create-pull-request/patch

master

patch-1

pr_475

revert-252-rm-only-tag-2.2.x

1.0.0

1.1.0

1.1.1

1.2.0

1.2.1

1.2.2

2.0.0

2.0.1

2.1.0

2.2.0

2.2.1

2.2.2

2.2.2-build1

2.3.0

2.3.1

2.4.0

2.5.0

2.5.2

2.5.3

2.6.0

2.6.1

2.6.2

2.7.0-build1

3.0.0

3.0.1

3.0.2

4.0.0

4.0.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '69da759609'

${ noResults }

Commit Graph

4 Commits (69da7596094456a6f2b88aef65de56aedac24e8c)

Author	SHA1	Message	Date
Kristian Amlie	2f8c0331e5	test: Make launching script independent of current folder. Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>	3 years ago
Kristian Amlie	1b3ab7c5e0	MEN-5255: Enable and start testing Secure Boot. This is using pre-signed binaries by Microsoft, Canonical and Debian, no customized signing. Changelog: None Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>	3 years ago
Kristian Amlie	245930608b	MEN-5219: Integrate with `grub.d` framework. This means that `grub-install` and `update-grub` no longer risk bricking the device, but will produce boot scripts with Mender support integrated. It also means that the standard GRUB menu will be available. It is supported on x86_64 platforms where `grub.d` is available, and can be turned on and off with `MENDER_GRUB_D_INTEGRATION`. The default is to use it if available. Devices that did not previously use `grub.d` integration won't be upgraded correctly with it turned on, so it is advised to set `MENDER_GRUB_D_INTEGRATION=n` if you are upgrading existing devices. Changelog: Commit Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>	3 years ago
Lluis Campos	babc77ff1c	MEN-2208: Run test_update tests for meta-mender QEMU image 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>	4 years ago