CI: add build test images to ghcr.io

[jordimassaguerpla]

What does this PR change?

This is the first step to fix https://github.com/SUSE/spacewalk/issues/25948 We need the test images in ghcr.io so we can pull them and push them to the authenticated and non-authenticated registries that we use when running tests that build container images based on the content of the registries.

It is important that the images are in ghcr.io, because we do not want to pull images from the opensuse mirror infrastructure, nor docker hub, during the test. First, for stability, second, because there are rate limits.

GUI diff

No difference.

• DONE

Documentation

• No documentation needed
• DONE

Test coverage

ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite

• No tests

• DONE

Links

Issue(s): https://github.com/SUSE/spacewalk/issues/25948

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "javascript_lint"
• Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

[github-actions]

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (aprox. 1h), please be patient ☕

You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/9843/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/9843/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary_parallel.yml?query=event%3Aschedule

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary.yml?query=event%3Aschedule

KNOWN ISSUES

Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience.

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!
⚠️ You should not merge if acceptance tests fail to pass. ⚠️

[nodeg]

Just out of curiousity, why do we not use Leap 15.6 or at least 15.5?

[jordimassaguerpla]

no idea. I am using what we are already using at the other build profiles.

[jordimassaguerpla]

@srbarrios I plan to split it into 2 PR, one that adds the images to the ghcr.io, and one that uses that, so we do not break anything.

[jordimassaguerpla]

Split into 3 PRs:

#9851
#9852
#9853