Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TCB tests to run on latest TOS versions/ Be able to run AVAL on kirkstone #43

Open
wants to merge 8 commits into
base: bullseye
Choose a base branch
from

Conversation

lucasbernardestoradex
Copy link
Contributor

Related-to: AVAL-18
Related-to: TCB-502

…ned images

Previously, get_tezi_images was downloading specific images, that had
the versions hardcoded on script. This commit changes this to download
the latest release, monthly or nightly.
Also, it's possible to define the YOCTO_BRANCH to request a specific
version of Torizon, e.g. 'kirkstone-6.x.y' and 'scarthgap-7.x.y'.

Related-to: AVAL-18

Signed-off-by: Lucas Bernardes <[email protected]>
…ested

Previously, the script was downloading images for all modules. This way,
it download only the image for the device wich are beeing tested.

Related-to: AVAL-18

Signed-off-by: Lucas Bernardes <[email protected]>
Related-to: AVAL-18

Signed-off-by: Lucas Bernardes <[email protected]>
A logic of dependency is already made by using the "stages" on gitlab-ci, so
duplicate this using "needs" is not necessary.

Signed-off-by: Lucas Bernardes <[email protected]>
This way it's possible to use the latest images, insted of having the
version of images hardcoded.

Related-to: AVAL-18

Signed-off-by: Lucas Bernardes <[email protected]>
…ed match

This test verify if the image installed on device, wich is beeing used
for the tests, is the same of the one downloaded on the host PC that is
running the test.

Related-to: TCB-502

Signed-off-by: Lucas Bernardes <[email protected]>
The jobs made in 'test-paltform' don't have dependencies with 'test'
stage, so this additional stage is unnecessary.

Signed-off-by: Lucas Bernardes <[email protected]>
The default docker:latest image is already adequate to build this AVAL
container, so it's not necessary to force the use of docker:dind.

Signed-off-by: Lucas Bernardes <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant