it's convention over configuration and added in the documentation. basically by chosing the rhel-version as parameter (e.g. rhel-7 oder rhel-6), the respective config files are chosen (for the pipeline and the mock config). this approach is chosen in order to allow the users to use the pipeline for multiple versions of rhel with the same pipeline and also to avoid typos due to longer file names. on top of that, it forces users to stick to a naming convention.
fixes #95
it's convention over configuration and added in the documentation. basically by chosing the rhel-version as parameter (e.g. rhel-7 oder rhel-6), the respective config files are chosen (for the pipeline and the mock config). this approach is chosen in order to allow the users to use the pipeline for multiple versions of rhel with the same pipeline and also to avoid typos due to longer file names. on top of that, it forces users to stick to a naming convention.