db update #1
Open
db update #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To be able to load the tests DB folders, make the DB path a parameter of the executable.
In this test the tool osbuild-image-test run against two databases. The first one containing a successible test case and the second one a faulty test cases that will fail upon comparison of the image-info.
This tool can be used to update the manifest-db from a gitlab ci pipeline. CI pipelines are building all the possible manifest with the Schutzfile's version of the CI. Thus, after a new run, we can use this script to update the database. Usage; Firstly, run ci_import at the root of the manifest-db project: ./tools/ci_import --pipeline-id $pipelineid --token your-gitlab-token Finally you can commit the modifications made to the test cases.
Some UUIDs are not fixed in the manifest. Therefore, ignore it at comparison time. Lvm2 and CD partition's UUIDs are concerned.
The import tool can now only update the manifests from composer instead of before importing manifests and image-info. This is good because the image-info on composer are sometimes outdated and we don't want to override our lately generated image-info with noise.
Some of the manifests coming from Composer produce images that are non explorable by the image-info tool. Add a way to not import this well known set with a db-ignore file that the root of the project containing all the faulty items to not import.
First a github action pulls the new manifests from composer. Creates a commit out of the modification and pushes these to the gitlab repository on a specific branch. Then it triggers a pipeline using the trigger token. Then the CI runs in "trigger" mode. In this mode it will compile all the new manifests and produce the corresponding image-info in the artifacts. Once this is done, in the final phase the CI will download all the produced image-info and ammend the update db commit with them. Then it will push that on github and open a PR.
Automatic update: - manifests from latest composer - image-info from pipeline 604788399
|
This PR needs to be closed, it was not opened at the right place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
automated db update