| |
@@ -25,6 +25,28 @@
|
| |
|
| |
The goal is to move all of our repos under this org in the near future.
|
| |
|
| |
+ == RabbitMQ and pipelines ==
|
| |
+
|
| |
+ *The same pipeline cannot be used twice by two different pipelines.*
|
| |
+
|
| |
+ Each pipeline that uses one of osci rabbitmq queue must have entry in the table bellow.
|
| |
+
|
| |
+ Ref doc https://pagure.io/fedora-infrastructure/issue/8996
|
| |
+
|
| |
+ .Table Queue <-> pipeline
|
| |
+ |===
|
| |
+ | Queue | Pipeline URL
|
| |
+
|
| |
+ | osci-pipelines-queue-4
|
| |
+ | https://osci-jenkins.ci.fedoraproject.org/job/RabbitMQ_Copr_Heartbeat/
|
| |
+
|
| |
+ | osci-pipelines-queue-5
|
| |
+ | https://jenkins-continuous-infra.apps.ci.centos.org/view/RabbitMQ_Copr_Heartbeat/job/RabbitMQ_Copr_Heartbeat/
|
| |
+
|
| |
+ | osci-pipelines-queue-X
|
| |
+ | Each pipelline must reserve queue here
|
| |
+ |===
|
| |
+
|
| |
=== Links ===
|
| |
|
| |
Jenkins repos:
|
| |
It seems that each trigger job has to have its own queue. Using the same queue on different Jenkins trigger job doesn't work even if the topic is different.