Add additional repository support #469
Draft
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
Make it possible to add additional repo for a kickstart test run. At the moment we assume the repository is a regular RPM repository, as for example created by running createrepo_c on a directory containing a bunch of RPMs. The main aim of this functionality is to make it possible to add additional packages to the RPM transaction Anaconda runs during a regular RPM based installation. Also by adding packages with a higher version number than those in the normal package repositories it is possible to override them with the package from the additional repo. This can be useful to test Anaconda and/or Initial Setup scratchbuilds. To use this feature use the -a or --additional-repo flag to the appropriate runner script and pass either a local filesystem path to a RPM repository or to a remote RPM repository. If a local path is detected a localhost web server on the runner will be used to serve the repo folder to the VM running the test. If a remote path to a RPM repository is passed, it will be passed directly to the VM. In both cases the additional repositories are passed via the inst.addrepo boot option as "inst.addrepo=KSTEST_ADDITIONAL_REPOSITORY,<repo_path>".
M4rtinK
force-pushed
the
master-add_additional_repo_support
branch
from
0263041
to
a92fb91
Compare
| @@ -46,7 +47,7 @@ EOF | |||
| } | |||
|
|
|||
| # parse options | |||
| eval set -- "$(getopt -o j:p:t:s:u:rh --long jobs:,platform:,testtype:,skip-testtypes:,updates:,retry,daily-iso:,defaults:,run-args:,help -- "$@")" | |||
| eval set -- "$(getopt -o j:p:t:s:u:a:rh --long jobs:,platform:,testtype:,skip-testtypes:,updates:additional-repo:,retry,daily-iso:,defaults:,run-args:,help -- "$@")" | |||
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.
Make it possible to add additional repo for a kickstart test run.
At the moment we assume the repository is a regular RPM repository,
as for example created by running createrepo_c on a directory
containing a bunch of RPMs.
The main aim of this functionality is to make it possible to add
additional packages to the RPM transaction Anaconda runs during a
regular RPM based installation. Also by adding packages with a higher
version number than those in the normal package repositories it
is possible to override them with the package from the additional repo.
This can be useful to test Anaconda and/or Initial Setup scratchbuilds.
To use this feature use the -a or --additional-repo flag to the appropriate
runner script and pass either a local filesystem path to a RPM
repository or to a remote RPM repository.
If a local path is detected a localhost web server on the runner will be used to
serve the repo folder to the VM running the test. If a remote path to a
RPM repository is passed, it will be passed directly to the VM.
In both cases the additional repositories are passed via the
inst.addrepo boot option as "inst.addrepo=KSTEST_ADDITIONAL_REPOSITORY,<repo_path>".