zlopez/ansible
1
0
Fork 0
forked from infra/ansible
Code Pull requests Activity
ansible/inventory/group_vars/checkcompose

15 lines
647 B
Text
Raw Normal View History

check-compose: convert to fedora-messaging Following the patterns from openQA and relvalconsumer. Just one to go after this! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-19 15:44:46 -07:00
# This var should never be set for more than one machine
openqa etc: fix up and improve AMQP messaging configuration This is triggered by https://pagure.io/fedora-infrastructure/issue/11375 , but the changes are rather extensive. Unfortunately, some of the relevant files got messed up by the alphabetical sort thing that got run on several group variable files a while ago, so that confuses the diff a bit - I had to unwind those changes to make the files readable again in order to make these changes. Ultimately the goal here is to make the config more consistent and more functional - the variables used and their names should be more consistently related to what they're actually *for*, which I didn't entirely understand when setting this up. So we have variables for the username being used in each case and we use that variable where we're referring to the username, for instance. This should also make the whole thing about the cases where listeners on the openQA stg/lab instance need to listen to prod messages clearer, too. It also makes the user creation clearer by doing it explicitly, just once per user, instead of haphazardly doing it implicitly through the queue definitions. And finally it should also actually fix 11375, by giving the appropriate write permissions to each user. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-06-21 11:54:03 +02:00
checkcompose_prod: true
check-compose: convert to fedora-messaging Following the patterns from openQA and relvalconsumer. Just one to go after this! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-19 15:44:46 -07:00
# The checkcompose settings below cause system(s) in this group to
# send out check-compose reports. This could cause duplicate reports
# if additional systems were added to this group.
checkcompose_emailfrom: rawhide@fedoraproject.org
send compose and updates reports to test-reports list instead of test list Related: https://pagure.io/fedora-qa/issue/700 Signed-off-by: Kamil Páral <kparal@redhat.com>
2022-07-21 16:47:45 +02:00
checkcompose_emailto: "test-reports@lists.fedoraproject.org"
Mass remove/replace iad2 -> rdu3, 10.3. -> 10.16. Signed-off-by: Nils Philippsen <nils@redhat.com>
2025-07-03 16:20:55 +02:00
checkcompose_smtp: bastion.rdu3.fedoraproject.org
check-compose: try to rejig email recipients for new system I changed how check-compose upstream does email recipient config to try and fix the 'get Atomic-related emails to Atomic people' problem again after Fedora-Atomic composes went away. This is an attempt to adjust the play to populate the config file for that change. Let's see what blows up! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-24 19:02:30 -07:00
checkcompose_subvariant_emails:
check-compose: set up subvariant error emails for ELN And get rid of the ancient "AtomicHost" one that's doing nobody any good. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2025-06-05 16:38:46 -07:00
BaseOS:
error: ["yselkowitz@redhat.com", "aavraham@redhat.com"]
openqa etc: fix up and improve AMQP messaging configuration This is triggered by https://pagure.io/fedora-infrastructure/issue/11375 , but the changes are rather extensive. Unfortunately, some of the relevant files got messed up by the alphabetical sort thing that got run on several group variable files a while ago, so that confuses the diff a bit - I had to unwind those changes to make the files readable again in order to make these changes. Ultimately the goal here is to make the config more consistent and more functional - the variables used and their names should be more consistently related to what they're actually *for*, which I didn't entirely understand when setting this up. So we have variables for the username being used in each case and we use that variable where we're referring to the username, for instance. This should also make the whole thing about the cases where listeners on the openQA stg/lab instance need to listen to prod messages clearer, too. It also makes the user creation clearer by doing it explicitly, just once per user, instead of haphazardly doing it implicitly through the queue definitions. And finally it should also actually fix 11375, by giving the appropriate write permissions to each user. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-06-21 11:54:03 +02:00
checkcompose_greenwaveurl: https://greenwave.fedoraproject.org
check-compose: convert to fedora-messaging Following the patterns from openQA and relvalconsumer. Just one to go after this! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-19 15:44:46 -07:00
checkcompose_url: "https://{{ external_hostname }}"
Copy permalink