MDBF-857 - Volume mounts for File/Upload steps #662
Merged
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
Some factories are using the File/Directory upload steps to move files from the worker to CI. The data is transferred to the master which is then in charge of writing the files to destination on the host, meaning hz-bbm[1,2]. In order for this to work, the paths (from hz-bbm) should be mounted inside the container. So far the following factories were identified: -> f_asan_ubsan_build -> f_big_test -> f_asan_ubsan_build -> f_valgrind_build -> f_windows -> f_windows_msi Windows is defined by non-latent master which has already the path mounted. The rest of the factories are defined in master-docker-nonstandard 1 and 2. For Linux builders is it possible to use a network file share but we will not cover this for the migration but taking a note for future refactoring.
vladbogo
approved these changes
Dec 12, 2024
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.
Some factories are using the File/Directory upload steps to move files from the worker to CI. The data is transferred to the master which is then in charge of writing the files to destination on the host, meaning hz-bbm[1,2].
In order for this to work, the paths (from hz-bbm) should be mounted inside the container.
So far the following factories were identified:
-> f_asan_ubsan_build
-> f_big_test
-> f_asan_ubsan_build
-> f_valgrind_build
-> f_windows
-> f_windows_msi
Windows is defined by non-latent master which has already the path mounted. The rest of the factories are defined in master-docker-nonstandard 1 and 2.
For Linux builders is it possible to use a network file share but we will not cover this for the migration but taking a note for future refactoring.