| |
@@ -26,6 +26,11 @@
|
| |
"os": {
|
| |
"compose": "{{ compose }}",
|
| |
},
|
| |
+ "variables": {
|
| |
+ "DISTRO": "{{ distro }}",
|
| |
+ "COMPONENT": "{{ zuul.project.short_name }}",
|
| |
+ "TARGET_BRANCH": "{{ zuul.branch }}"
|
| |
+ },
|
| |
"artifacts": [
|
| |
{%- for repo in zuul.artifacts -%}
|
| |
{%- if repo.name == 'repo' -%}
|
| |
Adding two variables for the new
rpm-rebuild-test
job:1. component - the name of that component to test (like ruby).
2. fedora_release - that is essentially the target branch.
info about the variables: https://zuul-ci.org/docs/zuul/latest/job-content.html#var-zuul.items.branch
I am modifying the current testing-farm role that is already used by 'rpm-tmt-test', assuming that providing it with two extra vars won't affect it. (but still needs to be tested).
Alternatively, I can create another PB identical to this one but with a minor change (those two extra vars) and use it only for the rpm-rebuild-test. (but I didn't do it now as I try to avoid duplicate code).