List of Message Topics¶
This document lists all the topics available on the Unified Message Bus.
Example messages are included as well as descriptions and sample output
from fedmsg.meta
.
Note
All topics from Unified Message Bus are prefixed with
/topic/VirtualTopic
, but the prefix is omitted here
for brevity. For instance, the item listed as eng.brew.task.open
will actually be broadcast as
/topic/VirtualTopic.eng.brew.task.open
.
devops.messagebusd¶
devops.messagebusd.reply.brew-task-repo¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “reply.brew-task-repo” message provides the result of a repo generation triggered by completion of a Brew build task.
You can view the history of messages with the devops.messagebusd.reply.brew-task-repo topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-client-messagebusd',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.reply.brew-task-repo',
'content-length': '802',
'correlation-id': 'e94a18a3-ea07-4d6e-9ca1-a7f389ec98db',
'destination': '/topic/VirtualTopic.devops.messagebusd.reply.brew-task-repo',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:62:0:1293:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.reply.brew-task-repo',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0'},
'i': 0,
'msg': { 'command_output': [ 'Creating x86_64 repo under '
'/srv/repos/scratch/istio-build/servicemesh-operator/1.1.10/1.el8/x86_64\n'
'Repos for task 33455032 created under '
'/srv/repos/scratch/istio-build/servicemesh-operator/1.1.10/1.el8\n'
'Wrote repo file to '
'/srv/repos/scratch/istio-build/servicemesh-operator/1.1.10/1.el8/servicemesh-operator-1.1.10-1.el8-scratch.repo\n'
'Sent email to '
'istio-build/istio-jenkins.rhev-ci-vms.eng.rdu2.redhat.com@redhat.com\n'],
'commands': [ [ 'flock',
'/var/tmp/task-33455032.lock',
'/usr/local/bin/gen-task-repo',
'33455032']],
'emails': 'mikeb@redhat.com',
'endtime': 1606959262.517975,
'message': 'Successfully ran "flock /var/tmp/task-33455032.lock '
'/usr/local/bin/gen-task-repo 33455032"',
'requesttime': None,
'returncode': 0,
'starttime': 1606959252.793886,
'status': 'success'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:62:0:1293:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606959263.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.reply.brew-task-repo',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.reply.brew-task-repo |
|
Successfully ran “flock /var/tmp/task-33455032.lock /usr/local/bin/gen-task-repo 33455032” |
|
None |
|
None |
|
set() |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.reply.task-repo¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “reply.task-repo” message provides the result of a previous “task-repo” message.
You can view the history of messages with the devops.messagebusd.reply.task-repo topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-client-messagebusd',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.reply.task-repo',
'content-length': '1024',
'correlation-id': '25f21d1c-f6a3-438c-ac82-c43d7bcf946c',
'destination': '/topic/VirtualTopic.devops.messagebusd.reply.task-repo',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:1534:0:15:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.reply.task-repo',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0'},
'i': 0,
'msg': { 'command_output': [ 'Creating x86_64 repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/x86_64\n'
'Creating ppc64le repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/ppc64le\n'
'Creating aarch64 repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/aarch64\n'
'Creating i686 repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/i686\n'
'Creating s390x repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/s390x\n'
'Creating noarch repo under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8/noarch\n'
'Repos for task 33314536 created under '
'/mnt/redhat/devel/task-repos/official/kernel/4.18.0/255.el8\n'],
'commands': [ [ 'flock',
'/var/tmp/task-33314536.lock',
'/usr/bin/brew-task-repo',
'33314536']],
'endtime': 1606951534.726212,
'message': 'Successfully ran "flock /var/tmp/task-33314536.lock '
'/usr/bin/brew-task-repo 33314536"',
'requesttime': 1606951330.391472,
'returncode': 0,
'starttime': 1606951331.458769,
'status': 'success'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:1534:0:15:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606951534.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.reply.task-repo',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.reply.task-repo |
|
Successfully ran “flock /var/tmp/task-33314536.lock /usr/bin/brew-task-repo 33314536” |
|
None |
|
None |
|
set() |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.stage-mw-release¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “stage-mw-release” message requests the staging of Middleware content to /mnt/redhat in preparation for release.
You can view the history of messages with the devops.messagebusd.stage-mw-release topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-umbproxy',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.stage-mw-release',
'correlation-id': '34f6e9ac-03f8-40fd-b022-024a069a4720',
'destination': '/topic/VirtualTopic.devops.messagebusd.stage-mw-release',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:220534:0:0:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.stage-mw-release',
'priority': '4',
'reply-to': '/topic/VirtualTopic.devops.messagebusd.reply.stage-mw-release',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0',
'type': 'stage-mw-release',
'user': 'hgao'},
'i': 0,
'msg': { 'release': 'AMQ-BROKER-ON-OPENSHIFT-7.8.0.CR4',
'requesttime': 1606833708.849003},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:220534:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606833709.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.stage-mw-release',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.stage-mw-release |
|
staging requested for release AMQ-BROKER-ON-OPENSHIFT-7.8.0.CR4 by hgao |
|
None |
|
hgao |
|
{‘hgao’} |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.static-repo-regen¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “static-repo-regen” message requests the regeneration of a yum repo based on the content of a Brew tag.
You can view the history of messages with the devops.messagebusd.static-repo-regen topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-umbproxy',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.static-repo-regen',
'correlation-id': '3e67b394-eeb6-436c-875c-a9de5501358a',
'destination': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:439154:0:0:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'priority': '4',
'reply-to': '/topic/VirtualTopic.devops.messagebusd.umbproxy.reply',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0',
'type': 'regen-static-repo',
'umbproxy_username': 'mikeb@IPA.REDHAT.COM',
'user': 'umbproxy-web'},
'i': 0,
'msg': {'requesttime': 1606957014.913, 'tag': 'eng-fedora-33'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:439154:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606957019.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.static-repo-regen |
|
static repo regen requested for tag eng-fedora-33 by mikeb@IPA.REDHAT.COM via umbproxy |
|
https://brewweb.engineering.redhat.com/brew/taginfo?tagID=eng-fedora-33 |
|
mikeb |
|
{‘mikeb’} |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.static-repo-regen¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “static-repo-regen” message requests the regeneration of a yum repo based on the content of a Brew tag. This example was requested by a Jenkins job.
You can view the history of messages with the devops.messagebusd.static-repo-regen topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'CI_NAME': 'revolutionary_engagement',
'CI_TYPE': 'custom',
'JMSXUserID': 'msg-rh-jenkins-ci-plugin',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.static-repo-regen',
'correlation-id': 'ff46fa99-617f-459e-8146-e66981f112be',
'destination': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'expires': '1606744458723',
'message-id': 'ID:rhos-d-rhel7-7134-37774-1606658056028-3:1:1:1:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'persistent': 'true',
'priority': '4',
'reply-to': '/topic/VirtualTopic.qe.ci.static-repo-regen',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '1606658058723',
'type': 'application/json'},
'i': 0,
'msg': {'requesttime': 1606658057, 'tag': 'eng-rhel-7-candidate'},
'msg_id': 'ID:rhos-d-rhel7-7134-37774-1606658056028-3:1:1:1:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606658058.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.static-repo-regen',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.static-repo-regen |
|
static repo regen requested for tag eng-rhel-7-candidate by client msg-rh-jenkins-ci-plugin |
|
https://brewweb.engineering.redhat.com/brew/taginfo?tagID=eng-rhel-7-candidate |
|
None |
|
set() |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.task-repo¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “task-repo” message requests the creation of a yum repo containing the output of a Brew task.
You can view the history of messages with the devops.messagebusd.task-repo topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-umbproxy',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.task-repo',
'correlation-id': '25f21d1c-f6a3-438c-ac82-c43d7bcf946c',
'destination': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:433137:0:0:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'priority': '4',
'reply-to': '/topic/VirtualTopic.devops.messagebusd.reply.task-repo',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0',
'type': 'task-repo',
'umbproxy_username': 'efuller@REDHAT.COM',
'user': 'efuller'},
'i': 0,
'msg': {'requesttime': 1606951330.391472, 'task_id': 33314536},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:433137:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606951331.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.task-repo |
|
repo requested for task 33314536 by efuller@REDHAT.COM via umbproxy |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33314536 |
|
efuller |
|
{‘efuller’} |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.task-repo¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “task-repo” message requests the creation of a yum repo containing the output of a Brew task. This message is artifically constructed to have no identifying information.
You can view the history of messages with the devops.messagebusd.task-repo topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.task-repo',
'correlation-id': '12c84ec2-3b04-4fb9-8871-97e1e58938bb',
'destination': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:347650:0:0:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'priority': '4',
'reply-to': '/topic/VirtualTopic.devops.messagebusd.reply.task-repo',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0',
'type': 'task-repo'},
'i': 0,
'msg': {'requesttime': 1606916274.8746986, 'task_id': 33437766},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:347650:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606916279.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.task-repo',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.task-repo |
|
repo requested for task 33437766 |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33437766 |
|
None |
|
set() |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
devops.messagebusd.umbproxy.reply¶
messagebusd receives a message on the Unified Message Bus, performs some action, and sends a response.
A “umbproxy.reply” message provides the result of a previous request submitted via umbproxy.
You can view the history of messages with the devops.messagebusd.umbproxy.reply topic or all messagebusd messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-client-messagebusd',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'amq6100_originalDestination': 'topic://VirtualTopic.devops.messagebusd.umbproxy.reply',
'content-length': '603',
'correlation-id': '3e67b394-eeb6-436c-875c-a9de5501358a',
'destination': '/topic/VirtualTopic.devops.messagebusd.umbproxy.reply',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:1534:0:18:1',
'original-destination': '/topic/VirtualTopic.devops.messagebusd.umbproxy.reply',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.devops.>',
'timestamp': '0'},
'i': 0,
'msg': { 'command_output': [''],
'commands': [ [ 'flock',
'/var/tmp/eng-fedora-33.lock',
'/usr/bin/brew-repo-wrapper',
'--basedir',
'/mnt/redhat/rel-eng/repos',
'--taggedfile',
'/mnt/redhat/rel-eng/repos/eng-fedora-33/tagged',
'eng-fedora-33',
'--unsigned']],
'endtime': 1606957024.853463,
'message': 'Successfully ran "flock /var/tmp/eng-fedora-33.lock '
'/usr/bin/brew-repo-wrapper --basedir '
'/mnt/redhat/rel-eng/repos --taggedfile '
'/mnt/redhat/rel-eng/repos/eng-fedora-33/tagged '
'eng-fedora-33 --unsigned"',
'requesttime': 1606957014.913,
'returncode': 0,
'starttime': 1606957019.837216,
'status': 'success'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-40384-1606738019242-3:1534:0:18:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1606957024.0,
'topic': '/topic/VirtualTopic.devops.messagebusd.umbproxy.reply',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
messagebusd.umbproxy.reply |
|
Successfully ran “flock /var/tmp/eng-fedora-33.lock /usr/bin/brew-repo-wrapper –basedir /mnt/redhat/rel-eng/repos –taggedfile /mnt/redhat/rel-eng/repos/eng-fedora-33/tagged eng-fedora-33 –unsigned” |
|
|
|
None |
|
set() |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.aqe-jenkins¶
eng.aqe-jenkins.retrobob.result¶
Retrobob is a service that runs another tool, retrodep, to generate source manifest from dist-git content. It publishes retrodep run results to UMB.
You can view the history of messages with the eng.aqe-jenkins.retrobob.result topic or all aqe-jenkins messages in datagrepper.
{ 'headers': { 'CI_NAME': 'retrobob-dev',
'CI_TYPE': 'custom',
'JMSXUserID': 'msg-aqe-jenkins',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-stage.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.aqe-jenkins.retrobob.result',
'correlation-id': 'ee691c02-0e29-44e3-be42-314f7ea2a60a',
'destination': '/topic/VirtualTopic.eng.aqe-jenkins.retrobob.result',
'expires': '1560486381829',
'message-id': 'ID:pnt-devops-rad-stage-jenkins.rhev-ci-vms.eng.rdu2.redhat.com-44328',
'original-destination': '/topic/VirtualTopic.eng.aqe-jenkins.retrobob.result',
'persistent': 'true',
'priority': '4',
'service': 'RetroBob',
'subscription': '/queue/Consumer.client-datanommer.upshift-stage.VirtualTopic.eng.>',
'timestamp': '1560399981829',
'type': 'application/json'},
'i': 0,
'msg': { 'build_id': 1719121,
'manifest_path': 'rh-manifest.txt',
'name': 'osbs-test-sandwich-container',
'nvr': 'osbs-test-sandwich-container-1.0.go.module.metadata-198',
'result': 'success',
'source': 'git://dist-git.host.stage.eng.bos.redhat.com/containers/osbs-test-sandwich#test-sources',
'source_tag': 'osbs-test-sandwich-container-1.0.go.module.metadata-198-sources',
'version': '1.0.go.module.metadata'},
'msg_id': 'ID:pnt-devops-rad-stage-jenkins.rhev-ci-vms.eng.rdu2.redhat.com-44328-1560142882813-1701:1:1:1:1',
'timestamp': 1560399981.0,
'topic': '/topic/VirtualTopic.eng.aqe-jenkins.retrobob.result'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
aqe-jenkins.retrobob.result |
|
retrodep run on build osbs-test-sandwich-container was met with success |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew¶
eng.brew.build.building¶
You can view the history of messages with the eng.brew.build.building topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'completion_time': None,
'epoch': None,
'extra': None,
'id': 547678,
'name': 'selinux-policy',
'owner': 2752,
'pkg_id': 2989,
'release': '136.el7',
'source': None,
'start_time': 'NOW',
'state': 0,
'task_id': 12910431,
'version': '3.13.1',
'volume_id': 0},
'new': 0,
'old': 3},
'msg_id': '9b697089-c192-49eb-a110-4754209a43f5',
'timestamp': 1490891323.0,
'topic': '/topic/VirtualTopic.eng.brew.build.building'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.building |
|
selinux-policy-3.13.1-136.el7 is building |
|
|
|
Unspecified |
|
Unspecified |
|
{‘selinux-policy’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.canceled¶
You can view the history of messages with the eng.brew.build.canceled topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'build_id': 543196,
'completion_time': '2017-03-09 22:17:31.160826',
'completion_ts': 1489097851.16083,
'creation_event_id': 15116085,
'creation_time': '2017-03-09 22:16:04.788558',
'creation_ts': 1489097764.78856,
'epoch': None,
'extra': None,
'id': 543196,
'name': 'libgpod',
'nvr': 'libgpod-0.8.2-12.el7',
'owner_id': 3004,
'owner_name': 'klember',
'package_id': 1924,
'package_name': 'libgpod',
'release': '12.el7',
'source': None,
'start_time': '2017-03-09 22:16:04.788558',
'start_ts': 1489097764.78856,
'state': 4,
'task_id': 12732117,
'version': '0.8.2',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'new': 4,
'old': 4},
'msg_id': '073a7b61-8e23-4448-9c09-6e59aa2f911d',
'timestamp': 1489097838.0,
'topic': '/topic/VirtualTopic.eng.brew.build.canceled'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.canceled |
|
build of libgpod-0.8.2-12.el7 has been canceled |
|
|
|
Unspecified |
|
{‘klember’} |
|
{‘libgpod’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.complete¶
You can view the history of messages with the eng.brew.build.complete topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'build_id': 547865,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15289596,
'creation_time': '2017-03-31 07:52:33.843957',
'creation_ts': 1490946753.84396,
'epoch': None,
'extra': None,
'id': 547865,
'name': 'org.jboss-jboss-dmr',
'nvr': 'org.jboss-jboss-dmr-1.4.0.Final_redhat_1-1',
'owner_id': 3099,
'owner_name': 'psakar',
'package_id': 31785,
'package_name': 'org.jboss-jboss-dmr',
'release': '1',
'source': None,
'start_time': '2017-03-31 07:52:33.843957',
'start_ts': 1490946753.84396,
'state': 0,
'task_id': 12915073,
'version': '1.4.0.Final_redhat_1',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'new': 1,
'old': 0},
'msg_id': '5372c2d5-ff01-49b4-97f5-71445264fece',
'timestamp': 1490946728.0,
'topic': '/topic/VirtualTopic.eng.brew.build.complete'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.complete |
|
org.jboss-jboss-dmr-1.4.0.Final_redhat_1-1 has been built successfully |
|
|
|
Unspecified |
|
{‘psakar’} |
|
{‘org.jboss-jboss-dmr’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.complete¶
You can view the history of messages with the eng.brew.build.complete topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'completion_time': '2017-04-11 22:52:49',
'epoch': None,
'extra': '{"image": {"autorebuild": false, "help": null}, '
'"container_koji_task_id": 12996137}',
'id': 550925,
'name': 'metrics-cassandra-docker',
'owner': 3436,
'pkg_id': 54389,
'release': '3',
'source': 'git://pkgs.devel.redhat.com/rpms/metrics-cassandra-docker#1c9ebc26c5066ed4894d45878bc90fd66046a292',
'start_time': '2017-04-11 22:42:53',
'state': 1,
'task_id': None,
'version': '3.6.0',
'volume_id': 0},
'new': 1,
'old': None},
'msg_id': 'ffcbdc40-1435-492f-83f9-51b9892b9524',
'timestamp': 1491951183.0,
'topic': '/topic/VirtualTopic.eng.brew.build.complete'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.complete |
|
metrics-cassandra-docker-3.6.0-3 has been built successfully |
|
|
|
Unspecified |
|
set() |
|
{‘metrics-cassandra-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.deleted¶
You can view the history of messages with the eng.brew.build.deleted topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'build_id': 524863,
'completion_time': '2016-11-16 23:57:14.887771',
'completion_ts': 1479340634.88777,
'creation_event_id': 14433958,
'creation_time': '2016-11-16 23:56:35.580377',
'creation_ts': 1479340595.58038,
'epoch': None,
'extra': None,
'id': 524863,
'name': 'elasticsearch',
'nvr': 'elasticsearch-2.4.1-2.el7',
'owner_id': 425,
'owner_name': 'rmeggins',
'package_id': 34337,
'package_name': 'elasticsearch',
'release': '2.el7',
'source': None,
'start_time': '2016-11-16 23:56:35.580377',
'start_ts': 1479340595.58038,
'state': 1,
'task_id': 12116211,
'version': '2.4.1',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'new': 2,
'old': 1},
'msg_id': '06a492c3-8758-4a08-aa34-279435de49d9',
'timestamp': 1490786161.0,
'topic': '/topic/VirtualTopic.eng.brew.build.deleted'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.deleted |
|
elasticsearch-2.4.1-2.el7 has been deleted |
|
|
|
Unspecified |
|
{‘rmeggins’} |
|
{‘elasticsearch’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.failed¶
You can view the history of messages with the eng.brew.build.failed topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'build_id': 547932,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15292221,
'creation_time': '2017-03-31 16:17:10.988945',
'creation_ts': 1490977030.98895,
'epoch': 1,
'extra': None,
'id': 547932,
'name': 'libreoffice',
'nvr': 'libreoffice-5.0.6.2-8.el7',
'owner_id': 89,
'owner_name': 'caolanm',
'package_id': 33948,
'package_name': 'libreoffice',
'release': '8.el7',
'source': None,
'start_time': '2017-03-31 16:17:10.988945',
'start_ts': 1490977030.98895,
'state': 0,
'task_id': 12919327,
'version': '5.0.6.2',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'new': 3,
'old': 0},
'msg_id': '9ff79b2a-67c2-4425-93d0-d7132f343b17',
'timestamp': 1490978317.0,
'topic': '/topic/VirtualTopic.eng.brew.build.failed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.failed |
|
build of libreoffice-5.0.6.2-8.el7 has failed |
|
|
|
Unspecified |
|
{‘caolanm’} |
|
{‘libreoffice’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.tag¶
You can view the history of messages with the eng.brew.build.tag topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 550575,
'completion_time': '2017-04-11 16:02:27.825432',
'completion_ts': 1491926547.82543,
'creation_event_id': 15403058,
'creation_time': '2017-04-11 15:57:37.130866',
'creation_ts': 1491926257.13087,
'epoch': None,
'extra': None,
'id': 550575,
'name': 'python-gssapi',
'nvr': 'python-gssapi-1.2.0-3.el7',
'owner_id': 2717,
'owner_name': 'rharwood',
'package_id': 52097,
'package_name': 'python-gssapi',
'release': '3.el7',
'source': None,
'start_time': '2017-04-11 15:57:37.130866',
'start_ts': 1491926257.13087,
'state': 1,
'task_id': 12990769,
'version': '1.2.0',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'force': False,
'tag': { 'arches': None,
'extra': {},
'id': 9895,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'rhel-7.4-candidate',
'perm': None,
'perm_id': None},
'user': { 'id': 2717,
'krb_principal': 'rharwood@REDHAT.COM',
'name': 'rharwood',
'status': 0,
'usertype': 0}},
'msg_id': '4307e30e-70c5-4d4a-9244-53b8860c067b',
'timestamp': 1491926538.0,
'topic': '/topic/VirtualTopic.eng.brew.build.tag'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.tag |
|
python-gssapi-1.2.0-3.el7 tagged into rhel-7.4-candidate |
|
|
|
Unspecified |
|
{‘rharwood’} |
|
{‘python-gssapi’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.build.untag¶
You can view the history of messages with the eng.brew.build.untag topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 480574,
'completion_time': '2016-02-16 07:25:20.776579',
'completion_ts': 1455607520.77658,
'creation_event_id': 12616125,
'creation_time': '2016-02-16 07:21:48.354511',
'creation_ts': 1455607308.35451,
'epoch': None,
'extra': None,
'id': 480574,
'name': 'luci',
'nvr': 'luci-0.26.0-75.el6',
'owner_id': 471,
'owner_name': 'rmccabe',
'package_id': 18835,
'package_name': 'luci',
'release': '75.el6',
'source': None,
'start_time': '2016-02-16 07:21:48.354511',
'start_ts': 1455607308.35451,
'state': 1,
'task_id': 10500836,
'version': '0.26.0',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'force': False,
'strict': True,
'tag': { 'arches': None,
'extra': {},
'id': 8179,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'RHEL-6.8-candidate',
'perm': None,
'perm_id': None},
'user': { 'id': 1181,
'krb_principal': 'host/x86-013.build.bos.redhat.com@REDHAT.COM',
'name': 'host/x86-013.build.bos.redhat.com',
'status': 0,
'usertype': 0}},
'msg_id': 'a4b5d91a-c4db-4e09-99eb-f460609f22b3',
'timestamp': 1491940321.0,
'topic': '/topic/VirtualTopic.eng.brew.build.untag'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.build.untag |
|
luci-0.26.0-75.el6 untagged from RHEL-6.8-candidate |
|
|
|
Unspecified |
|
{‘host/x86-013.build.bos.redhat.com’, ‘rmccabe’} |
|
{‘luci’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.import.archive¶
You can view the history of messages with the eng.brew.import.archive topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'archive': { 'artifact_id': 'errai-ui',
'btype': 'maven',
'btype_id': 2,
'build_id': 550651,
'buildroot_id': None,
'checksum': 'fe1d65b3501803a612ebfcf4f6f42b6a',
'checksum_type': 0,
'extra': None,
'filename': 'errai-ui-3.2.5.Final-redhat-1.jar',
'group_id': 'org.jboss.errai',
'id': 1859056,
'metadata_only': False,
'size': 494473,
'type_description': 'Jar file',
'type_extensions': 'jar war rar ear sar kar jdocbook '
'jdocbook-style plugin',
'type_id': 1,
'type_name': 'jar',
'version': '3.2.5.Final-redhat-1'},
'build': { 'build_id': 550651,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15403648,
'creation_time': '2017-04-11 17:00:13.711461',
'creation_ts': 1491930013.71146,
'epoch': None,
'extra': None,
'id': 550651,
'name': 'org.jboss.errai-errai-parent',
'nvr': 'org.jboss.errai-errai-parent-3.2.5.Final_redhat_1-8',
'owner_id': 3820,
'owner_name': 'anstephe',
'package_id': 19560,
'package_name': 'org.jboss.errai-errai-parent',
'release': '8',
'source': None,
'start_time': '2017-04-11 17:00:13.711461',
'start_ts': 1491930013.71146,
'state': 0,
'task_id': 12991530,
'version': '3.2.5.Final_redhat_1',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'build_type': 'maven',
'fileinfo': {},
'filepath': '/mnt/brew/work/tasks/1531/12991531/org/jboss/errai/errai-ui/3.2.5.Final-redhat-1/errai-ui-3.2.5.Final-redhat-1.jar',
'type': 'archive'},
'msg_id': '0c6e5ca8-b9ad-46f5-be91-ce430f219264',
'timestamp': 1491930018.0,
'topic': '/topic/VirtualTopic.eng.brew.import.archive'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.import.archive |
|
errai-ui-3.2.5.Final-redhat-1.jar from org.jboss.errai-errai-parent-3.2.5.Final_redhat_1-8 has been imported |
|
Unspecified |
|
Unspecified |
|
{‘anstephe’} |
|
{‘org.jboss.errai-errai-parent’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.import.build¶
You can view the history of messages with the eng.brew.import.build topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'brmap': { 'tasks/156/12990156/ghostscript-9.07-26.el7.ppc.rpm': 3286169,
'tasks/156/12990156/ghostscript-9.07-26.el7.src.rpm': 3286169,
'tasks/156/12990156/ghostscript-cups-9.07-26.el7.ppc.rpm': 3286169,
'tasks/156/12990156/ghostscript-debuginfo-9.07-26.el7.ppc.rpm': 3286169,
'tasks/156/12990156/ghostscript-devel-9.07-26.el7.ppc.rpm': 3286169,
'tasks/156/12990156/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286169,
'tasks/156/12990156/ghostscript-gtk-9.07-26.el7.ppc.rpm': 3286169,
'tasks/157/12990157/ghostscript-9.07-26.el7.x86_64.rpm': 3286166,
'tasks/157/12990157/ghostscript-cups-9.07-26.el7.x86_64.rpm': 3286166,
'tasks/157/12990157/ghostscript-debuginfo-9.07-26.el7.x86_64.rpm': 3286166,
'tasks/157/12990157/ghostscript-devel-9.07-26.el7.x86_64.rpm': 3286166,
'tasks/157/12990157/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286166,
'tasks/157/12990157/ghostscript-gtk-9.07-26.el7.x86_64.rpm': 3286166,
'tasks/160/12990160/ghostscript-9.07-26.el7.s390.rpm': 3286173,
'tasks/160/12990160/ghostscript-cups-9.07-26.el7.s390.rpm': 3286173,
'tasks/160/12990160/ghostscript-debuginfo-9.07-26.el7.s390.rpm': 3286173,
'tasks/160/12990160/ghostscript-devel-9.07-26.el7.s390.rpm': 3286173,
'tasks/160/12990160/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286173,
'tasks/160/12990160/ghostscript-gtk-9.07-26.el7.s390.rpm': 3286173,
'tasks/162/12990162/ghostscript-9.07-26.el7.aarch64.rpm': 3286168,
'tasks/162/12990162/ghostscript-cups-9.07-26.el7.aarch64.rpm': 3286168,
'tasks/162/12990162/ghostscript-debuginfo-9.07-26.el7.aarch64.rpm': 3286168,
'tasks/162/12990162/ghostscript-devel-9.07-26.el7.aarch64.rpm': 3286168,
'tasks/162/12990162/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286168,
'tasks/162/12990162/ghostscript-gtk-9.07-26.el7.aarch64.rpm': 3286168,
'tasks/163/12990163/ghostscript-9.07-26.el7.ppc64le.rpm': 3286175,
'tasks/163/12990163/ghostscript-cups-9.07-26.el7.ppc64le.rpm': 3286175,
'tasks/163/12990163/ghostscript-debuginfo-9.07-26.el7.ppc64le.rpm': 3286175,
'tasks/163/12990163/ghostscript-devel-9.07-26.el7.ppc64le.rpm': 3286175,
'tasks/163/12990163/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286175,
'tasks/163/12990163/ghostscript-gtk-9.07-26.el7.ppc64le.rpm': 3286175,
'tasks/164/12990164/ghostscript-9.07-26.el7.ppc64.rpm': 3286170,
'tasks/164/12990164/ghostscript-cups-9.07-26.el7.ppc64.rpm': 3286170,
'tasks/164/12990164/ghostscript-debuginfo-9.07-26.el7.ppc64.rpm': 3286170,
'tasks/164/12990164/ghostscript-devel-9.07-26.el7.ppc64.rpm': 3286170,
'tasks/164/12990164/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286170,
'tasks/164/12990164/ghostscript-gtk-9.07-26.el7.ppc64.rpm': 3286170,
'tasks/165/12990165/ghostscript-9.07-26.el7.i686.rpm': 3286167,
'tasks/165/12990165/ghostscript-cups-9.07-26.el7.i686.rpm': 3286167,
'tasks/165/12990165/ghostscript-debuginfo-9.07-26.el7.i686.rpm': 3286167,
'tasks/165/12990165/ghostscript-devel-9.07-26.el7.i686.rpm': 3286167,
'tasks/165/12990165/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286167,
'tasks/165/12990165/ghostscript-gtk-9.07-26.el7.i686.rpm': 3286167,
'tasks/166/12990166/ghostscript-9.07-26.el7.s390x.rpm': 3286177,
'tasks/166/12990166/ghostscript-cups-9.07-26.el7.s390x.rpm': 3286177,
'tasks/166/12990166/ghostscript-debuginfo-9.07-26.el7.s390x.rpm': 3286177,
'tasks/166/12990166/ghostscript-devel-9.07-26.el7.s390x.rpm': 3286177,
'tasks/166/12990166/ghostscript-doc-9.07-26.el7.noarch.rpm': 3286177,
'tasks/166/12990166/ghostscript-gtk-9.07-26.el7.s390x.rpm': 3286177},
'build': { 'build_id': 550553,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15402490,
'creation_time': '2017-04-11 15:06:25.391196',
'creation_ts': 1491923185.3912,
'epoch': None,
'extra': None,
'id': 550553,
'name': 'ghostscript',
'nvr': 'ghostscript-9.07-26.el7',
'owner_id': 3066,
'owner_name': 'dkaspar',
'package_id': 537,
'package_name': 'ghostscript',
'release': '26.el7',
'source': None,
'start_time': '2017-04-11 15:06:25.391196',
'start_ts': 1491923185.3912,
'state': 0,
'task_id': 12990126,
'version': '9.07',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'build_id': 550553,
'logs': { 'aarch64': [ 'tasks/162/12990162/build.log',
'tasks/162/12990162/state.log',
'tasks/162/12990162/root.log'],
'i686': [ 'tasks/165/12990165/root.log',
'tasks/165/12990165/build.log',
'tasks/165/12990165/state.log'],
'ppc': [ 'tasks/156/12990156/state.log',
'tasks/156/12990156/build.log',
'tasks/156/12990156/root.log'],
'ppc64': [ 'tasks/164/12990164/state.log',
'tasks/164/12990164/build.log',
'tasks/164/12990164/root.log'],
'ppc64le': [ 'tasks/163/12990163/root.log',
'tasks/163/12990163/build.log',
'tasks/163/12990163/state.log'],
's390': [ 'tasks/160/12990160/state.log',
'tasks/160/12990160/build.log',
'tasks/160/12990160/root.log'],
's390x': [ 'tasks/166/12990166/state.log',
'tasks/166/12990166/build.log',
'tasks/166/12990166/root.log'],
'x86_64': [ 'tasks/157/12990157/root.log',
'tasks/157/12990157/build.log',
'tasks/157/12990157/state.log']},
'rpms': [ 'tasks/156/12990156/ghostscript-doc-9.07-26.el7.noarch.rpm',
'tasks/156/12990156/ghostscript-cups-9.07-26.el7.ppc.rpm',
'tasks/156/12990156/ghostscript-devel-9.07-26.el7.ppc.rpm',
'tasks/156/12990156/ghostscript-gtk-9.07-26.el7.ppc.rpm',
'tasks/156/12990156/ghostscript-debuginfo-9.07-26.el7.ppc.rpm',
'tasks/156/12990156/ghostscript-9.07-26.el7.ppc.rpm',
'tasks/157/12990157/ghostscript-cups-9.07-26.el7.x86_64.rpm',
'tasks/157/12990157/ghostscript-devel-9.07-26.el7.x86_64.rpm',
'tasks/157/12990157/ghostscript-9.07-26.el7.x86_64.rpm',
'tasks/157/12990157/ghostscript-debuginfo-9.07-26.el7.x86_64.rpm',
'tasks/157/12990157/ghostscript-gtk-9.07-26.el7.x86_64.rpm',
'tasks/163/12990163/ghostscript-cups-9.07-26.el7.ppc64le.rpm',
'tasks/163/12990163/ghostscript-gtk-9.07-26.el7.ppc64le.rpm',
'tasks/163/12990163/ghostscript-9.07-26.el7.ppc64le.rpm',
'tasks/163/12990163/ghostscript-devel-9.07-26.el7.ppc64le.rpm',
'tasks/163/12990163/ghostscript-debuginfo-9.07-26.el7.ppc64le.rpm',
'tasks/162/12990162/ghostscript-debuginfo-9.07-26.el7.aarch64.rpm',
'tasks/162/12990162/ghostscript-devel-9.07-26.el7.aarch64.rpm',
'tasks/162/12990162/ghostscript-cups-9.07-26.el7.aarch64.rpm',
'tasks/162/12990162/ghostscript-9.07-26.el7.aarch64.rpm',
'tasks/162/12990162/ghostscript-gtk-9.07-26.el7.aarch64.rpm',
'tasks/164/12990164/ghostscript-devel-9.07-26.el7.ppc64.rpm',
'tasks/164/12990164/ghostscript-debuginfo-9.07-26.el7.ppc64.rpm',
'tasks/164/12990164/ghostscript-gtk-9.07-26.el7.ppc64.rpm',
'tasks/164/12990164/ghostscript-cups-9.07-26.el7.ppc64.rpm',
'tasks/164/12990164/ghostscript-9.07-26.el7.ppc64.rpm',
'tasks/165/12990165/ghostscript-cups-9.07-26.el7.i686.rpm',
'tasks/165/12990165/ghostscript-debuginfo-9.07-26.el7.i686.rpm',
'tasks/165/12990165/ghostscript-9.07-26.el7.i686.rpm',
'tasks/165/12990165/ghostscript-gtk-9.07-26.el7.i686.rpm',
'tasks/165/12990165/ghostscript-devel-9.07-26.el7.i686.rpm',
'tasks/160/12990160/ghostscript-9.07-26.el7.s390.rpm',
'tasks/160/12990160/ghostscript-devel-9.07-26.el7.s390.rpm',
'tasks/160/12990160/ghostscript-debuginfo-9.07-26.el7.s390.rpm',
'tasks/160/12990160/ghostscript-gtk-9.07-26.el7.s390.rpm',
'tasks/160/12990160/ghostscript-cups-9.07-26.el7.s390.rpm',
'tasks/166/12990166/ghostscript-devel-9.07-26.el7.s390x.rpm',
'tasks/166/12990166/ghostscript-9.07-26.el7.s390x.rpm',
'tasks/166/12990166/ghostscript-gtk-9.07-26.el7.s390x.rpm',
'tasks/166/12990166/ghostscript-debuginfo-9.07-26.el7.s390x.rpm',
'tasks/166/12990166/ghostscript-cups-9.07-26.el7.s390x.rpm'],
'srpm': 'tasks/156/12990156/ghostscript-9.07-26.el7.src.rpm',
'task_id': 12990126,
'type': 'build'},
'msg_id': '05ddb3ff-12aa-4295-bca0-e9f77ecb0448',
'timestamp': 1491924112.0,
'topic': '/topic/VirtualTopic.eng.brew.import.build'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.import.build |
|
ghostscript-9.07-26.el7 has been imported |
|
Unspecified |
|
Unspecified |
|
{‘dkaspar’} |
|
{‘ghostscript’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.import.cg¶
You can view the history of messages with the eng.brew.import.cg topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 550756,
'completion_time': '2017-04-11 19:04:24',
'completion_ts': 1491937464.0,
'creation_event_id': 15405094,
'creation_time': '2017-04-11 19:04:39.18265',
'creation_ts': 1491937479.18265,
'epoch': None,
'extra': { 'container_koji_task_id': 12993625,
'filesystem_koji_task_id': 12993952,
'image': {'autorebuild': False, 'help': None}},
'id': 550756,
'name': 'rhel7-atomic-docker',
'nvr': 'rhel7-atomic-docker-7.3-17',
'owner_id': 3436,
'owner_name': 'osbs',
'package_id': 61681,
'package_name': 'rhel7-atomic-docker',
'release': '17',
'source': 'git://pkgs.devel.redhat.com/rpms/atomic-docker#6469fe553d4ca7f1f26605dee84fab5c26652481',
'start_time': '2017-04-11 18:54:05',
'start_ts': 1491936845.0,
'state': 1,
'task_id': None,
'version': '7.3',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'directory': 'koji-promote/1491937471.520017.CFvOUTpZ',
'metadata': { 'buildroots': [ { 'buildroot_id': 1,
'cg_id': 1,
'checksum': 'a2bdc7397dacb86adc8b0c775ce5ec3f',
'checksum_type': 'md5',
'components': [ { 'arch': 'noarch',
'epoch': 1,
'name': 'perl-TimeDate',
'release': '2.el7',
'sigmd5': 'e034b23248cf3f6b6b028688f3fce41d',
'signature': '199e2f91fd431d51',
'type': 'rpm',
'version': '2.30'},
{ 'arch': 'noarch',
'epoch': None,
'name': 'perl-Mozilla-PublicSuffix',
'release': '1.el7eng',
'sigmd5': 'cad070218512ed9864a895e8a58cb5b5',
'signature': None,
'type': 'rpm',
'version': '0.1.19'},
{ 'arch': 'noarch',
'epoch': None,
'name': 'setup',
'release': '7.el7',
'sigmd5': '0a445b9930665e1b435ed08b792f4811',
'signature': '199e2f91fd431d51',
'type': 'rpm',
'version': '2.8.71'},
{ 'arch': 'x86_64',
'epoch': None,
'name': 'libdnf',
'release': '3.el7',
'sigmd5': '9103f02b5f7f567e17b4a6bc38a5f3cb',
'signature': '199e2f91fd431d51',
'type': 'rpm',
'version': '0.7.4'}],
'container': { 'arch': 'x86_64',
'type': 'docker'},
'content_generator': { 'name': 'atomic-reactor',
'version': '1.6.23'},
'extra': { 'osbs': { 'build_id': 'atomic-docker-unknown-14',
'builder_image_id': 'docker-pullable://brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rcm/buildroot@sha256:90671a732a1b644c76fe18ec67cb4305cd22cf7db86efaa92aed23e4e0b1f45f'}},
'host': { 'arch': 'x86_64',
'os': 'rhel-7'}}]},
'type': 'cg'},
'msg_id': '5fc16f0f-92f7-4638-8048-2f4d3571bc30',
'timestamp': 1491937445.0,
'topic': '/topic/VirtualTopic.eng.brew.import.cg'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.import.cg |
|
rhel7-atomic-docker-7.3-17 has been imported by a Content Generator |
|
Unspecified |
|
Unspecified |
|
{‘osbs’} |
|
{‘rhel7-atomic-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.import.image¶
You can view the history of messages with the eng.brew.import.image topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 550555,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15402549,
'creation_time': '2017-04-11 15:12:06.983196',
'creation_ts': 1491923526.9832,
'epoch': 0,
'extra': None,
'id': 550555,
'name': 'rhel-guest-image',
'nvr': 'rhel-guest-image-7.4-99',
'owner_id': 3641,
'owner_name': 'compose/rcm-compose-nightly-01.host.prod.eng.bos.redhat.com',
'package_id': 42902,
'package_name': 'rhel-guest-image',
'release': '99',
'source': None,
'start_time': '2017-04-11 15:12:06.983196',
'start_ts': 1491923526.9832,
'state': 0,
'task_id': 12990216,
'version': '7.4',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'fullpath': '/mnt/brew/work/tasks/230/12990230/rhel-guest-image-7.4-99.x86_64.raw.xz',
'image': { 'arch': 'x86_64',
'files': [ 'tdl-x86_64.xml',
'rhel-7.4-server-kvm.ks',
'koji-guest-rhel-7.4-image-build-12990230-base.ks',
'libvirt-qcow2-x86_64.xml',
'rhel-guest-image-7.4-99.x86_64.qcow2',
'libvirt-raw-xz-x86_64.xml',
'rhel-guest-image-7.4-99.x86_64.raw.xz'],
'logs': ['oz-x86_64.log'],
'name': 'rhel-guest-image',
'release': '99',
'relpath': 'tasks/230/12990230',
'rpmlist': [ { 'arch': 'x86_64',
'buildtime': 1490591341,
'epoch': None,
'name': 'teamd',
'payloadhash': '7c325e52cb51f8a86038d85728b589b5',
'release': '5.el7',
'size': 277765,
'version': '1.25'},
{ 'arch': 'noarch',
'buildtime': 1490970740,
'epoch': 1,
'name': 'grub2-common',
'payloadhash': '923ffc8d16fc80d3dab4ff2e17cf71d8',
'release': '0.53.el7',
'size': 3913922,
'version': '2.02'},
{ 'arch': 'x86_64',
'buildtime': 1390744419,
'epoch': None,
'name': 'libunistring',
'payloadhash': '2634a7ca66d6fae3ad80627b05bde877',
'release': '9.el7',
'size': 1145753,
'version': '0.9.3'},
{ 'arch': 'x86_64',
'buildtime': 1491587215,
'epoch': None,
'name': 'kernel-tools-libs',
'payloadhash': '792adf2459b94af82be4cda26fbc1697',
'release': '646.el7',
'size': 18640,
'version': '3.10.0'}],
'task_id': 12990230,
'version': '7.4'},
'type': 'image'},
'msg_id': 'd45ca752-1942-46b2-a9c3-51aadb47b495',
'timestamp': 1491926158.0,
'topic': '/topic/VirtualTopic.eng.brew.import.image'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.import.image |
|
x86_64 image from rhel-guest-image-7.4-99 has been imported |
|
Unspecified |
|
Unspecified |
|
{‘compose/rcm-compose-nightly-01.host.prod.eng.bos.redhat.com’} |
|
{‘rhel-guest-image’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.import.rpm¶
You can view the history of messages with the eng.brew.import.rpm topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 550526,
'completion_time': None,
'completion_ts': None,
'creation_event_id': 15401837,
'creation_time': '2017-04-11 13:38:40.86017',
'creation_ts': 1491917920.86017,
'epoch': None,
'extra': None,
'id': 550526,
'name': 'systemd',
'nvr': 'systemd-219-34.el7',
'owner_id': 1615,
'owner_name': 'lnykryn',
'package_id': 34071,
'package_name': 'systemd',
'release': '34.el7',
'source': None,
'start_time': '2017-04-11 13:38:40.86017',
'start_ts': 1491917920.86017,
'state': 0,
'task_id': 12989147,
'version': '219',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'fileinfo': None,
'filepath': '/mnt/brew/work/tasks/9157/12989157/systemd-devel-219-34.el7.x86_64.rpm',
'rpm': { 'arch': 'x86_64',
'build_id': 550526,
'buildroot_id': 3286008,
'buildtime': 1491918212,
'epoch': None,
'external_repo_id': 0,
'id': 4637364,
'name': 'systemd-devel',
'payloadhash': '9a9f00c2ea82ec63cb251fa32554fcd6',
'release': '34.el7',
'size': 186320,
'sourcepackage': None,
'sourcerpm': 'systemd-219-34.el7.src.rpm',
'version': '219'},
'type': 'rpm'},
'msg_id': '7f6c705c-8513-41a7-bf17-f56ab5c59f10',
'timestamp': 1491918957.0,
'topic': '/topic/VirtualTopic.eng.brew.import.rpm'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.import.rpm |
|
systemd-devel-219-34.el7.x86_64.rpm has been imported |
|
Unspecified |
|
Unspecified |
|
{‘lnykryn’} |
|
{‘systemd’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.kojira.expired¶
You can view the history of messages with the eng.brew.kojira.expired topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'seconds': 30,
'tag': 'rhos-16.0-rhel-8-trunk-image-build',
'tag_id': 21700,
'task_id': 22335794,
'type': 'RepoExpired'},
'msg_id': '47f15511-549c-4fc1-b6cd-738d4e1995bc',
'topic': '/topic/VirtualTopic.eng.brew.kojira.expired'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
Unspecified |
|
tag rhos-16.0-rhel-8-trunk-image-build was expired for 30 seconds |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=22335794 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.package.add¶
You can view the history of messages with the eng.brew.package.add topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'action': 'add',
'block': False,
'extra_arches': None,
'force': None,
'owner': 3099,
'package': {'id': 32324, 'name': 'jboss-logging'},
'tag': { 'arches': None,
'extra': {},
'id': 9356,
'locked': True,
'maven_include_all': False,
'maven_support': False,
'name': 'jb-eap-7.1-rhel-7',
'perm': None,
'perm_id': None},
'update': False},
'msg_id': '47f155fe-549c-4fc1-b6cd-738d4e1995bc',
'timestamp': 1490890860.0,
'topic': '/topic/VirtualTopic.eng.brew.package.add'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.package.add |
|
package jboss-logging was added to tag jb-eap-7.1-rhel-7 |
|
https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=32324 |
|
Unspecified |
|
Unspecified |
|
{‘jboss-logging’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.package.block¶
You can view the history of messages with the eng.brew.package.block topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'action': 'block',
'block': True,
'extra_arches': None,
'force': False,
'owner': 2838,
'package': {'id': 34523, 'name': 'python-mock'},
'tag': { 'arches': None,
'extra': {},
'id': 10767,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'extras-rhel-7.4-set',
'perm': 'trusted',
'perm_id': 6},
'update': False},
'msg_id': 'ee19ce13-a0a3-46bd-91c5-921bef874016',
'timestamp': 1490195003.0,
'topic': '/topic/VirtualTopic.eng.brew.package.block'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.package.block |
|
package python-mock was blocked in tag extras-rhel-7.4-set |
|
https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=34523 |
|
Unspecified |
|
Unspecified |
|
{‘python-mock’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.package.remove¶
You can view the history of messages with the eng.brew.package.remove topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'action': 'remove',
'package': {'id': 4323, 'name': 'python-nose'},
'tag': { 'arches': 'i686 x86_64 ppc ppc64 ppc64le s390 s390x '
'aarch64',
'extra': {},
'id': 9899,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'rhel-7.4-build',
'perm': 'admin',
'perm_id': 1}},
'msg_id': '369459c1-a8ce-4bb6-9778-293c2bfe0c4b',
'timestamp': 1490351237.0,
'topic': '/topic/VirtualTopic.eng.brew.package.remove'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.package.remove |
|
package python-nose was removed from tag rhel-7.4-build |
|
https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=4323 |
|
Unspecified |
|
Unspecified |
|
{‘python-nose’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.package.unblock¶
You can view the history of messages with the eng.brew.package.unblock topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'action': 'unblock',
'package': {'id': 61658, 'name': 'rdma-core'},
'tag': { 'arches': None,
'extra': {},
'id': 9894,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'rhel-7.4',
'perm': 'admin',
'perm_id': 1}},
'msg_id': 'aa80f510-feec-4577-8886-b2645b4de58b',
'timestamp': 1489765815.0,
'topic': '/topic/VirtualTopic.eng.brew.package.unblock'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.package.unblock |
|
package rdma-core was unblocked in tag rhel-7.4 |
|
https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=61658 |
|
Unspecified |
|
Unspecified |
|
{‘rdma-core’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.package.update¶
You can view the history of messages with the eng.brew.package.update topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'action': 'update',
'block': False,
'extra_arches': None,
'force': True,
'owner': 746,
'package': {'id': 12877, 'name': 'iotop'},
'tag': { 'arches': None,
'extra': {},
'id': 10819,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'rhel-7.4-set',
'perm': 'admin',
'perm_id': 1},
'update': True},
'msg_id': '93d5cf48-d6ad-4a42-90cf-3b790f6e2bb9',
'timestamp': 1490709503.0,
'topic': '/topic/VirtualTopic.eng.brew.package.update'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.package.update |
|
package iotop was updated in tag rhel-7.4-set |
|
https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=12877 |
|
Unspecified |
|
Unspecified |
|
{‘iotop’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.repo.done¶
You can view the history of messages with the eng.brew.repo.done topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'data': { 'x86_64': [ 'tasks/8792/12918792',
[ '1e4feca4ea3d5f598d1be8666d90a4af0c803316a0ffa166f1023c666237f374-comps.xml.gz',
'primary.xml.gz',
'c7ac64e14242c5417436cfc10225f4a559d989a180ece78769a68542d1916839-other.sqlite.bz2',
'f143b4220b9237fe62c6a5ae699f270d1cc0fe9b9c44582e1f85bf5a40ab21dc-filelists.sqlite.bz2',
'repomd.xml',
'781f361c7323db0891e799b16c0cb3f30102259d56e3a63869d6a8b1a7a8d9a9-comps.xml.gz',
'filelists.xml.gz',
'other.xml.gz',
'1b05ee5edf3b6b2b598cb3dcb55a38a45b267ae9ae5f08374dcf0180d04f3c9e-primary.xml.gz',
'84ea58b0b9889961fc0f706f69763fde8ca463f9fe2a5694fadf459d130592f9-comps.xml',
'91ab4470004bdae24e8e8a16f43c025c451923f3fa0eb632226ecdc7dff44b4d-primary.sqlite.bz2',
'6e230ed35977838a9c5a68281948788dc9efa7359b1029450c8c152297d091c9-filelists.xml.gz',
'9b0e3103f1f2a6e46d1f2739b5e571018e9508b056e1b81bd7bef2bbbe34c9d5-other.xml.gz',
'38cd9b4022b5adf14ebed57de9195a83a7b2538abac4ce01879bde1f014d35b7-comps.xml']]},
'expire': False,
'repo': { 'create_event': 15291857,
'create_ts': 1490972501.10624,
'creation_time': '2017-03-31 15:01:41.106243',
'id': 1961874,
'state': 0,
'tag_id': 6626,
'tag_name': 'jb-eap-6.3-jdk7-rhel-6-build'}},
'msg_id': 'b99b6445-f8cb-4532-a7b3-1cb06540439e',
'timestamp': 1490973142.0,
'topic': '/topic/VirtualTopic.eng.brew.repo.done'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.repo.done |
|
repo 1961874 for jb-eap-6.3-jdk7-rhel-6-build has been created |
|
https://brewweb.engineering.redhat.com/brew/taginfo?tagID=6626 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.repo.init¶
You can view the history of messages with the eng.brew.repo.init topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'event': None,
'repo_id': 1961878,
'tag': { 'arches': 'i686 x86_64 ppc ppc64 ppc64le s390 s390x '
'aarch64',
'extra': {},
'id': 9899,
'locked': False,
'maven_include_all': False,
'maven_support': False,
'name': 'rhel-7.4-build',
'perm': 'admin',
'perm_id': 1},
'with_debuginfo': False,
'with_src': False},
'msg_id': '806a55b1-5014-43a5-9362-817c090996be',
'signature': None,
'source_version': '0.6.5',
'timestamp': 1490973066.0,
'topic': '/topic/VirtualTopic.eng.brew.repo.init'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.repo.init |
|
repo 1961878 for rhel-7.4-build is being created |
|
https://brewweb.engineering.redhat.com/brew/taginfo?tagID=9899 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.sign.rpm¶
You can view the history of messages with the eng.brew.sign.rpm topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'build': { 'build_id': 549993,
'completion_time': '2017-04-10 14:12:25.27925',
'completion_ts': 1491833545.27925,
'creation_event_id': 15394787,
'creation_time': '2017-04-10 13:55:25.254418',
'creation_ts': 1491832525.25442,
'epoch': None,
'extra': None,
'id': 549993,
'name': 'libvirt',
'nvr': 'libvirt-3.2.0-2.el7',
'owner_id': 798,
'owner_name': 'jdenemar',
'package_id': 1989,
'package_name': 'libvirt',
'release': '2.el7',
'source': None,
'start_time': '2017-04-10 13:55:25.254418',
'start_ts': 1491832525.25442,
'state': 1,
'task_id': 12980391,
'version': '3.2.0',
'volume_id': 0,
'volume_name': 'DEFAULT'},
'rpm': { 'arch': 'x86_64',
'build_id': 549993,
'buildroot_id': 3284277,
'buildtime': 1491832854,
'epoch': None,
'external_repo_id': 0,
'external_repo_name': 'INTERNAL',
'extra': None,
'id': 4634284,
'metadata_only': False,
'name': 'libvirt-devel',
'payloadhash': '3ef74d49c41e85c9979a149c3d05275d',
'release': '2.el7',
'size': 300924,
'version': '3.2.0'},
'sighash': 'fc030b062b00969ece88b42099adc306',
'sigkey': 'fd431d51'},
'msg_id': '80d5593a-db12-49ab-9419-5516bdd55ea8',
'timestamp': 1491937664.0,
'topic': '/topic/VirtualTopic.eng.brew.sign.rpm'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
brew.sign.rpm |
|
libvirt-devel-3.2.0-2.el7.x86_64.rpm has been signed with key fd431d51 |
|
Unspecified |
|
Unspecified |
|
{‘jdenemar’} |
|
{‘libvirt’} |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.assigned¶
You can view the history of messages with the eng.brew.task.assigned topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'noarch',
'awaited': True,
'channel_id': 11,
'completion_time': None,
'completion_ts': None,
'create_time': '2017-03-20 22:08:44.115594',
'create_ts': 1490047724.11559,
'host_id': 176,
'id': 12812517,
'label': 'srpm',
'method': 'buildSRPMFromSCM',
'owner': 2,
'parent': 12812515,
'priority': 19,
'request': [ 'git://pkgs.devel.redhat.com/rpms/ntp?#acd9a8595b68518ded106bb4a7ea8518f6f7c129',
9899,
{'repo_id': 1941359}],
'start_time': '2017-03-20 22:08:44.802256',
'start_ts': 1490047724.80226,
'state': 4,
'waiting': None,
'weight': 1.0},
'new': 'ASSIGNED',
'old': 'OPEN'},
'msg_id': 'b4f23ea0-af61-44d2-b9c1-cf82dffb8470',
'timestamp': 1490047718.0,
'topic': '/topic/VirtualTopic.eng.brew.task.assigned'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
buildSRPMFromSCM task 12812517 has been assigned |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12812517 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.canceled¶
You can view the history of messages with the eng.brew.task.canceled topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'ppc64le',
'awaited': True,
'channel_id': 11,
'completion_time': '2017-03-21 17:48:01.703416',
'completion_ts': 1490118481.70342,
'create_time': '2017-03-21 17:27:02.871697',
'create_ts': 1490117222.8717,
'host_id': 136,
'id': 12822614,
'label': 'ppc64le',
'method': 'buildArch',
'owner': 3344,
'parent': 12822603,
'priority': 19,
'request': [ 'cli-build/1490117191.258269.JHwzgjKh/python-2.7.5-54.el7.src.rpm',
9899,
'ppc64le',
False,
{'repo_id': 1943198}],
'start_time': '2017-03-21 17:27:10.589763',
'start_ts': 1490117230.58976,
'state': 3,
'waiting': None,
'weight': 2.26420799958},
'new': 'CANCELED',
'old': 'OPEN'},
'msg_id': '3cb070b4-faf9-4c80-b6dc-cbe0fa6f5812',
'timestamp': 1490118460.0,
'topic': '/topic/VirtualTopic.eng.brew.task.canceled'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
buildArch task 12822614 has been canceled |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12822614 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.closed¶
You can view the history of messages with the eng.brew.task.closed topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'i386',
'awaited': True,
'channel_id': 9,
'completion_time': '2017-03-20 23:35:26.957282',
'completion_ts': 1490052926.95728,
'create_time': '2017-03-20 22:40:53.128651',
'create_ts': 1490049653.12865,
'host_id': 147,
'id': 12812639,
'label': 'i686',
'method': 'buildArch',
'owner': 2121,
'parent': 12812634,
'priority': 19,
'request': [ 'cli-build/1490047793.281109.ZJGYFfrz/kernel-2.6.32-504.38.1.el6.01739954.src.rpm',
9114,
'i686',
False,
{'repo_id': 1939802}],
'result': { 'brootid': 3253546,
'logs': [ 'tasks/2639/12812639/build.log',
'tasks/2639/12812639/root.log',
'tasks/2639/12812639/state.log'],
'rpms': [ 'tasks/2639/12812639/kernel-debug-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-debuginfo-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/perf-debuginfo-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/python-perf-debuginfo-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-debuginfo-common-i686-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-devel-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-headers-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/python-perf-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/perf-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-debug-devel-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-debug-debuginfo-2.6.32-504.38.1.el6.01739954.i686.rpm',
'tasks/2639/12812639/kernel-2.6.32-504.38.1.el6.01739954.i686.rpm'],
'srpms': []},
'start_time': '2017-03-20 22:41:16.799812',
'start_ts': 1490049676.79981,
'state': 2,
'waiting': None,
'weight': 2.93294190937},
'new': 'CLOSED',
'old': 'OPEN'},
'msg_id': 'f5aabce8-abf4-4607-86da-bf8ac4668144',
'timestamp': 1490052905.0,
'topic': '/topic/VirtualTopic.eng.brew.task.closed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
buildArch task 12812639 has completed |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12812639 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.failed¶
You can view the history of messages with the eng.brew.task.failed topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'x86_64',
'awaited': True,
'channel_id': 11,
'completion_time': '2017-03-21 22:18:59.777722',
'completion_ts': 1490134739.77772,
'create_time': '2017-03-21 21:34:20.977687',
'create_ts': 1490132060.97769,
'host_id': 110,
'id': 12826300,
'label': 'x86_64',
'method': 'buildArch',
'owner': 740,
'parent': 12826299,
'priority': 19,
'request': [ 'cli-build/1490131138.120602.GoxqgsQj/libreoffice-5.0.6.2-6.el7.src.rpm',
10495,
'x86_64',
True,
{'repo_id': 1943876}],
'start_time': '2017-03-21 21:34:35.806375',
'start_ts': 1490132075.80638,
'state': 5,
'waiting': None,
'weight': 6.0},
'new': 'FAILED',
'old': 'OPEN'},
'msg_id': '2a82d688-0679-4312-b03f-cd6434b07f62',
'timestamp': 1490134717.0,
'topic': '/topic/VirtualTopic.eng.brew.task.failed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
buildArch task 12826300 has failed |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12826300 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.free¶
You can view the history of messages with the eng.brew.task.free topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'noarch',
'channel': 'createrepo',
'channel_id': 2,
'id': 18064,
'label': None,
'method': 'newRepo',
'owner': 1,
'parent': None,
'priority': 15,
'request': "<?xml version='1.0'?>\n"
'<methodCall>\n'
'<methodName>newRepo</methodName>\n'
'<params>\n'
'<param>\n'
'<value><string>rhel-7.4-candidate</string></value>\n'
'</param>\n'
'</params>\n'
'</methodCall>\n',
'state': 0},
'new': 'FREE',
'old': None},
'msg_id': '239f9b70-84cb-4774-9365-dfbf0264602b',
'timestamp': 1488318030.0,
'topic': '/topic/VirtualTopic.eng.brew.task.free'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
newRepo task 18064 has been created |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=18064 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.brew.task.open¶
You can view the history of messages with the eng.brew.task.open topic or all brew messages in datagrepper.
{ 'i': 0,
'msg': { 'attribute': 'state',
'info': { 'arch': 'noarch',
'awaited': None,
'channel_id': 11,
'completion_time': None,
'completion_ts': None,
'create_time': '2017-03-20 23:28:12.506607',
'create_ts': 1490052492.50661,
'host_id': 95,
'id': 12812867,
'label': None,
'method': 'build',
'owner': 588,
'parent': None,
'priority': 20,
'request': [ 'git://pkgs.devel.redhat.com/rpms/kernel-rt?#8211e397155a7bc5edc36d3a4499ad53454a2b94',
'rhel-7.4-candidate',
{}],
'start_time': '2017-03-20 23:28:24.071589',
'start_ts': 1490052504.07159,
'state': 1,
'waiting': None,
'weight': 1.0},
'new': 'OPEN',
'old': 'FREE'},
'msg_id': '1c1ed177-d137-403c-bfc2-2905e6171c52',
'timestamp': 1490052482.0,
'topic': '/topic/VirtualTopic.eng.brew.task.open'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
<property object at 0x7f9b9d9d67f0> |
|
build task 12812867 has started |
|
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12812867 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.ci¶
eng.ci.brew-build.test.complete¶
Engineering CI Automation System performs tests to ensure the quality of virtualization packages automatically.
Messages (like the example given here) are published when an CI job is completed.
You can view the history of messages with the eng.ci.brew-build.test.complete topic or all ci messages in datagrepper.
{ 'certificate': 'null',
'crypto': 'null',
'headers': { 'component': 'libvirt',
'content-length': '918',
'destination': '/topic/VirtualTopic.eng.ci.brew-build.test.complete',
'expires': '1531275730696',
'id': '16976169',
'issuer': 'jdenemar',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-41274-1529619027429-3:231921:-1:1:1',
'nvr': 'libvirt-4.5.0-1.el7',
'priority': '4',
'scratch': 'False',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1530670930696',
'type': 'brew-build'},
'i': 0,
'msg': { 'artifact': { 'component': 'libvirt',
'id': '16976169',
'issuer': 'jdenemar',
'nvr': 'libvirt-4.5.0-1.el7',
'scratch': 'false',
'type': 'brew-build'},
'category': 'functional',
'ci': { 'email': 'gsun@redhat.com',
'irc': '#libvirt-auto',
'name': 'Libvirt CI',
'team': 'Libvirt QE',
'url': 'https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com'},
'namespace': 'libvirt-ci',
'note': 'Submit by Metadash',
'run': { 'log': 'http://qed.lab.eng.pek2.redhat.com/test-results/testresult/e23871e8-7f30-11e8-b238-0a580a8101fd',
'url': 'https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/libvirt-RHEL-7.6-runtest-x86_64-function-migration/9/#rhev'},
'status': 'failed',
'system': {'os': 'RHEL7.6', 'provider': 'beaker'},
'type': 'official'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-41274-1529619027429-3:231921:-1:1:1',
'signature': 'null',
'source_name': 'datanommer',
'source_version': '0.9.0',
'timestamp': 1530670930,
'topic': '/topic/VirtualTopic.eng.ci.brew-build.test.complete',
'username': 'null'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
ci.brew-build.test.complete |
|
Test job for libvirt-4.5.0-1.el7 complete |
|
|
|
Unspecified |
|
Unspecified |
|
{‘libvirt’} |
|
Unspecified |
|
|
|
Unspecified |
eng.cips¶
eng.cips¶
shanks once sent a test message like this one…
You can view the history of messages with the eng.cips topic or all cips messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '38',
'destination': '/topic/VirtualTopic.eng.cips',
'expires': '0',
'message-id': 'ID:somebroker01-43669-1508744086399-2:286434:0:0:2',
'msgnum': '1',
'msgtype': 'test',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '2017-10-27 16:02:12.643878'},
'i': 0,
'msg': {'message': 'This is test message 1.'},
'msg_id': 'ID:somebroker01-43669-1508744086399-2:286434:0:0:2',
'timestamp': 1509120145.0,
'topic': '/topic/VirtualTopic.eng.cips'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cips |
|
None |
|
None |
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.cips.complete¶
CIPS performs basic package sanity testing of rpms.
Messages (like the example given here) are published when an CIPS job is completed. (A CIPS job performs basic sanity testing for the given brew build).
You can view the history of messages with the eng.cips.complete topic or all cips messages in datagrepper.
{ 'certificate': 'null',
'crypto': 'null',
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'component': 'setup-2.8.71-7.el7_4',
'content-length': '1102',
'destination': '/topic/VirtualTopic.eng.cips.complete',
'expires': '0',
'id': '15485779',
'issuer': 'jenkins/some-jenkins',
'message-id': 'ID:somebroker-37288-1518002445552-2:1414297:0:0:1',
'nvr': 'setup-2.8.71-7.el7_4',
'priority': '4',
'scratch': 'true',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'brew-build'},
'i': 0,
'msg': { 'artifact': { 'component': 'setup-2.8.71-7.el7_4',
'id': 15485779,
'issuer': 'jenkins/some-jenkins',
'nvr': 'setup-2.8.71-7.el7_4',
'scratch': 'true',
'type': 'brew-build'},
'category': 'sanity',
'ci': { 'email': 'nobody@redhat.com',
'environment': 'production',
'irc': '#rpm-factory',
'name': 'RPM Factory',
'team': 'rpm-factory',
'url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com'},
'name': 'tier0',
'recipients': [],
'run': { 'log': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1858//console',
'rebuild': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1858//rebuild/parametrized',
'url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1858/'},
'status': 'PASSED',
'system': [ { 'os': 'rhel-7.4-server-x86_64-updated',
'provider': 'openstack'}],
'thread_id': '',
'xunit': ''},
'msg_id': 'ID:somebroker-37288-1518002445552-2:1414297:0:0:1',
'signature': 'null',
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1520336954.0,
'topic': '/topic/VirtualTopic.eng.cips.complete',
'username': 'null'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cips.complete |
|
continuous integration package sanity testing PASSED for component: setup-2.8.71-7.el7_4 with brew task_id: 15485779 |
|
|
|
Unspecified |
|
Unspecified |
|
{‘setup’} |
|
Unspecified |
|
|
|
Unspecified |
eng.cips.end¶
CIPS performs basic package sanity testing of rpms.
Messages (like the example given here) are published when an CIPS job is completed. (A CIPS job performs basic sanity testing for the given brew build).
You can view the history of messages with the eng.cips.end topic or all cips messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'ci_type': 'ci-cips',
'component': 'setup-2.8.71-7.el7_4',
'content-length': '41',
'destination': '/topic/VirtualTopic.eng.cips.completed',
'expires': '0',
'id': '14393825',
'jenkins_build_url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1915/',
'message-id': 'ID:somebroker-43669-1508744086399-2:275325:0:0:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': {'end_time': '2017-10-27T11:47:02+00:00'},
'msg_id': 'ID:somebroker-43669-1508744086399-2:275325:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1509104805.0,
'topic': '/topic/VirtualTopic.eng.cips.end',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cips.end |
|
continuous integration package sanity testing ended for component: setup-2.8.71-7.el7_4 with brew task_id: 14393825 |
|
|
|
Unspecified |
|
Unspecified |
|
{‘setup’} |
|
Unspecified |
|
|
|
Unspecified |
eng.cips.running¶
CIPS performs basic package sanity testing of rpms.
Messages (like the example given here) are published when an CIPS job is running. (A CIPS job performs basic sanity testing for the given brew build).
You can view the history of messages with the eng.cips.running topic or all cips messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'baseline': '',
'component': 'setup-2.8.71-7.el7_4',
'content-length': '778',
'destination': '/topic/VirtualTopic.eng.cips.running',
'expires': '0',
'id': '15508224',
'issuer': 'jenkins/some-jenkins',
'message-id': 'ID:somebroker-34234-1520485687892-2:42911:0:0:1',
'nvr': 'setup-2.8.71-7.el7_4',
'priority': '4',
'scratch': 'true',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'brew-build'},
'i': 0,
'msg': { 'artifact': { 'component': 'setup-2.8.71-7.el7_4',
'id': 15508224,
'issuer': 'jenkins/some-jenkins',
'nvr': 'setup-2.8.71-7.el7_4',
'scratch': 'true',
'type': 'brew-build'},
'category': 'sanity',
'ci': { 'email': 'nobody@redhat.com',
'environment': 'production',
'irc': '#rpm-factory',
'name': 'RPM Factory',
'team': 'rpm-factory',
'url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com'},
'name': 'tier0',
'run': { 'log': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1919//console',
'url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1919/'}},
'msg_id': 'ID:somebroker-34234-1520485687892-2:42911:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1520556343.0,
'topic': '/topic/VirtualTopic.eng.cips.running',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cips.running |
|
continuous integration package sanity testing in progress for component: setup-2.8.71-7.el7_4 with brew task_id: 15508224 |
|
|
|
Unspecified |
|
Unspecified |
|
{‘setup’} |
|
Unspecified |
|
|
|
Unspecified |
eng.cips.start¶
CIPS performs basic package sanity testing of rpms.
Messages (like the example given here) are published when an CIPS job is starting. (A CIPS job performs basic sanity testing for the given brew build).
You can view the history of messages with the eng.cips.start topic or all cips messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'ci_type': 'ci-cips',
'component': 'setup-2.8.71-7.el7_4',
'content-length': '43',
'destination': '/topic/VirtualTopic.eng.cips.starting',
'expires': '0',
'id': '14393825',
'jenkins_build_url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-package-sanity-development/label=ose-slave-tps,provision_arch=x86_64/1915/',
'message-id': 'ID:somebroker-43669-1508744086399-2:275322:0:0:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': {'start_time': '2017-10-27T11:43:51+00:00'},
'msg_id': 'ID:somebroker-43669-1508744086399-2:275322:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1509104627.0,
'topic': '/topic/VirtualTopic.eng.cips.start',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cips.start |
|
continuous integration package sanity testing started for component: setup-2.8.71-7.el7_4 with brew task_id: 14393825 |
|
|
|
Unspecified |
|
Unspecified |
|
{‘setup’} |
|
Unspecified |
|
|
|
Unspecified |
eng.clair¶
eng.clair.command¶
Messages (like the example given here) are published when user manually request scan of Red Hat image
You can view the history of messages with the eng.clair.command topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.command',
'architecture': 'amd64',
'brew_build': 'rhmap-fh-metrics-docker-2.0.0-1',
'content-length': '93',
'correlation-id': '19f27f03-68ae-480e-8aaa-220491678de0',
'destination': '/topic/VirtualTopic.eng.clair.command',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:1568663:0:0:1',
'original-destination': '/topic/VirtualTopic.eng.clair.command',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0',
'user': 'araszka'},
'i': 0,
'msg': { 'architecture': 'amd64',
'brew_build': 'rhmap-fh-metrics-docker-2.0.0-1',
'user': 'araszka'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:1568663:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561927509.0,
'topic': '/topic/VirtualTopic.eng.clair.command',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.command |
|
Scan request: rhmap-fh-metrics-docker-2.0.0-1.amd64 |
|
|
|
Unspecified |
|
{‘araszka’} |
|
{‘rhmap-fh-metrics-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.clair.command¶
Messages (like the example given here) are published when user manually request scan of ISV image
You can view the history of messages with the eng.clair.command topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.command',
'containerProcessStatus': 'SCAN_COMPLETE_CERTIFIED_PASS',
'content-length': '167',
'correlation-id': '13a85146-45cb-48a9-97c0-7a92d5072b8f',
'destination': '/topic/VirtualTopic.eng.clair.command',
'expires': '0',
'imageDigest': 'sha256:0b8363dcca5b19788e84c7642a8a272a7fa1736b0db05614a6cf38e8f3bcf3d4',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:1765358:0:0:1',
'original-destination': '/topic/VirtualTopic.eng.clair.command',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0',
'user': 'araszka'},
'i': 0,
'msg': { 'containerProcessStatus': 'SCAN_COMPLETE_CERTIFIED_PASS',
'imageDigest': 'sha256:0b8363dcca5b19788e84c7642a8a272a7fa1736b0db05614a6cf38e8f3bcf3d4',
'user': 'araszka'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:1765358:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1562157865.0,
'topic': '/topic/VirtualTopic.eng.clair.command',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.command |
|
Scan request: sha256:0b8363dcca5b19788e84c7642a8a272a7fa1736b0db05614a6cf38e8f3bcf3d4 |
|
None |
|
Unspecified |
|
{‘araszka’} |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.clair.notification¶
Unknown format of message
You can view the history of messages with the eng.clair.notification topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.notification',
'content-type': 'application/json',
'correlation-id': '2ccad28b-0a6e-43d9-9376-ee238276fcbf',
'destination': '/topic/VirtualTopic.eng.clair.notification',
'expires': '1561103466372',
'message-id': "ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-' "
"'35238-1560306230293-3:382125:-1:1:122",
'original-destination': '/topic/VirtualTopic.eng.clair.notification',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1561017066372'},
'i': 0,
'msg': 'string-msg',
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-3:382125:-1:1:122',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561017066.0,
'topic': '/topic/VirtualTopic.eng.clair.notification',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
Unspecified |
|
Unknown message format |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.clair.scan¶
Messages (like the example given here) are published when Clair + Wrapper scan and grade new container image
You can view the history of messages with the eng.clair.scan topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.scan',
'arch': 'ppc64le',
'content-length': '154',
'correlation-id': '2ec19d5b-8820-4a9e-b8aa-ea3a11523057',
'destination': '/topic/VirtualTopic.eng.clair.scan',
'expires': '0',
'message-id': "ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.' "
"'com-35238-1560306230293-6:866563:0:0:1",
'nvr': 'openstack-nova-compute-container-14.0-110.1561066899',
'original-destination': '/topic/VirtualTopic.eng.clair.scan',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'arch': 'ppc64le',
'grades': [ { 'grade': 'A',
'start_date': '20190621T06:55:00.000-0400'}],
'image_id': 'sha256:d994ce5745cd63d727d21a0c93d0811942d4e4d054d7704e7240b8e4471edf5f',
'nvr': 'openstack-nova-compute-container-14.0-110.1561066899'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:866563:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561114556.0,
'topic': '/topic/VirtualTopic.eng.clair.scan',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.scan |
|
New image scanned: openstack-nova-compute-container-14.0-110.1561066899.ppc64le (A) |
|
|
|
Unspecified |
|
Unspecified |
|
{‘openstack-nova-compute-container’} |
|
set() |
|
|
|
Unspecified |
eng.clair.scan¶
Messages (like the example given here) are published when Clair + Wrapper scan and grade new container image
You can view the history of messages with the eng.clair.scan topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.scan',
'arch': 'ppc64le',
'content-length': '154',
'correlation-id': '2ec19d5b-8820-4a9e-b8aa-ea3a11523057',
'destination': '/topic/VirtualTopic.eng.clair.scan',
'expires': '0',
'message-id': "ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.' "
"'com-35238-1560306230293-6:866563:0:0:1",
'nvr': 'openstack-nova-compute-container-14.0-110.1561066899',
'original-destination': '/topic/VirtualTopic.eng.clair.scan',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'grades': [ { 'grade': 'A',
'start_date': '20190621T06:55:00.000-0400'}],
'image_id': 'sha256:d994ce5745cd63d727d21a0c93d0811942d4e4d054d7704e7240b8e4471edf5f',
'nvra': 'openstack-nova-compute-container-14.0-110.1561066899.ppc64le'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:866563:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561114556.0,
'topic': '/topic/VirtualTopic.eng.clair.scan',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.scan |
|
New image scanned: openstack-nova-compute-container-14.0-110.1561066899.ppc64le (A) |
|
|
|
Unspecified |
|
Unspecified |
|
{‘openstack-nova-compute-container’} |
|
set() |
|
|
|
Unspecified |
eng.clair.scan.isv¶
Messages (like the example given here) are published when Clair + Wrapper scan and grade new ISV container image
You can view the history of messages with the eng.clair.scan.isv topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.scan.isv',
'content-length': '465',
'correlation-id': '375c97f7-d03f-4f4b-87d5-ce82bb4b4712',
'destination': '/topic/VirtualTopic.eng.clair.scan.isv',
'expires': '0',
'image_id': 'sha256:d994ce5745cd63d727d21a0c93d0811942d4e4d054d7704e7240b8e4471edf5f',
'message-id': "ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-' "
"'1560306230293-6:867825:0:0:1",
'original-destination': '/topic/VirtualTopic.eng.clair.scan.isv',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'grades': [ { 'end_date': '20190720T15:51:00.000-0400',
'grade': 'B',
'start_date': '20190621T07:20:00.000-0400'},
{ 'end_date': '20190918T15:51:00.000-0400',
'grade': 'C',
'start_date': '20190720T15:51:00.000-0400'},
{ 'end_date': '20200619T15:51:00.000-0400',
'grade': 'D',
'start_date': '20190918T15:51:00.000-0400'},
{ 'grade': 'F',
'start_date': '20200619T15:51:00.000-0400'}],
'image_id': 'sha256:d994ce5745cd63d727d21a0c93d0811942d4e4d054d7704e7240b8e4471edf5f'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-6:867825:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561116055.0,
'topic': '/topic/VirtualTopic.eng.clair.scan.isv',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.scan.isv |
|
New image scanned: sha256:d994ce5745cd63d727d21a0c93d0811942d4e4d054d7704e7240b8e4471edf5f (B) |
|
|
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.clair.v4.notification¶
Messages (like the example given here) are published when Clair gets new security vulnerability
You can view the history of messages with the eng.clair.v4.notification topic or all clair messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-clair',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.clair.notification',
'content-type': 'application/json',
'correlation-id': '2ccad28b-0a6e-43d9-9376-ee238276fcbf',
'destination': '/topic/VirtualTopic.eng.clair.notification',
'expires': '1561103466372',
'message-id': "ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-' "
"'35238-1560306230293-3:382125:-1:1:122",
'original-destination': '/topic/VirtualTopic.eng.clair.notification',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1561017066372'},
'i': 0,
'msg': [ { 'id': '001680dd-bf80-49d0-842d-255c06d0d2df',
'manifest': 'sha256:6066f95b13ae8b2c210c60c215ac93401e297f45e59b755ac14d2262157d9fea',
'reason': 'added',
'vulnerability': { 'distribution': { 'arch': '',
'cpe': 'cpe:2.3:o:redhat:enterprise_linux:8:*:*:*:*:*:*:*',
'did': 'rhel',
'id': '',
'name': 'Red Hat Enterprise '
'Linux Server',
'pretty_name': 'Red Hat '
'Enterprise '
'Linux Server '
'8',
'version': '8',
'version_code_name': '',
'version_id': '8'},
'fixed_in_version': '0:6.0.0-25.5.module+el8.2.1+8680+ea98947b',
'links': 'https://access.redhat.com/errata/RHSA-2020:5111',
'name': 'RHSA-2020:5111: virt:8.2 and '
'virt-devel:8.2 security and bug fix '
'update (Moderate)',
'package': { 'arch': 'aarch64|ppc64le|s390x|x86_64',
'cpe': '',
'id': '',
'kind': 'binary',
'module': 'virt:8.2',
'name': 'libvirt-daemon',
'normalized_version': '',
'version': ''},
'repo': { 'cpe': '',
'key': 'rhel-cpe-repository',
'name': 'cpe:/a:redhat:advanced_virtualization:8.2::el8'},
'severity': 'Medium'}},
{ 'id': '009e3b28-ac0f-4bbc-8604-0f0d4ade08a4',
'manifest': 'sha256:30ea340057e23e6be8d6012453e709879ce29a23d9e5482164826ba4aa6ffe2b',
'reason': 'added',
'vulnerability': { 'distribution': { 'arch': '',
'cpe': 'cpe:2.3:o:redhat:enterprise_linux:8:*:*:*:*:*:*:*',
'did': 'rhel',
'id': '',
'name': 'Red Hat Enterprise '
'Linux Server',
'pretty_name': 'Red Hat '
'Enterprise '
'Linux Server '
'8',
'version': '8',
'version_code_name': '',
'version_id': '8'},
'fixed_in_version': '0:6.0.0-25.5.module+el8.2.1+8680+ea98947b',
'links': 'https://access.redhat.com/errata/RHSA-2020:5111',
'name': 'RHSA-2020:5111: virt:8.2 and '
'virt-devel:8.2 security and bug fix '
'update (Moderate)',
'package': { 'arch': 'aarch64|ppc64le|s390x|x86_64',
'cpe': '',
'id': '',
'kind': 'binary',
'module': 'virt:8.2',
'name': 'libvirt-daemon',
'normalized_version': '',
'version': ''},
'repo': { 'cpe': '',
'key': 'rhel-cpe-repository',
'name': 'cpe:/a:redhat:advanced_virtualization:8.2::el8'},
'severity': 'Medium'}},
{ 'id': '00ae7a5b-bd08-468a-b3c6-dc95c249a435',
'manifest': 'sha256:05c7ad6e08d7f2203b5c35cfeabd7fd423959f5cfcdefc32d07b5a1e6e0581dc',
'reason': 'removed',
'vulnerability': { 'distribution': { 'arch': '',
'cpe': 'cpe:2.3:o:redhat:enterprise_linux:8:*:*:*:*:*:*:*',
'did': 'rhel',
'id': '',
'name': 'Red Hat Enterprise '
'Linux Server',
'pretty_name': 'Red Hat '
'Enterprise '
'Linux Server '
'8',
'version': '8',
'version_code_name': '',
'version_id': '8'},
'fixed_in_version': '0:6.0.0-25.5.module+el8.2.1+8680+ea98947b',
'links': 'https://access.redhat.com/errata/RHSA-2020:5111',
'name': 'RHSA-2020:5111: virt:8.2 and '
'virt-devel:8.2 security and bug fix '
'update (Moderate)',
'package': { 'arch': 'aarch64|ppc64le|s390x|x86_64',
'cpe': '',
'id': '',
'kind': 'binary',
'module': 'virt:8.2',
'name': 'libvirt-daemon',
'normalized_version': '',
'version': ''},
'repo': { 'cpe': '',
'key': 'rhel-cpe-repository',
'name': 'cpe:/a:redhat:advanced_virtualization:8.2::el8'},
'severity': 'Medium'}}],
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-35238-1560306230293-3:382125:-1:1:122',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1561017066.0,
'topic': '/topic/VirtualTopic.eng.clair.v4.notification',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
clair.v4.notification |
|
New notification - added: 2, removed: 1 vulnerabilities |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.cts¶
eng.cts.compose-changed¶
Compose Tracking Service (CTS) stored metadata about composes created in various services.
Here’s an example message published when a compose is changed in CTS.
You can view the history of messages with the eng.cts.compose-changed topic or all cts messages in datagrepper.
{ 'msg': { 'compose': { 'builder': 'odcs/odcs.example.com',
'children': [],
'compose_info': { 'header': { 'type': 'productmd.composeinfo',
'version': '1.2'},
'payload': { 'compose': { 'date': '20210511',
'final': False,
'id': 'TEST-1-20210511.1',
'label': 'Beta-1.0',
'respin': 1,
'type': 'production'},
'release': { 'internal': False,
'name': 'TEST',
'short': 'TEST',
'type': 'ga',
'version': '1'},
'variants': {}}},
'parents': [],
'respin_of': None,
'respun_by': [],
'tags': []},
'event': 'compose-changed'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.cts.compose-changed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cts.compose-changed |
|
Compose TEST-1-20210511.1 was changed |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.cts.compose-created¶
Compose Tracking Service (CTS) stored metadata about composes created in various services.
Here’s an example message published when a compose is created in CTS.
You can view the history of messages with the eng.cts.compose-created topic or all cts messages in datagrepper.
{ 'msg': { 'compose': { 'builder': 'odcs/odcs.example.com',
'children': [],
'compose_info': { 'header': { 'type': 'productmd.composeinfo',
'version': '1.2'},
'payload': { 'compose': { 'date': '20210511',
'final': False,
'id': 'TEST-1-20210511.1',
'label': 'Beta-1.0',
'respin': 1,
'type': 'production'},
'release': { 'internal': False,
'name': 'TEST',
'short': 'TEST',
'type': 'ga',
'version': '1'},
'variants': {}}},
'parents': [],
'respin_of': None,
'respun_by': [],
'tags': []},
'event': 'compose-created'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.cts.compose-created'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cts.compose-created |
|
Compose TEST-1-20210511.1 was created |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.cts.compose-tagged¶
Compose Tracking Service (CTS) stored metadata about composes created in various services.
Here’s an example message published when a tag is added to a compose in CTS.
You can view the history of messages with the eng.cts.compose-tagged topic or all cts messages in datagrepper.
{ 'msg': { 'compose': { 'builder': 'odcs/odcs.example.com',
'children': [],
'compose_info': { 'header': { 'type': 'productmd.composeinfo',
'version': '1.2'},
'payload': { 'compose': { 'date': '20210511',
'final': False,
'id': 'TEST-1-20210511.1',
'label': 'Beta-1.0',
'respin': 1,
'type': 'production'},
'release': { 'internal': False,
'name': 'TEST',
'short': 'TEST',
'type': 'ga',
'version': '1'},
'variants': {}}},
'parents': [],
'respin_of': None,
'respun_by': [],
'tags': ['nightly-requested']},
'event': 'compose-tagged',
'tag': 'nightly-requested'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.cts.compose-tagged'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cts.compose-tagged |
|
Compose TEST-1-20210511.1 was tagged with nightly-requested |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.cts.compose-untagged¶
Compose Tracking Service (CTS) stored metadata about composes created in various services.
Here’s an example message published when a tag is removed from a compose in CTS.
You can view the history of messages with the eng.cts.compose-untagged topic or all cts messages in datagrepper.
{ 'msg': { 'compose': { 'builder': 'odcs/odcs.example.com',
'children': [],
'compose_info': { 'header': { 'type': 'productmd.composeinfo',
'version': '1.2'},
'payload': { 'compose': { 'date': '20210511',
'final': False,
'id': 'TEST-1-20210511.1',
'label': 'Beta-1.0',
'respin': 1,
'type': 'production'},
'release': { 'internal': False,
'name': 'TEST',
'short': 'TEST',
'type': 'ga',
'version': '1'},
'variants': {}}},
'parents': [],
'respin_of': None,
'respun_by': [],
'tags': []},
'event': 'compose-untagged',
'tag': 'nightly-requested'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.cts.compose-untagged'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
cts.compose-untagged |
|
Compose TEST-1-20210511.1 was untagged with nightly-requested |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.distgit¶
eng.distgit.commit¶
The Dist-Git system manages collections of git repositories.
A commit message is published for every commit that is pushed to a repo.
You can view the history of messages with the eng.distgit.commit topic or all distgit messages in datagrepper.
{ 'headers': { 'agent': 'steved',
'branch': 'rhel-7.4',
'content-length': '666',
'destination': '/topic/VirtualTopic.eng.distgit.commit',
'email': 'steved@redhat.com',
'expires': '0',
'message-id': 'ID\\cmessaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4\\c171881\\c0\\c0\\c1',
'name': 'Steve Dickson',
'namespace': 'rpms',
'path': '/srv/git/rpms/rpcbind.git',
'repo': 'rpcbind',
'rev': '42bcbca202b35ae663bdbca9e10b64d4a5dfbf5a',
'seen': 'false',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'timestamp': '0',
'username': 'steved'},
'i': 0,
'msg': { 'agent': 'steved',
'branch': 'rhel-7.4',
'email': 'steved@redhat.com',
'message': 'Fixed memory leaks (bz 1449456)\n'
'\n'
'Signed-off-by: Steve Dickson <steved@redhat.com>\n'
'Resolves: bz1449456\n',
'name': 'Steve Dickson',
'namespace': 'rpms',
'path': '/srv/git/rpms/rpcbind.git',
'repo': 'rpcbind',
'rev': '42bcbca202b35ae663bdbca9e10b64d4a5dfbf5a',
'seen': False,
'stats': { 'files': { 'rpcbind-0.2.0-memleaks.patch': { 'additions': 177,
'deletions': 0,
'lines': 177},
'rpcbind.spec': { 'additions': 8,
'deletions': 2,
'lines': 10}},
'total': { 'additions': 185,
'deletions': 2,
'files': 2,
'lines': 187}},
'summary': 'Fixed memory leaks (bz 1449456)',
'username': 'steved'},
'msg_id': 'ID\\cmessaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4\\c171881\\c0\\c0\\c1',
'timestamp': 1494525626.0,
'topic': '/topic/VirtualTopic.eng.distgit.commit'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
distgit.commit |
|
42bcbca2 was committed on the rhel-7.4 branch of the rpcbind rpm repo by steved |
|
https://pipeline.engineering.redhat.com/distgitcommit/42bcbca202b35ae663bdbca9e10b64d4a5dfbf5a |
|
steved |
|
{‘steved’} |
|
{‘rpcbind’} |
|
Unspecified |
|
|
|
Unspecified |
eng.distgit.push¶
The Dist-Git system manages collections of git repositories.
A push message is published for every branch updated by a “git push”. This is a message representing a push which updates a branch with a single commit.
You can view the history of messages with the eng.distgit.push topic or all distgit messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'branch': 'rhel-8.0',
'content-length': '312',
'destination': '/topic/VirtualTopic.eng.distgit.push',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34380-1520940284355-18:52484:0:0:1',
'namespace': 'rpms',
'newrev': '9d3d09ed37b4450bbff8c45527a7d75297626633',
'numcommits': '1',
'oldrev': '0000000000000000000000000000000000000000',
'path': '/srv/git/rpms/httpd.git',
'priority': '4',
'repo': 'httpd',
'subscription': '/queue/Consumer.client-datanommer.openpaas-stage.VirtualTopic.eng.>',
'timestamp': '0',
'username': 'mikeb'},
'i': 0,
'msg': { 'branch': 'rhel-8.0',
'commits': ['9d3d09ed37b4450bbff8c45527a7d75297626633'],
'namespace': 'rpms',
'newrev': '9d3d09ed37b4450bbff8c45527a7d75297626633',
'numcommits': 1,
'oldrev': '0000000000000000000000000000000000000000',
'path': '/srv/git/rpms/httpd.git',
'repo': 'httpd',
'username': 'mikeb'},
'msg_id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34380-1520940284355-18:52484:0:0:1',
'timestamp': 1521512774.0,
'topic': '/topic/VirtualTopic.eng.distgit.push'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
distgit.push |
|
1 commit was pushed to the rhel-8.0 branch of the httpd rpm repo by mikeb |
|
https://pkgs.devel.redhat.com/cgit/rpms/httpd/log/?h=rhel-8.0 |
|
mikeb |
|
{‘mikeb’} |
|
{‘httpd’} |
|
Unspecified |
|
|
|
Unspecified |
eng.distgit.push¶
The Dist-Git system manages collections of git repositories.
A push message is published for every branch updated by a “git push”. This is a message representing a push which updates a branch with multiple commits.
You can view the history of messages with the eng.distgit.push topic or all distgit messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'branch': 'rhel-7.5',
'content-length': '356',
'destination': '/topic/VirtualTopic.eng.distgit.push',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34380-1520940284355-18:52505:0:0:1',
'namespace': 'rpms',
'newrev': 'b904064468acb97fe0a7a00165979d19a462ec0b',
'numcommits': '3',
'oldrev': '9d3d09ed37b4450bbff8c45527a7d75297626633',
'path': '/srv/git/rpms/ntp.git',
'priority': '4',
'repo': 'ntp',
'subscription': '/queue/Consumer.client-datanommer.openpaas-stage.VirtualTopic.eng.>',
'timestamp': '0',
'username': 'mikeb'},
'i': 0,
'msg': { 'branch': 'rhel-7.5',
'commits': [ 'b426cb95170fc4308828f640a75975410771c7af',
'a0f167a36048c77f84c57507873995614ce07bc8',
'b904064468acb97fe0a7a00165979d19a462ec0b'],
'namespace': 'rpms',
'newrev': 'b904064468acb97fe0a7a00165979d19a462ec0b',
'numcommits': 3,
'oldrev': '9d3d09ed37b4450bbff8c45527a7d75297626633',
'path': '/srv/git/rpms/ntp.git',
'repo': 'ntp',
'username': 'mikeb'},
'msg_id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34380-1520940284355-18:52505:0:0:1',
'timestamp': 1521513184.0,
'topic': '/topic/VirtualTopic.eng.distgit.push'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
distgit.push |
|
3 commits were pushed to the rhel-7.5 branch of the ntp rpm repo by mikeb |
|
|
|
mikeb |
|
{‘mikeb’} |
|
{‘ntp’} |
|
Unspecified |
|
|
|
Unspecified |
eng.distill¶
eng.distill.compose-finished¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Sometimes, older versions of distill need to be used for older products (to ensure the metadata is compatible).
Here’s an example message published when a compose completes.
You can view the history of messages with the eng.distill.compose-finished topic or all distill messages in datagrepper.
{ 'msg': { 'compose-id': 'Supp-6.10-RHEL-6-20170703.n.0',
'compose-label': '',
'compose-path': '/mnt/redhat/nightly/Supp-6.10-RHEL-6-20170703.n.0',
'compose-state': 'FINISHED',
'compose-type': 'nightly',
'release-id': 'Supp-6.10-RHEL-6'},
'topic': '/topic/VirtualTopic.eng.distill.compose-finished'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
distill.compose-finished |
|
distill compose of Supp-6.10-RHEL-6-20170703.n.0 just finished |
|
http://download.lab.bos.redhat.com/nightly/Supp-6.10-RHEL-6-20170703.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.distill.compose-started¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Sometimes, older versions of distill need to be used for older products (to ensure the metadata is compatible).
Here’s an example message published when a compose starts.
You can view the history of messages with the eng.distill.compose-started topic or all distill messages in datagrepper.
{ 'msg': { 'compose-id': 'Supp-6.10-RHEL-6-20170703.n.0',
'compose-label': '',
'compose-path': '/mnt/redhat/nightly/Supp-6.10-RHEL-6-20170703.n.0',
'compose-state': 'STARTED',
'compose-type': 'nightly',
'release-id': 'Supp-6.10-RHEL-6'},
'topic': '/topic/VirtualTopic.eng.distill.compose-started'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
distill.compose-started |
|
distill compose of Supp-6.10-RHEL-6-20170703.n.0 started |
|
http://download.lab.bos.redhat.com/nightly/Supp-6.10-RHEL-6-20170703.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.errata¶
eng.errata.activity.assigned_to¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like these appear whenever someone is assigned to an advisory.
You can view the history of messages with the eng.errata.activity.assigned_to topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.assigned_to',
'errata_id': '28809',
'errata_status': 'QE',
'expires': '0',
'from': 'kernel-qe@redhat.com',
'fulladvisory': 'RHBA-2017:28809-02',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:482002:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.assigned_to',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'kernel bug fix update',
'timestamp': '0',
'to': 'rbean@redhat.com',
'type': 'errata.activity.assigned_to',
'when': '2017-06-01 02:35:03 UTC',
'who': 'cye@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:482002:0:0:1',
'timestamp': 1496284509.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.assigned_to'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.assigned_to |
|
cye assigned rbean to RHBA-2017:28809-02 |
|
|
|
cye |
|
{‘rbean’, ‘kernel-qe’, ‘cye’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.batch¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone changes the batch associated with an advisory.
You can view the history of messages with the eng.errata.activity.batch topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.batch',
'errata_id': '28445',
'errata_status': 'QE',
'expires': '0',
'from': 'null',
'fulladvisory': 'RHEA-2017:28445-03',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478875:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.batch',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'New Red Hat Enterprise Linux Atomic Container '
'Engine Container Image',
'timestamp': '0',
'to': 'RHEL-7.3.6-Containers',
'type': 'errata.activity.batch',
'when': '2017-05-31 22:16:04 UTC',
'who': 'lfriedma@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478875:0:0:1',
'timestamp': 1496268967.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.batch'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.batch |
|
lfriedma added RHEA-2017:28445-03 to the RHEL-7.3.6-Containers advisory batch |
|
|
|
lfriedma |
|
{‘lfriedma’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.created¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like this one are published when an advisory is created.
You can view the history of messages with the eng.errata.activity.created topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.created',
'errata_id': '28816',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:480845:0:0:1',
'persistent': 'true',
'priority': '4',
'release': 'Sat-Tools-6.2-ASYNC',
'subject': 'errata.activity.created',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'Satellite Tools 6.2.10 Async Bug Release',
'timestamp': '0',
'type': 'RHBA',
'when': '2017-05-31 23:29:54 UTC',
'who': 'bkearney@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:480845:0:0:1',
'source_version': '0.7.0',
'timestamp': 1496273395.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.created',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.created |
|
bkearney filed a new RHBA advisory for Sat-Tools-6.2-ASYNC |
|
|
|
bkearney |
|
{‘bkearney’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.docs_approval¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like these appear whenever someone approves the docs on an advisory.
You can view the history of messages with the eng.errata.activity.docs_approval topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.docs_approval',
'errata_id': '27244',
'errata_status': 'QE',
'expires': '0',
'from': 'null',
'fulladvisory': 'RHBA-2017:27244-01',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:481523:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.docs_approval',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'openstack-packstack and openstack-puppet-modules '
'bug fix advisory',
'timestamp': '0',
'to': 'docs_approved',
'type': 'errata.activity.docs_approval',
'when': '2017-06-01 01:16:31 UTC',
'who': 'lbopf@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:481523:0:0:1',
'timestamp': 1496279793.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.docs_approval'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.docs_approval |
|
lbopf approved the docs on RHBA-2017:27244-01 |
|
|
|
lbopf |
|
{‘lbopf’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.security_approved¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like this one are published when someone requests security approval.
You can view the history of messages with the eng.errata.activity.security_approved topic or all errata messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'errata_id': '10000',
'errata_status': 'QE',
'expires': '0',
'from': 'null',
'fulladvisory': 'RHSA-2016:10000-01',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:481029:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.security_approved',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'A mocked security update. Not a real example.',
'timestamp': '0',
'to': '0',
'type': 'errata.activity.security_approved',
'when': '2016-01-01 00:00:01 UTC',
'who': 'rbean@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:481029:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.7.0',
'timestamp': 1496275955.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.security_approved |
|
rbean requested security approval on RHSA-2016:10000-01 |
|
|
|
rbean |
|
{‘rbean’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.security_approved¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like this one are published when someone grants security approval.
You can view the history of messages with the eng.errata.activity.security_approved topic or all errata messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-client-errata',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.errata.activity.security_approved',
'correlation-id': 'c547d12f-d41e-44cf-a45c-7538ac436f22',
'destination': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'errata_id': '58034',
'errata_status': 'REL_PREP',
'expires': '0',
'from': '0',
'fulladvisory': 'RHSA-2020:58034-03',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-45945-1594124283720-5:3843970:0:0:1',
'original-destination': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'persistent': 'true',
'priority': '4',
'product': 'RHEL',
'release': 'RHEL-7.8.Z',
'subject': 'errata.activity.security_approved',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'synopsis': 'Important: thunderbird security update',
'timestamp': '0',
'to': '1',
'type': 'RHSA',
'when': '2020-08-05 23:45:44 UTC',
'who': 'dmoppert@redhat.com'},
'i': 0,
'msg': { 'content_types': ['rpm'],
'errata_id': 58034,
'errata_status': 'REL_PREP',
'from': '0',
'fulladvisory': 'RHSA-2020:58034-03',
'product': 'RHEL',
'release': 'RHEL-7.8.Z',
'synopsis': 'Important: thunderbird security update',
'to': '1',
'type': 'RHSA',
'when': '2020-08-05 23:45:44 UTC',
'who': 'dmoppert@redhat.com'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-45945-1594124283720-5:3843970:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1596671149,
'topic': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.security_approved |
|
dmoppert approved the security request on RHSA-2020:58034-03 |
|
|
|
dmoppert |
|
{‘dmoppert’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.security_approved¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like this one are published when someone changes the security approval value.
You can view the history of messages with the eng.errata.activity.security_approved topic or all errata messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-client-errata',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.errata.activity.security_approved',
'correlation-id': '6462cedc-b0bf-4d6d-9700-4713f5166857',
'destination': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'errata_id': '58035',
'errata_status': 'QE',
'expires': '0',
'from': 'foo',
'fulladvisory': 'RHSA-2020:58035-03',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-45945-1594124283720-5:3843827:0:0:1',
'original-destination': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'persistent': 'true',
'priority': '4',
'product': 'RHEL',
'release': 'RHEL-6.10.z',
'subject': 'errata.activity.security_approved',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'synopsis': 'Important: thunderbird security update',
'timestamp': '0',
'to': 'bar',
'type': 'RHSA',
'when': '2020-08-05 23:43:56 UTC',
'who': 'dmoppert@redhat.com'},
'i': 0,
'msg': { 'content_types': ['rpm'],
'errata_id': 58035,
'errata_status': 'QE',
'from': 'foo',
'fulladvisory': 'RHSA-2020:58035-03',
'product': 'RHEL',
'release': 'RHEL-6.10.z',
'synopsis': 'Important: thunderbird security update',
'to': 'bar',
'type': 'RHSA',
'when': '2020-08-05 23:43:56 UTC',
'who': 'dmoppert@redhat.com'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-45945-1594124283720-5:3843827:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1596671040,
'topic': '/topic/VirtualTopic.eng.errata.activity.security_approved',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.security_approved |
|
dmoppert set the security flag from “foo” to “bar” on RHSA-2020:58035-03 |
|
|
|
dmoppert |
|
{‘dmoppert’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.signing¶
The Errata Tool supports the release workflow for Red Hat content.
The Errata Tool pumps out messages like this one when cryptographic signatures are attached to builds (which are in turn attached to advisories).
You can view the history of messages with the eng.errata.activity.signing topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.signing',
'errata_id': '26924',
'errata_status': 'QE',
'expires': '0',
'from': 'null',
'fulladvisory': 'RHBA-2017:26924-01',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:479960:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.signing',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'gssproxy bug fix and enhancement update',
'timestamp': '0',
'to': 'gssproxy-0.7.0-4.el7',
'type': 'errata.activity.signing',
'when': '2017-05-31 22:50:02 UTC',
'who': 'robosignatory/robosignatory.host.prod.eng.bos.redhat.com@REDHAT.COM'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:479960:0:0:1',
'timestamp': 1496271000.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.signing'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.signing |
|
robosignatory reported signing gssproxy-0.7.0-4.el7 for RHBA-2017:26924-01 |
|
|
|
robosignatory |
|
{‘robosignatory’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.status¶
The Errata Tool supports the release workflow for Red Hat content.
Messages are published when an advisory changes state. This is an example of an advisory moving from the QE state back to the NEW_FILES state (for modification by developers).
You can view the history of messages with the eng.errata.activity.status topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.status',
'errata_id': '27087',
'errata_status': 'NEW_FILES',
'expires': '0',
'from': 'QE',
'fulladvisory': 'RHBA-2017:27087-02',
'message-id': 'ID\\cmessaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4\\c472412\\c0\\c0\\c1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.activity.status',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'synopsis': 'mutter/shell/extensions bug fix and enhancement '
'update',
'timestamp': '0',
'to': 'NEW_FILES',
'type': 'errata.activity.status',
'when': '2017-05-31 17:35:24 UTC',
'who': 'fmuellne@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID\\cmessaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4\\c472412\\c0\\c0\\c1',
'timestamp': 1496252132.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.status',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.status |
|
fmuellne moved RHBA-2017:27087-02 from QE to NEW_FILES |
|
|
|
fmuellne |
|
{‘fmuellne’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.activity.text_changes¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone changes the text in a field of an advisory.
You can view the history of messages with the eng.errata.activity.text_changes topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.activity.text_changes',
'errata_id': '30821',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:51216:0:0:1',
'persistent': 'true',
'priority': '4',
'product': 'JBEAP',
'release': 'RHEL-7-JBEAP-6.4',
'subject': 'errata.activity.text_changes',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'RHSA',
'when': '2018-01-23 08:16:46 UTC',
'who': 'bkundal@redhat.com'},
'i': 0,
'msg': { 'errata_id': 30821,
'product': 'JBEAP',
'release': 'RHEL-7-JBEAP-6.4',
'text_changes': [ { 'from': 'None',
'name': 'security_impact',
'to': 'Important'},
{ 'from': 'Red Hat JBoss Enterprise Application '
'Platform 6.4.19 update on RHEL 7',
'name': 'synopsis',
'to': 'Important: Red Hat JBoss Enterprise '
'Application Platform 6.4.19 update on '
'RHEL 7'},
{ 'from': '',
'name': 'cve',
'to': 'CVE-2017-12617 CVE-2018-1041 '
'CVE-2017-12174'},
{ 'from': 'Updated packages that provide Red Hat '
'JBoss Enterprise Application Platform '
'6.4.19 and fix several bugs,and add '
'various enhancements are now available '
'for Red Hat Enterprise Linux 7.',
'name': 'topic',
'to': 'An update is now available for Red Hat '
'JBoss Enterprise Application Platform '
'6.4 for Red Hat Enterprise Linux 6.\n'
'\n'
'Red Hat Product Security has rated this '
'update as having a security impact of '
'Important.A Common Vulnerability Scoring '
'System (CVSS) base score,which gives a '
'detailed severity rating,is available '
'for each vulnerability from the CVE '
'link(s) in the References section.'},
{ 'from': 'Red Hat JBoss Enterprise Application '
'Platform 6 is a platform for Java\n'
'applications based on JBoss '
'Application Server 7. \n'
'\n'
'This release serves as a replacement '
'for Red Hat JBoss Enterprise '
'Application\n'
'Platform 6.4.18,and includes bug fixes '
'and enhancements. Documentation for '
'these\n'
'changes will be available shortly from '
'the Red Hat JBoss Enterprise '
'Application\n'
'Platform 6.4.19 Release Notes,linked '
'to in the References. \n'
'\n'
'All users of Red Hat JBoss Enterprise '
'Application Platform 6.4 on Red Hat\n'
'Enterprise Linux 7 are advised to '
'upgrade to these updated packages. The '
'JBoss\n'
'server process must be restarted for '
'the update to take effect.',
'name': 'description',
'to': 'Red Hat JBoss Enterprise Application '
'Platform is a platform for Java\n'
'applications based on the JBoss '
'Application Server.\n'
'\n'
'This release of Red Hat JBoss Enterprise '
'Application Platform 6.4.19 serves as a '
'replacement for Red Hat JBoss Enterprise '
'Application Platform 6.4.18,and includes '
'bug fixes and enhancements,which are '
'documented in the Release Notes document '
'linked to in the References.\n'
'\n'
'Security Fix(es):\n'
'\n'
'* It was found that when Artemis and '
'HornetQ are configure with UDP discovery '
'and JGroups discovery create huge byte '
'array when receiving unexpected '
'multicast message and may result in heap '
'memory exhaustion ,full GC and '
'OutOfMemoryError. (CVE-2017-12174)\n'
'\n'
'* A vulnerability was discovered in '
'Tomcat where if a servlet context was\n'
'configured with readonly=false and HTTP '
'PUT requests were allowed,an\n'
'attacker could upload a JSP file to that '
'context and achieve code\n'
'execution. (CVE-2017-12617)\n'
'\n'
'* A vulnerability was found in the way '
'RemoteMessageChannel,introduced in\n'
'jboss-remoting versions '
'3.3.10.Final-redhat-1,reads from an '
'empty buffer.\n'
'An attacker could use this flaw to cause '
'denial of service via high CPU\n'
'caused by an infinite loop. '
'(CVE-2018-1041)\n'
'\n'
'The CVE-2017-12174 issue was discovered '
'by Masafumi Miura (Red Hat).'},
{ 'from': 'https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/index.html',
'name': 'reference',
'to': 'https://access.redhat.com/security/updates/classification/#important\n'
'https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/'}],
'type': 'RHSA',
'when': '2018-01-23 08:16:46 UTC',
'who': 'bkundal@redhat.com'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:51216:0:0:1',
'timestamp': 1516695443.0,
'topic': '/topic/VirtualTopic.eng.errata.activity.text_changes'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.activity.text_changes |
|
bkundal changed security_impact, synopsis, cve, topic, description, and reference on JBEAP advisory 30821 |
|
|
|
bkundal |
|
{‘bkundal’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.bugs.changed¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone changes bugs on an advisory.
You can view the history of messages with the eng.errata.bugs.changed topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.bugs.changed',
'errata_id': '26924',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478932:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.bugs.changed',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'errata.bugs.changed',
'when': '2017-05-31 22:20:21 UTC',
'who': 'rharwood@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478932:0:0:1',
'timestamp': 1496269224.0,
'topic': '/topic/VirtualTopic.eng.errata.bugs.changed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.bugs.changed |
|
rharwood changed bugs on an advisory |
|
|
|
rharwood |
|
{‘rharwood’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.builds.added¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone adds a build to an advisory.
You can view the history of messages with the eng.errata.builds.added topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'libpciaccess-0.13.4-3.1.el7_4',
'destination': '/topic/VirtualTopic.eng.errata.builds.added',
'errata_id': '31169',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-2:216012:0:0:1',
'persistent': 'true',
'priority': '4',
'product': 'RHEL',
'subject': 'errata.builds.added',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'errata.builds.added',
'when': '2017-10-26 14:34:37 UTC',
'who': 'ajackson@redhat.com'},
'i': 0,
'msg': { 'brew_build': 'libpciaccess-0.13.4-3.1.el7_4',
'errata_id': 31169,
'product': 'RHEL',
'when': '2017-10-26 14:34:37 UTC',
'who': 'ajackson@redhat.com'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-2:216012:0:0:1',
'timestamp': 1509028483.0,
'topic': '/topic/VirtualTopic.eng.errata.builds.added'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.builds.added |
|
ajackson added libpciaccess-0.13.4-3.1.el7_4 to RHEL advisory 31169 |
|
|
|
ajackson |
|
{‘ajackson’} |
|
{‘libpciaccess’} |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.builds.changed¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone changes the builds on an advisory.
You can view the history of messages with the eng.errata.builds.changed topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'destination': '/topic/VirtualTopic.eng.errata.builds.changed',
'errata_id': '26924',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478922:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.builds.changed',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'errata.builds.changed',
'when': '2017-05-31 22:19:49 UTC',
'who': 'rharwood@redhat.com'},
'i': 0,
'msg': '',
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-32888-1493960489068-4:478922:0:0:1',
'timestamp': 1496269189.0,
'topic': '/topic/VirtualTopic.eng.errata.builds.changed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.builds.changed |
|
rharwood changed builds on an advisory |
|
|
|
rharwood |
|
{‘rharwood’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.builds.removed¶
The Errata Tool supports the release workflow for Red Hat content.
You’ll see a message like this one when someone removes a build from an advisory.
You can view the history of messages with the eng.errata.builds.removed topic or all errata messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'ovirt-engine-dwh-4.2.1-0.0.master.20171025112108.el7ev',
'destination': '/topic/VirtualTopic.eng.errata.builds.removed',
'errata_id': '29571',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-2:215849:0:0:1',
'persistent': 'true',
'priority': '4',
'product': 'RHV',
'subject': 'errata.builds.removed',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'errata.builds.removed',
'when': '2017-10-26 14:31:03 UTC',
'who': 'sradco@redhat.com'},
'i': 0,
'msg': { 'brew_build': 'ovirt-engine-dwh-4.2.1-0.0.master.20171025112108.el7ev',
'errata_id': 29571,
'product': 'RHV',
'when': '2017-10-26 14:31:03 UTC',
'who': 'sradco@redhat.com'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-2:215849:0:0:1',
'timestamp': 1509028264.0,
'topic': '/topic/VirtualTopic.eng.errata.builds.removed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.builds.removed |
|
sradco removed ovirt-engine-dwh-4.2.1-0.0.master.20171025112108.el7ev from RHV advisory 29571 |
|
|
|
sradco |
|
{‘sradco’} |
|
{‘ovirt-engine-dwh’} |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.ccat¶
The Errata Tool supports the release workflow for Red Hat content.
Container Content Availability Testing (CCAT) results are published to the UMB whenever a test completes.
You can view the history of messages with the eng.errata.ccat topic or all errata messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'BUILD_ID': '6277',
'ERRATA_ID': '34908',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'MESSAGE_TYPE': 'pass',
'TARGET': 'cdn-stage',
'TRIGGER_TYPE': 'automated',
'content-length': '199',
'destination': '/topic/VirtualTopic.eng.errata.ccat',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-34769-1532431903164-21:11079:0:0:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'BUILD_URL': 'https://content-test-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/stage_cdn_content_validation/6277/',
'MESSAGE': 'This is a content testing message sent at 2018-07-24 '
'14:23:31.328161'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-34769-1532431903164-21:11079:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.0',
'timestamp': 1532442252.0,
'topic': '/topic/VirtualTopic.eng.errata.ccat',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.ccat |
|
CAT results for erratum 34908 on cdn-stage (automated): pass |
|
https://content-test-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/stage_cdn_content_validation/6277/ |
|
None |
|
set() |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.errata.ccat.reschedule_test¶
The Errata Tool supports the release workflow for Red Hat content.
Messages like these appear whenever someone reschedules a CCAT test.
You can view the history of messages with the eng.errata.ccat.reschedule_test topic or all errata messages in datagrepper.
{ 'headers': { 'ERRATA_ID': '29873',
'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'TARGET': 'cdn-live',
'destination': '/topic/VirtualTopic.eng.errata.ccat.reschedule_test',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-35748-1505981049344-2:327116:0:0:1',
'persistent': 'true',
'priority': '4',
'subject': 'errata.ccat.reschedule_test',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'type': 'errata.ccat.reschedule_test'},
'msg': {'ERRATA_ID': '29873', 'TARGET': 'cdn-live'},
'topic': '/topic/VirtualTopic.eng.errata.ccat.reschedule_test'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
errata.ccat.reschedule_test |
|
CCAT for erratum 29873 in cdn-live was rescheduled |
|
|
|
None |
|
set() |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker¶
eng.freshmaker.build.state.changed¶
You can view the history of messages with the eng.freshmaker.build.state.changed topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': { 'build_args': { 'branch': 'rhscl-2.4-rh-nodejs6-rhel-7',
'commit': '7173d2ef184d571a5dda71794217f3ceae27d270',
'odcs_pulp_compose_id': 18,
'parent': 's2i-base-docker-1-6.1511360843',
'repository': 'rpms/rh-nodejs6-docker',
'target': 'rhscl-2.4-rh-nodejs6-rhel-7-docker-candidate'},
'build_id': 13,
'dep_on': 's2i-base-docker',
'event_id': 58,
'id': 32,
'name': 'rh-nodejs6-docker',
'original_nvr': 'rh-nodejs6-docker-6-14.11',
'rebuilt_nvr': 'rh-nodejs6-docker-6-14.1511360844',
'state': 1,
'state_name': 'DONE',
'state_reason': 'Built successfully.',
'time_completed': '2017-11-29T07:07:49Z',
'time_submitted': '2017-11-22T14:27:24Z',
'type': 1,
'type_name': 'IMAGE',
'url': 'http://freshmaker.localhost/api/1/builds/32'},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.build.state.changed',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.build.state.changed |
|
IMAGE rh-nodejs6-docker is successfully rebuilt from original build rh-nodejs6-docker-6-14.11 to new build rh-nodejs6-docker-6-14.1511360844. |
|
|
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.build.state.changed¶
You can view the history of messages with the eng.freshmaker.build.state.changed topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': { 'build_args': { 'branch': 'rhmap-4.5-rhel-7',
'commit': '3135dd5c0d1199ff6688f4d50c702a789fea5b09',
'odcs_pulp_compose_id': 84,
'parent': 'httpd24-docker-2.4-36.1511363210',
'repository': 'rpms/rhmap-httpd-docker',
'target': 'rhmap-4.5-rhel-7-docker-candidate'},
'build_id': 62,
'dep_on': 'httpd24-docker',
'event_id': 60,
'id': 96,
'name': 'rhmap-httpd-docker',
'original_nvr': 'rhmap-httpd-docker-2.4-40',
'rebuilt_nvr': 'rhmap-httpd-docker-2.4-40.1511363210',
'state': 2,
'state_name': 'FAILED',
'state_reason': 'Cannot build artifact, because its dependency '
'cannot be built.',
'time_completed': '2017-11-29T11:05:49Z',
'time_submitted': '2017-11-22T15:06:50Z',
'type': 1,
'type_name': 'IMAGE',
'url': 'http://freshmaker.localhost/api/1/builds/96'},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.build.state.changed',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.build.state.changed |
|
IMAGE build state is switched to FAILED: “Cannot build artifact, because its dependency cannot be built.” |
|
|
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.event.state.changed¶
You can view the history of messages with the eng.freshmaker.event.state.changed topic or all freshmaker messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '1938',
'destination': '/topic/VirtualTopic.eng.freshmaker.event.state.changed',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.localhost-45704-1510236486219-2:121170:0:0:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-stage.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'builds': [ { 'build_args': { 'branch': 'somebranch',
'commit': '61c79adcc6db5f62cf62d358329042831b153f63',
'odcs_pulp_compose_id': 18,
'parent': 'someimage3-docker-7.0.6-3',
'repository': 'rpms/someimage4-docker',
'target': 'somebranch-docker-candidate'},
'build_id': None,
'dep_on': None,
'event_id': 242,
'id': 122,
'name': 'someimage',
'original_nvr': 'someimage-1.4-36',
'rebuilt_nvr': 'someimage-1.4-36.1512495241',
'state': 4,
'state_name': 'PLANNED',
'state_reason': None,
'time_completed': None,
'time_submitted': '2017-12-05T17:34:01Z',
'type': 1,
'type_name': 'IMAGE',
'url': 'http://freshmaker.localhost/api/1/builds/122'},
{ 'build_args': { 'branch': 'somebranch2',
'commit': '07d6e35c241500a68fdaa02f208c6c098cc00835',
'odcs_pulp_compose_id': 19,
'parent': 'someimage-1.4-36.1512495241',
'repository': 'rpms/someimage2',
'target': 'somebranch2-docker-candidate'},
'build_id': None,
'dep_on': 'someimage',
'event_id': 242,
'id': 123,
'name': 'someimage2',
'original_nvr': 'someimage2-v3.7.9-21',
'rebuilt_nvr': 'someimage2-v3.7.9-21.1512495241',
'state': 4,
'state_name': 'PLANNED',
'state_reason': None,
'time_completed': None,
'time_submitted': '2017-12-05T17:34:01Z',
'type': 1,
'type_name': 'IMAGE',
'url': 'http://freshmaker.localhost/api/1/builds/123'}],
'event_type_id': 8,
'id': 242,
'message_id': 'ID:messaging-devops-broker02.localhost-33824-1512422606448-2:64621:0:0:1.RHSA-2017:31059',
'search_key': '31059',
'state': 2,
'state_name': 'COMPLETE',
'state_reason': 'All docker images have been rebuilt.',
'url': 'http://freshmaker.localhost/api/1/events/242'},
'msg_id': 'ID:messaging-devops-broker01.localhost-45704-1510236486219-2:121170:0:0:1',
'timestamp': 1512495243.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.event.state.changed',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.event.state.changed |
|
Event state is switched to COMPLETE: “All docker images have been rebuilt.” |
|
|
|
Unspecified |
|
Unspecified |
|
{‘someimage2’, ‘someimage’} |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.event.state.changed¶
You can view the history of messages with the eng.freshmaker.event.state.changed topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': { 'builds': ['pkg-0.1-1', 'another-pkg-1.0-7'],
'event_type_id': 11,
'id': 81,
'message_id': 'ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1',
'search_key': 'ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1',
'state': 2,
'state_name': 'COMPLETE',
'state_reason': 'Generated ErrataAdvisoryRPMsSignedEvent '
'(ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1) '
'for errata: RHSA-2017:29110',
'url': 'http://freshmaker.localhost/api/1/events/81'},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.event.state.changed',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.event.state.changed |
|
Event state is switched to COMPLETE: “Generated ErrataAdvisoryRPMsSignedEvent (ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1) for errata: RHSA-2017:29110” |
|
|
|
Unspecified |
|
Unspecified |
|
{‘another-pkg’, ‘pkg’} |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.event.state.changed.min¶
You can view the history of messages with the eng.freshmaker.event.state.changed.min topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': { 'event_type_id': 11,
'id': 81,
'message_id': 'ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1',
'search_key': 'ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1',
'state': 2,
'state_name': 'COMPLETE',
'state_reason': 'Generated ErrataAdvisoryRPMsSignedEvent '
'(ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1) '
'for errata: RHSA-2017:29110',
'url': 'http://freshmaker.localhost/api/1/events/81'},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.event.state.changed.min',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.event.state.changed.min |
|
Event state is switched to COMPLETE: “Generated ErrataAdvisoryRPMsSignedEvent (ID:messaging-devops-broker01.localhost-46295-1510954431290-2:473881:0:0:1) for errata: RHSA-2017:29110” |
|
|
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.manual.rebuild¶
You can view the history of messages with the eng.freshmaker.manual.rebuild topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': {'errata_id': 31360},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.manual.rebuild',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.manual.rebuild |
|
Manual rebuild is triggered for Errata advisory 31360. |
|
|
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.freshmaker.some.new.event¶
You can view the history of messages with the eng.freshmaker.some.new.event topic or all freshmaker messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'i': 0,
'msg': { 'builds': [],
'event_type_id': 8,
'id': 83,
'message_id': 'ID:messaging-devops-broker01.localhost-46295-1510954431290-2:474199:0:0:1.RHSA-2017:31570',
'search_key': '31570',
'state': 4,
'state_name': 'SKIPPED',
'state_reason': 'No container images to rebuild for advisory '
"u'RHSA-2017:31570'",
'url': 'http://freshmaker.localhost/api/1/events/83'},
'msg_id': 'ID:localhost-45704-1510236486219-2:66659:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1511940834.0,
'topic': '/topic/VirtualTopic.eng.freshmaker.some.new.event',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
freshmaker.some.new.event |
|
Unknown message. |
|
None |
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.greenwave¶
eng.greenwave.decision.update¶
Greenwave is a service to decide whether a software artifact can pass certain gating points in a software delivery pipeline, based on test results stored in ResultsDB and waivers stored in WaiverDB.
Greenwave publishes a message when a new result/waiver causes the decision to change.
This decision is for Erratum moving to New Files state.
You can view the history of messages with the eng.greenwave.decision.update topic or all greenwave messages in datagrepper.
{ 'crypto': None,
'headers': { 'content-type': 'text/plain',
'destination': '/topic/VirtualTopic.eng.greenwave.decision.update',
'expires': '1527253961866',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-36970-1526482715012-2:55604:-1:1:1267',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1526649161866'},
'i': 0,
'msg': { 'applicable_policies': ['1'],
'decision_context': 'errata_newfile_to_qe',
'policies_satisfied': True,
'previous': { 'applicable_policies': ['1'],
'policies_satisfied': False,
'summary': '1 of 30 required test results missing',
'unsatisfied_requirements': [ { 'item': { 'item': 'libXdmcp-1.1.2-9.el8',
'type': 'koji_build'},
'scenario': None,
'testcase': 'dist.rpmdiff.analysis.xml_validity',
'type': 'test-result-missing'}]},
'product_version': 'rhel-7',
'subject': [{'item': 'libXdmcp-1.1.2-9.el8', 'type': 'koji_build'}],
'summary': 'all required tests passed',
'unsatisfied_requirements': []},
'msg_id': '2018-c50ff499-7573-4d7b-97de-45536096dfba',
'signature': None,
'source_version': '0.8.2',
'timestamp': 1526649161.0,
'topic': '/topic/VirtualTopic.eng.greenwave.decision.update',
'username': 'upshift'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
greenwave.decision.update |
|
all required tests passed for libXdmcp-1.1.2-9.el8, “errata_newfile_to_qe” (rhel-7) |
|
https://pipeline.engineering.redhat.com/kojibuild/libXdmcp-1.1.2-9.el8 |
|
Unspecified |
|
Unspecified |
|
{‘libXdmcp’} |
|
Unspecified |
|
|
|
Unspecified |
eng.greenwave.decision.update¶
Greenwave is a service to decide whether a software artifact can pass certain gating points in a software delivery pipeline, based on test results stored in ResultsDB and waivers stored in WaiverDB.
Greenwave publishes a message when a new result/waiver causes the decision to change.
This decision is for compose gating.
You can view the history of messages with the eng.greenwave.decision.update topic or all greenwave messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'text/plain',
'destination': '/topic/VirtualTopic.eng.greenwave.decision.update',
'expires': '1529008267689',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-42045-1527890187852-2:112143:-1:1:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1528403467689'},
'i': 39446,
'msg': { 'applicable_policies': ['osci_compose'],
'decision_context': 'osci_compose_gate',
'policies_satisfied': False,
'previous': { 'applicable_policies': ['osci_compose'],
'policies_satisfied': False,
'summary': '1 of 1 required tests failed',
'unsatisfied_requirements': [ { 'item': { 'item': 'libsemanage-2.8-2.el8+7',
'type': 'brew-build'},
'result_id': 5016237,
'scenario': None,
'testcase': 'osci.brew-build.tier0.functional',
'type': 'test-result-failed'}]},
'product_version': 'rhel-8',
'subject': [ { 'item': 'libsemanage-2.8-2.el8+7',
'type': 'brew-build'}],
'summary': '1 of 1 required tests failed',
'unsatisfied_requirements': [ { 'item': { 'item': 'libsemanage-2.8-2.el8+7',
'type': 'brew-build'},
'result_id': 5036102,
'scenario': None,
'testcase': 'osci.brew-build.tier0.functional',
'type': 'test-result-failed'}]},
'msg_id': '2018-3337fe81-2e0b-4048-a963-068b34405205',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.0',
'timestamp': 1528403467.0,
'topic': '/topic/VirtualTopic.eng.greenwave.decision.update',
'username': 'upshift'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
greenwave.decision.update |
|
1 of 1 required tests failed for libsemanage-2.8-2.el8+7, “osci_compose_gate” (rhel-8) |
|
https://pipeline.engineering.redhat.com/kojibuild/libsemanage-2.8-2.el8+7 |
|
Unspecified |
|
Unspecified |
|
{‘libsemanage’} |
|
Unspecified |
|
|
|
Unspecified |
eng.jira¶
eng.jira.comment.added¶
JIRA is issue tracking system
Messages (like the example given here) are published when issue is updated by posting a new comment.
You can view the history of messages with the eng.jira.comment.added topic or all jira messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.jira.comment.added',
'event_type': 'jira:issue_updated',
'expires': '1535382740838',
'issue_key': 'FACTORY-2904',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'priority': '4',
'project': 'FACTORY',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1534777940838'},
'i': 0,
'msg': { 'changelog': { 'items': [ { 'field': 'Product Affects Version',
'fieldtype': 'custom',
'to': '[11704, 11626]',
'toString': 'rhel-8.0,fedora-x'}]},
'comment': { 'author': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'body': 'Added new comment',
'created': '2018-08-20T18:55:36.524+0000',
'id': '973188',
'updateAuthor': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'updated': '2018-08-20T18:55:36.524+0000'},
'issue': { 'fields': { 'assignee': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'created': '2018-08-14T21:12:16.681+0000',
'creator': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'description': 'Some longer description',
'issuetype': { 'description': 'A problem '
'which impairs '
'functions.',
'name': 'Bug'},
'project': { 'key': 'FACTORY',
'name': 'Factory 2.0',
'projectCategory': { 'description': 'Tooling '
'projects',
'name': 'PnT '
'DevOps '
'Dev'}},
'reporter': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'resolution': {},
'status': { 'description': 'This issue is '
'being worked on.',
'name': 'In Progress',
'statusCategory': { 'colorName': 'yellow',
'key': 'indeterminate',
'name': 'In '
'Progress'}},
'summary': 'Determine MBS hang issue',
'updated': '2018-08-20T15:12:20.474+0000',
'votes': {},
'watches': {'watchCount': 5}},
'key': 'FACTORY-2904'},
'user': { 'displayName': 'red-user',
'emailAddress': 'rbean+red-user@redhat.com',
'name': 'red-user',
'self': 'https://projects.engineering.redhat.com/rest/api/2/user?username=red-user',
'timeZone': 'Europe/London'},
'webhookEvent': 'jira:issue_updated'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1534777940.0,
'topic': '/topic/VirtualTopic.eng.jira.comment.added',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
jira.comment.added |
|
Comment has been added by Bill Rainford in bug FACTORY-2904. |
|
https://projects.engineering.redhat.com/browse/FACTORY-2904?focusedCommentId=973188 |
|
red-user |
|
{‘rbean’, ‘brainfor’, ‘red-user’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.jira.comment.updated¶
JIRA is issue tracking system
Messages (like the example given here) are published when issue is updated by posting a new comment.
You can view the history of messages with the eng.jira.comment.updated topic or all jira messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.jira.comment.updated',
'event_type': 'jira:issue_updated',
'expires': '1535382740838',
'issue_key': 'FACTORY-2904',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'priority': '4',
'project': 'FACTORY',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1534777940838'},
'i': 0,
'msg': { 'changelog': { 'items': [ { 'field': 'Product Affects Version',
'fieldtype': 'custom',
'to': '[11704, 11626]',
'toString': 'rhel-8.0,fedora-x'}]},
'comment': { 'author': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'body': 'Edited comment',
'created': '2018-08-20T18:55:36.524+0000',
'id': '973188',
'updateAuthor': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'updated': '2018-08-21T18:55:36.524+0000'},
'issue': { 'fields': { 'assignee': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'created': '2018-08-14T21:12:16.681+0000',
'creator': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'description': 'Some longer description',
'issuetype': { 'description': 'A problem '
'which impairs '
'functions.',
'name': 'Bug'},
'project': { 'key': 'FACTORY',
'name': 'Factory 2.0',
'projectCategory': { 'description': 'Tooling '
'projects',
'name': 'PnT '
'DevOps '
'Dev'}},
'reporter': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'resolution': {},
'status': { 'description': 'This issue is '
'being worked on.',
'name': 'In Progress',
'statusCategory': { 'colorName': 'yellow',
'key': 'indeterminate',
'name': 'In '
'Progress'}},
'summary': 'Determine MBS hang issue',
'updated': '2018-08-20T15:12:20.474+0000',
'votes': {},
'watches': {'watchCount': 5}},
'key': 'FACTORY-2904'},
'user': { 'displayName': 'red-user',
'emailAddress': 'rbean+red-user@redhat.com',
'name': 'red-user',
'self': 'https://projects.engineering.redhat.com/rest/api/2/user?username=red-user',
'timeZone': 'Europe/London'},
'webhookEvent': 'jira:issue_updated'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1534777940.0,
'topic': '/topic/VirtualTopic.eng.jira.comment.updated',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
jira.comment.updated |
|
Comment has been edited by Bill Rainford in bug FACTORY-2904. |
|
https://projects.engineering.redhat.com/browse/FACTORY-2904?focusedCommentId=973188 |
|
red-user |
|
{‘rbean’, ‘brainfor’, ‘red-user’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.jira.issue.created¶
JIRA is issue tracking system
Messages (like the example given here) are published when new issue is created
You can view the history of messages with the eng.jira.issue.created topic or all jira messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.jira.issue.created',
'event_type': 'jira:issue_created',
'expires': '1535388010247',
'issue_key': 'DEVOPSA-4091',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:144',
'priority': '4',
'project': 'DEVOPSA',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1534783210247'},
'i': 0,
'msg': { 'changelog': {},
'comment': {'author': {}, 'updateAuthor': {}},
'issue': { 'fields': { 'assignee': { 'active': True,
'displayName': 'Kyle Boran',
'emailAddress': 'kboran@redhat.com',
'key': 'kboran',
'name': 'kboran',
'timeZone': 'America/New_York'},
'created': '2018-08-20T16:40:09.644+0000',
'description': 'Proper long description',
'issuetype': { 'description': 'A task that '
'needs to be '
'done.',
'name': 'Task'},
'project': { 'key': 'DEVOPSA',
'name': 'PnT DevOps Automation',
'projectCategory': { 'description': 'Tools '
'developed '
'by '
'PnT',
'name': 'PnT '
'Developer '
'Operations '
'Tools'}},
'reporter': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'resolution': {},
'status': { 'description': 'This status is '
'managed '
'internally',
'name': 'To Do',
'statusCategory': { 'colorName': 'blue-gray',
'key': 'new',
'name': 'To '
'Do'}},
'summary': 'Add some basic summary to new '
'issues',
'updated': '2018-08-20T16:40:09.644+0000',
'votes': {},
'watches': {}},
'key': 'DEVOPSA-4091'},
'user': { 'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'name': 'rbean',
'self': 'https://projects.engineering.redhat.com/rest/api/2/user?username=rbean',
'timeZone': 'America/Havana'},
'webhookEvent': 'jira:issue_created'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:144',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1534783210.0,
'topic': '/topic/VirtualTopic.eng.jira.issue.created',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
jira.issue.created |
|
Task DEVOPSA-4091 has been created by Ralph Bean. |
|
|
|
rbean |
|
{‘rbean’, ‘kboran’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.jira.issue.updated¶
JIRA is issue tracking system
Messages (like the example given here) are published when issue is updated by posting a new comment.
You can view the history of messages with the eng.jira.issue.updated topic or all jira messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.jira.issue.updated',
'event_type': 'jira:issue_updated',
'expires': '1535382740838',
'issue_key': 'FACTORY-2904',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'priority': '4',
'project': 'FACTORY',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1534777940838'},
'i': 0,
'msg': { 'changelog': { 'items': [ { 'field': 'Product Affects Version',
'fieldtype': 'custom',
'to': '[11704, 11626]',
'toString': 'rhel-8.0,fedora-x'}]},
'comment': { 'author': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'body': 'Edited comment',
'created': '2018-08-20T18:55:36.524+0000',
'id': '973188',
'updateAuthor': { 'displayName': 'Bill Rainford',
'emailAddress': 'brainfor@redhat.com',
'key': 'brainfor',
'name': 'brainfor',
'timeZone': 'America/Havana'},
'updated': '2018-08-21T18:55:36.524+0000'},
'issue': { 'fields': { 'assignee': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'created': '2018-08-14T21:12:16.681+0000',
'creator': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'description': 'Some longer description',
'issuetype': { 'description': 'A problem '
'which impairs '
'functions.',
'name': 'Bug'},
'project': { 'key': 'FACTORY',
'name': 'Factory 2.0',
'projectCategory': { 'description': 'Tooling '
'projects',
'name': 'PnT '
'DevOps '
'Dev'}},
'reporter': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'resolution': {},
'status': { 'description': 'This issue is '
'being worked on.',
'name': 'In Progress',
'statusCategory': { 'colorName': 'yellow',
'key': 'indeterminate',
'name': 'In '
'Progress'}},
'summary': 'Determine MBS hang issue',
'updated': '2018-08-20T15:12:20.474+0000',
'votes': {},
'watches': {'watchCount': 5}}},
'user': { 'displayName': 'red-user',
'emailAddress': 'rbean+red-user@redhat.com',
'name': 'red-user',
'self': 'https://projects.engineering.redhat.com/rest/api/2/user?username=red-user',
'timeZone': 'Europe/London'},
'webhookEvent': 'jira:issue_updated'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1534777940.0,
'topic': '/topic/VirtualTopic.eng.jira.issue.updated',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
jira.issue.updated |
|
None |
|
None |
|
red-user |
|
{‘rbean’, ‘brainfor’, ‘red-user’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.jira.issue.updated¶
JIRA is issue tracking system
Messages (like the example given here) are published when issue is updated. There are some more specific updates for comments being added/removed as well
You can view the history of messages with the eng.jira.issue.updated topic or all jira messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.jira.issue.updated',
'event_type': 'jira:issue_updated',
'expires': '1535382740838',
'issue_key': 'FACTORY-2904',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'priority': '4',
'project': 'FACTORY',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1534777940838'},
'i': 0,
'msg': { 'changelog': { 'items': [ { 'field': 'Product Affects Version',
'fieldtype': 'custom',
'to': '[11704, 11626]',
'toString': 'rhel-8.0,fedora-x'}]},
'comment': {'author': {}, 'updateAuthor': {}},
'issue': { 'fields': { 'created': '2018-08-14T21:12:16.681+0000',
'creator': { 'active': True,
'displayName': 'Ralph Bean',
'emailAddress': 'rbean@redhat.com',
'key': 'rbean',
'name': 'rbean',
'timeZone': 'America/Havana'},
'description': 'Some longer description',
'issuetype': { 'description': 'A problem '
'which impairs '
'functions.',
'name': 'Bug'},
'project': { 'key': 'FACTORY',
'name': 'Factory 2.0',
'projectCategory': { 'description': 'Tooling '
'projects',
'name': 'PnT '
'DevOps '
'Dev'}},
'resolution': {},
'status': { 'description': 'This issue is '
'being worked on.',
'name': 'In Progress',
'statusCategory': { 'colorName': 'yellow',
'key': 'indeterminate',
'name': 'In '
'Progress'}},
'summary': 'Determine MBS hang issue',
'updated': '2018-08-20T15:12:20.474+0000',
'votes': {},
'watches': {'watchCount': 5}},
'key': 'FACTORY-2904'},
'user': { 'displayName': 'red-user',
'emailAddress': 'rbean+red-user@redhat.com',
'name': 'red-user',
'self': 'https://projects.engineering.redhat.com/rest/api/2/user?username=red-user',
'timeZone': 'Europe/London'},
'webhookEvent': 'jira:issue_updated'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-37550-1534679656045-2:40012:-1:1:132',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1534777940.0,
'topic': '/topic/VirtualTopic.eng.jira.issue.updated',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
jira.issue.updated |
|
Bug FACTORY-2904 has been updated by red-user. |
|
|
|
red-user |
|
{‘rbean’, ‘red-user’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.mbs¶
eng.mbs.module.state.change¶
The Module Build Service (MBS) builds modules.
During the course of a “module build”, the build will transition through a number of states. Every time it changes, the MBS will publish a message much like this one:
You can view the history of messages with the eng.mbs.module.state.change topic or all mbs messages in datagrepper.
{ 'crypto': None,
'headers': { 'content-length': '3904',
'content-type': 'text/json',
'destination': '/topic/VirtualTopic.eng.mbs.module.state.change',
'expires': '1509653413799',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-3:5230:-1:1:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1509048613799'},
'i': 0,
'msg': { 'component_builds': [2182, 2179, 2177, 2180, 2178, 2181],
'id': 40,
'koji_tag': 'module-a8c57dc51895c3b4',
'modulemd': 'data:\n components:\n rpms:\n ...',
'name': 'foobar',
'owner': 'tdawson',
'scmurl': 'git://pkgs.devel.redhat.com/modules/foobar?#e160b976daf28d17770c3cd1b33f388155688944',
'state': 3,
'state_name': 'done',
'state_reason': None,
'state_trace': [ { 'reason': None,
'state': 1,
'state_name': 'wait',
'time': '2017-10-26T17:13:22Z'},
{ 'reason': None,
'state': 1,
'state_name': 'wait',
'time': '2017-10-26T17:13:40Z'},
{ 'reason': None,
'state': 2,
'state_name': 'build',
'time': '2017-10-26T17:13:44Z'},
{ 'reason': None,
'state': 2,
'state_name': 'build',
'time': '2017-10-26T17:13:46Z'},
{ 'reason': None,
'state': 2,
'state_name': 'build',
'time': '2017-10-26T17:21:53Z'},
{ 'reason': None,
'state': 2,
'state_name': 'build',
'time': '2017-10-26T17:23:55Z'}],
'state_url': 'http://localhost/module-build-service/1/module-builds/40',
'stream': 'linux-9000',
'tasks': { 'rpms': { 'cachefilesd': { 'nvr': 'cachefilesd-0.10.10-3.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380514},
'e2fsprogs': { 'nvr': 'e2fsprogs-1.43.6-1.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380519},
'kernel': { 'nvr': 'kernel-4.14.0-0.rc3.git0.1.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380510},
'keyutils': { 'nvr': 'keyutils-1.5.10-3.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380509},
'module-build-macros': { 'nvr': 'module-build-macros-0.1-1.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380271},
'quota': { 'nvr': 'quota-4.03-9.el8+a8c57dc5',
'state': 1,
'state_reason': '',
'task_id': 14380517}}},
'time_completed': '2017-10-26T20:10:13Z',
'time_modified': '2017-10-26T20:10:13Z',
'time_submitted': '2017-10-26T17:13:18Z',
'version': '20171026171229'},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-43669-1508744086399-3:5230:-1:1:1',
'timestamp': 1509048641.0,
'topic': '/topic/VirtualTopic.eng.mbs.module.state.change',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
mbs.module.state.change |
|
tdawson’s build of foobar-linux-9000 transitioned to the “done” state. |
|
|
|
tdawson |
|
{‘tdawson’} |
|
{‘foobar’} |
|
Unspecified |
|
|
|
Unspecified |
eng.metaxor¶
eng.metaxor.events.lightblue.containerImage.insert¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when information about new image gets stored in Lightblue
You can view the history of messages with the eng.metaxor.events.lightblue.containerImage.insert topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'aos3-installation-docker-v3.3.1.46.37-1',
'changes': '[]',
'content-length': '187',
'destination': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerImage.insert',
'expires': '0',
'force_refresh': 'false',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:230301:0:0:1',
'overridden': 'false',
'priority': '4',
'published': 'false',
'schema_version': '1.0.4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'brew_build': 'aos3-installation-docker-v3.3.1.46.37-1',
'changes': [],
'force_refresh': False,
'full_refresh': False,
'overridden': False,
'published': False,
'schema_version': '1.0.4'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:230301:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1516924184.0,
'topic': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerImage.insert',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.events.lightblue.containerImage.insert |
|
New containerImage entity for unpublished container image aos3-installation-docker-v3.3.1.46.37-1 has been created. |
|
|
|
Unspecified |
|
Unspecified |
|
{‘aos3-installation-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.metaxor.events.lightblue.containerImage.update¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when the existing image in lightblue gets updated
You can view the history of messages with the eng.metaxor.events.lightblue.containerImage.update topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'etcd-docker-3.2.11-2',
'changes': '[brew, lastUpdateDate, repositories]',
'content-length': '206',
'destination': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerImage.update',
'expires': '0',
'force_refresh': 'true',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'overridden': 'false',
'priority': '4',
'published': 'true',
'schema_version': '1.0.4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'brew_build': 'etcd-docker-3.2.11-2',
'changes': ['brew', 'lastUpdateDate', 'repositories'],
'force_refresh': True,
'full_refresh': False,
'overridden': False,
'published': True,
'schema_version': '1.0.4'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517059491.0,
'topic': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerImage.update',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.events.lightblue.containerImage.update |
|
Existing containerImage entity for published container image etcd-docker-3.2.11-2 has been updated. |
|
https://brewweb.engineering.redhat.com/brew/search?terms=etcd-docker-3.2.11-2&type=build&match=exact |
|
Unspecified |
|
Unspecified |
|
{‘etcd-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.metaxor.events.lightblue.containerRepository.insert¶
The MetaXOR service provides repositories to lightblue database
Messages (like the example given here) are published when the new repository is created in Lightblue
You can view the history of messages with the eng.metaxor.events.lightblue.containerRepository.insert topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'etcd-docker-3.2.11-2',
'changes': '[lastUpdateDate]',
'content-length': '206',
'destination': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerRepository.insert',
'expires': '0',
'force_refresh': 'true',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'overridden': 'false',
'priority': '4',
'published': 'true',
'schema_version': '1.0.0',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'changes': ['lastUpdateDate'],
'force_refresh': False,
'full_refresh': False,
'published': True,
'registry': 'registry.access.redhat.com',
'repository': 'rhel7/rhel',
'schema_version': '1.0.0'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517059491.0,
'topic': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerRepository.insert',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.events.lightblue.containerRepository.insert |
|
New published container repository rhel7/rhel has been created. |
|
https://access.redhat.com/containers/#/registry.access.redhat.com/rhel7/rhel |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
{‘rhel7/rhel’} |
|
|
|
Unspecified |
eng.metaxor.events.lightblue.containerRepository.update¶
The MetaXOR service provides repositories to lightblue database
Messages (like the example given here) are published when the existing repository is updated in Lightblue
You can view the history of messages with the eng.metaxor.events.lightblue.containerRepository.update topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'brew_build': 'etcd-docker-3.2.11-2',
'changes': '[lastUpdateDate]',
'content-length': '206',
'destination': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerRepository.update',
'expires': '0',
'force_refresh': 'true',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'overridden': 'false',
'priority': '4',
'published': 'true',
'schema_version': '1.0.0',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'changes': ['lastUpdateDate'],
'force_refresh': False,
'full_refresh': False,
'published': True,
'registry': 'registry.access.redhat.com',
'repository': 'rhel7/rhel',
'schema_version': '1.0.0'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:283330:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517059491.0,
'topic': '/topic/VirtualTopic.eng.metaxor.events.lightblue.containerRepository.update',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.events.lightblue.containerRepository.update |
|
Existing published container repository rhel7/rhel has been updated. |
|
https://access.redhat.com/containers/#/registry.access.redhat.com/rhel7/rhel |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
{‘rhel7/rhel’} |
|
|
|
Unspecified |
eng.metaxor.events.refresh¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when MetaXOR finishes refreshing metadata about whole repository
You can view the history of messages with the eng.metaxor.events.refresh topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '95',
'destination': '/topic/VirtualTopic.eng.metaxor.events.refresh',
'expires': '0',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'priority': '4',
'repository': 'openshift3/registry-console',
'repository_filter': 'null',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'full_refresh': False,
'repository': 'openshift3/registry-console',
'repository_filter': None},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517069378.0,
'topic': '/topic/VirtualTopic.eng.metaxor.events.refresh',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.events.refresh |
|
Container repository openshift3/registry-console has been refreshed in Lightblue. |
|
https://access.redhat.com/containers/#/registry.access.redhat.com/openshift3/registry-console |
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.metaxor.internal.refresh¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when we issue command to MetaXOR using strings
You can view the history of messages with the eng.metaxor.internal.refresh topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '95',
'destination': '/topic/VirtualTopic.eng.metaxor.internal.refresh',
'expires': '0',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'priority': '4',
'repository': 'openshift3/registry-console',
'repository_filter': 'null',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': 'Non dictionary message',
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517069378.0,
'topic': '/topic/VirtualTopic.eng.metaxor.internal.refresh',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.internal.refresh |
|
Non dictionary message |
|
None |
|
Unspecified |
|
Unspecified |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.metaxor.internal.refresh¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when we send non-string messages to metaxor. These likely can’t be simply displayed so let’s just put a placeholder for them’
You can view the history of messages with the eng.metaxor.internal.refresh topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '95',
'destination': '/topic/VirtualTopic.eng.metaxor.internal.refresh',
'expires': '0',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'priority': '4',
'repository': 'openshift3/registry-console',
'repository_filter': 'null',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': 123,
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-42569-1516420517578-2:285156:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1517069378.0,
'topic': '/topic/VirtualTopic.eng.metaxor.internal.refresh',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.internal.refresh |
|
Unknown message format |
|
None |
|
Unspecified |
|
Unspecified |
|
set() |
|
set() |
|
|
|
Unspecified |
eng.metaxor.internal.refresh.repository¶
The MetaXOR service provides images to lightblue database
Messages (like the example given here) are published when user/service requests repository update done by workers
You can view the history of messages with the eng.metaxor.internal.refresh.repository topic or all metaxor messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '130',
'destination': '/topic/VirtualTopic.eng.metaxor.internal.refresh.repository',
'expires': '0',
'force_refresh': 'false',
'full_refresh': 'false',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-38086-1536885036904-4:664804:0:0:1',
'name': 'jboss-datagrid-7/datagrid72-openshift',
'persistent': 'true',
'priority': '2',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0',
'user': 'metaxor'},
'i': 0,
'msg': { 'force_refresh': False,
'full_refresh': False,
'name': 'jboss-datagrid-7/datagrid72-openshift',
'priority': 2,
'user': 'metaxor'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-38086-1536885036904-4:664804:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1537794802.0,
'topic': '/topic/VirtualTopic.eng.metaxor.internal.refresh.repository',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
metaxor.internal.refresh.repository |
|
Repository update (2) requested by metaxor - jboss-datagrid-7/datagrid72-openshift |
|
Unspecified |
|
Unspecified |
|
{‘metaxor’} |
|
Unspecified |
|
{‘jboss-datagrid-7/datagrid72-openshift’} |
|
|
|
Unspecified |
eng.odcs¶
eng.odcs.state.change¶
You can view the history of messages with the eng.odcs.state.change topic or all odcs messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '629',
'destination': '/topic/VirtualTopic.eng.odcs.state.change',
'expires': '0',
'message-id': 'ID:broker.domain-45752-1512505691529-2:38975:0:0:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-stage.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'compose': { 'flags': [],
'id': 185,
'owner': 'UID=osbs,OU=users,DC=redhat,DC=com',
'result_repo': 'http://odcs.host.stage.eng.bos.redhat.com/composes/latest-odcs-185-1/compose/Temporary',
'result_repofile': 'http://odcs.host.stage.eng.bos.redhat.com/composes/latest-odcs-185-1/compose/Temporary/odcs-185.repo',
'results': ['repository'],
'sigkeys': '37017186 FD431D51 DB42A60E',
'source': 'osbs-test-odcs',
'source_type': 1,
'state': 2,
'state_name': 'done',
'time_done': '2017-12-11T08:38:41Z',
'time_removed': None,
'time_submitted': '2017-12-11T08:38:33Z',
'time_to_expire': '2017-12-12T08:38:33Z'},
'event': 'state-changed'},
'msg_id': 'ID:broker.domain-45752-1512505691529-2:38975:0:0:1',
'timestamp': 1512981522.0,
'topic': '/topic/VirtualTopic.eng.odcs.state.change'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
odcs.state.change |
|
osbs’s compose of osbs-test-odcs transitioned to done. |
|
http://odcs.host.stage.eng.bos.redhat.com/composes/latest-odcs-185-1/compose/Temporary/odcs-185.repo |
|
Unspecified |
|
{‘osbs’} |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pnc¶
eng.pnc.builds¶
Project Newcastle is a buildsystem for the middleware org.
Newcastle will publish messages to the message bus when builds change state. This is an example of just such a message.
You can view the history of messages with the eng.pnc.builds topic or all pnc messages in datagrepper.
{ 'headers': { 'attribute': 'state',
'configurationId': '400',
'configurationRevision': '2348',
'destination': '/topic/VirtualTopic.eng.pnc.builds',
'expires': '1535562990800',
'message-id': 'ID:orch-70-8z1lp-37781-1533892609865-3:1:250:1:1',
'name': 'nickboldt-experiments',
'newStatus': 'building',
'oldStatus': 'accepted',
'persistent': 'true',
'priority': '4',
'producer': 'PNC',
'timestamp': '1534958190800',
'type': 'BuildStateChange'},
'msg': { 'attribute': 'state',
'buildRecordId': '7156',
'newStatus': 'building',
'oldStatus': 'accepted'},
'msg_id': 'ID:orch-70-8z1lp-37781-1533892609865-3:1:250:1:1',
'timestamp': 1534958190.0,
'topic': '/topic/VirtualTopic.eng.pnc.builds'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pnc.builds |
|
The state of pnc nickboldt-experiments build #7156 changed from accepted to building |
|
http://orch.cloud.pnc.engineering.redhat.com/pnc-web/#/build-records/7156 |
|
Unspecified |
|
set() |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.pub¶
eng.pub.container.sign¶
“Pub” is the system used to push Red Hat releases for distribution.
This is an example of a message published when Pub signs a container image.
You can view the history of messages with the eng.pub.container.sign topic or all pub messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '751',
'destination': '/queue/Consumer.client-datanommer.openpaas-stage-2.VirtualTopic.eng.>',
'environment': 'devel',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34269-1498498125324-2:5227:0:0:3',
'method': 'PushAdvisory',
'mtype': 'container_signature',
'nochannel': 'false',
'original-destination': '/topic/VirtualTopic.eng.pub.container.sign',
'owner_id': 'pub/rcm-pub.app.eng.bos.redhat.com',
'priority': '4',
'push_id': '10908',
'pushed_item_count': '0',
'service': 'pub',
'source': 'advisory',
'state': 'OPEN',
'subscription': '/queue/Consumer.client-datanommer.openpaas-stage-2.VirtualTopic.eng.>',
'target': 'cdn-docker-stage-qa',
'task_id': '10908',
'timestamp': '0'},
'i': 0,
'msg': { 'claim_file': 'eyJjcml0aWNhbCI6IHsiaW1hZ2UiOiB7ImRvY2tlci1tYW5pZmVzdC1kaWdlc3QiOiAic2hhMjU2OjFiM2E5M2Q1ZjM2ODg3YWI3MTkwOTQzYTQ0Yzc1NzkyMzBiYWI4MDMzYmYzYjgzOTJkNzUxNDhiYjE0NWMyNTYifSwgInR5cGUiOiAiYXRvbWljIGNvbnRhaW5lciBzaWduYXR1cmUiLCAiaWRlbnRpdHkiOiB7ImRvY2tlci1yZWZlcmVuY2UiOiAicmVnaXN0cnkuYWNjZXNzLnFhLnJlZGhhdC5jb20vZTJlLWNvbnRhaW5lci1lMmUtY29udGFpbmVyLXRlc3QtcHJvZHVjdCJ9fSwgIm9wdGlvbmFsIjogeyJjcmVhdG9yIjogIlJlZCBIYXQsIEluYy4ifX0=',
'image_name': 'e2e-container/e2e-container-test-product',
'manifest_digest': 'sha256:1b3a93d5f36887ab7190943a44c7579230bab8033bf3b8392d75148bb145c256',
'pub_task_id': 10908,
'repo': 'redhat-e2e-container-e2e-container-test-product',
'request_id': '554f6752-83d3-41a4-a6a4-8eebdeb27599',
'sig_key_id': 'F21541EB'},
'msg_id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-34269-1498498125324-2:5227:0:0:3',
'timestamp': 1498714993.0,
'topic': '/topic/VirtualTopic.eng.pub.container.sign',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pub.container.sign |
|
image e2e-container/e2e-container-test-product was signed with key f21541eb in cdn-docker-stage-qa |
|
|
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pub.push_start¶
“Pub” is the system used to push Red Hat releases for distribution.
Pub will publish a message to the message bus when pushes start and stop. This is an example of a stop message announced when a push starts.
You can view the history of messages with the eng.pub.push_start topic or all pub messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '520',
'destination': '/topic/VirtualTopic.eng.pub.push_start',
'environment': 'production',
'expires': '0',
'message-id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c226859\\c0\\c0\\c1',
'method': 'PushStaged',
'mtype': 'push_start',
'nochannel': 'false',
'owner_id': 'pub/pub.app.eng.bos.redhat.com',
'priority': '4',
'push_id': '121932',
'pushed_item_count': '0',
'service': 'pub',
'source': 'staged',
'state': 'OPEN',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'target': 'cdn-qa',
'task_id': '121932',
'timestamp': '0'},
'i': 0,
'msg': { 'comment': 'Push missing SRPMs (RCMWORK-1400)',
'file_list': [ '/mnt/redhat/devel/lismith/staging-dir/rhel-x86_64-server-optional-7.1.eus'],
'hostname': 'pub.app.eng.bos.redhat.com',
'method': 'PushStaged',
'nochannel': False,
'owner': 'lismith',
'push_id': 121932,
'push_url': 'http://pub.devel.redhat.com/pub/push/121932/',
'pushed_by': 'lismith@redhat.com',
'pushed_item_count': 0,
'source': 'staged',
'state': 'OPEN',
'target': 'cdn-qa',
'task_id': 121932,
'task_url': 'http://pub.devel.redhat.com/pub/task/121932/'},
'msg_id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c226859\\c0\\c0\\c1',
'timestamp': 1495813073.0,
'topic': '/topic/VirtualTopic.eng.pub.push_start',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pub.push_start |
|
lismith’s staged push to cdn-qa of rhel-x86_64-server-optional-7.1.eus just started |
|
|
|
lismith |
|
{‘lismith’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.pub.push_stop¶
“Pub” is the system used to push Red Hat releases for distribution.
Pub will publish a message to the message bus when pushes start and stop. This is an example of a stop message announced when a push fails.
You can view the history of messages with the eng.pub.push_stop topic or all pub messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '613',
'destination': '/topic/VirtualTopic.eng.pub.push_stop',
'environment': 'production',
'expires': '0',
'message-id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c220960\\c0\\c0\\c1',
'method': 'PushAdvisory',
'mtype': 'push_stop',
'nochannel': 'false',
'owner_id': 'pub/pub.app.eng.bos.redhat.com',
'priority': '4',
'push_id': '121923',
'pushed_item_count': '55',
'service': 'pub',
'source': 'advisory',
'state': 'FAILED',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'target': 'live',
'task_id': '121923',
'timestamp': '0'},
'i': 0,
'msg': { 'comment': '',
'file_list': [ 'RHEA-2017:1321',
'RHBA-2017:1322',
'RHBA-2017:1323',
'RHBA-2017:1324',
'RHBA-2017:1325',
'RHEA-2017:1326',
'RHBA-2017:1327',
'RHEA-2017:1328',
'RHEA-2017:1329',
'RHBA-2017:1330',
'RHBA-2017:1331'],
'hostname': 'pub.app.eng.bos.redhat.com',
'method': 'PushAdvisory',
'nochannel': False,
'owner': 'errata',
'push_id': 121923,
'push_url': 'http://pub.devel.redhat.com/pub/push/121923/',
'pushed_by': 'rhartman@redhat.com',
'pushed_item_count': 55,
'source': 'advisory',
'state': 'FAILED',
'target': 'live',
'task_id': 121923,
'task_url': 'http://pub.devel.redhat.com/pub/task/121923/'},
'msg_id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c220960\\c0\\c0\\c1',
'timestamp': 1495807290.0,
'topic': '/topic/VirtualTopic.eng.pub.push_stop',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pub.push_stop |
|
rhartman’s advisory push to live of RHBA-2017:1322, RHBA-2017:1323, and 9 others failed |
|
|
|
rhartman |
|
{‘rhartman’, ‘errata’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.pub.push_stop¶
“Pub” is the system used to push Red Hat releases for distribution.
Pub will publish a message to the message bus when pushes start and stop. This is an example of a stop message announced when a push completes successfully.
You can view the history of messages with the eng.pub.push_stop topic or all pub messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'content-length': '422',
'destination': '/topic/VirtualTopic.eng.pub.push_stop',
'environment': 'production',
'expires': '0',
'message-id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c198478\\c0\\c0\\c1',
'method': 'PushAdvisory',
'mtype': 'push_stop',
'nochannel': 'false',
'owner_id': 'pub/pub.app.eng.bos.redhat.com',
'priority': '4',
'push_id': '121870',
'pushed_item_count': '1',
'service': 'pub',
'source': 'advisory',
'state': 'CLOSED',
'subscription': '/queue/Consumer.datanommer-dev-mikeb.VirtualTopic.eng.>',
'target': 'code-stage',
'task_id': '121870',
'timestamp': '0'},
'i': 0,
'msg': { 'comment': '',
'file_list': ['RHBA-2017:28733'],
'hostname': 'pub.app.eng.bos.redhat.com',
'method': 'PushAdvisory',
'nochannel': False,
'owner': 'errata',
'push_id': 121870,
'push_url': 'http://pub.devel.redhat.com/pub/push/121870/',
'pushed_by': None,
'pushed_item_count': 1,
'source': 'advisory',
'state': 'CLOSED',
'target': 'code-stage',
'task_id': 121870,
'task_url': 'http://pub.devel.redhat.com/pub/task/121870/'},
'msg_id': 'ID\\cmessaging-devops-broker02.web.prod.ext.phx2.redhat.com-35060-1495137834512-7\\c198478\\c0\\c0\\c1',
'timestamp': 1495759713.0,
'topic': '/topic/VirtualTopic.eng.pub.push_stop',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pub.push_stop |
|
errata’s advisory push to code-stage of RHBA-2017:28733 completed successfully |
|
|
|
errata |
|
{‘errata’} |
|
set() |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi¶
eng.pungi.createiso-imagedone¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when a createiso target completes.
You can view the history of messages with the eng.pungi.createiso-imagedone topic or all pungi messages in datagrepper.
{ 'i': 1,
'msg': { 'arch': 's390x',
'compose_id': 'RHEL-7.4-20170602.n.3',
'file': '/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/s390x/iso/RHEL-7.4-20170602.n.3-Server-s390x-dvd1.iso',
'location': 'http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3/compose',
'variant': 'Server'},
'timestamp': 1449605930.0,
'topic': '/topic/VirtualTopic.eng.pungi.createiso-imagedone'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.createiso-imagedone |
|
pungi finished createiso for Server/s390x/iso/RHEL-7.4-20170602.n.3-Server-s390x-dvd1.iso |
|
http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.createiso-targets¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when createiso targets are assigned.
You can view the history of messages with the eng.pungi.createiso-targets topic or all pungi messages in datagrepper.
{ 'i': 1,
'msg': { 'compose_id': 'RHEL-7.4-20170602.n.3',
'deliverables': [ '/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Client/x86_64/iso/RHEL-7.4-20170602.n.3-Client-x86_64-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Client/source/iso/RHEL-7.4-20170602.n.3-Client-source-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Client/source/iso/RHEL-7.4-20170602.n.3-Client-source-dvd2.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/aarch64/iso/RHEL-7.4-20170602.n.3-Server-aarch64-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/ppc64/iso/RHEL-7.4-20170602.n.3-Server-ppc64-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/ppc64le/iso/RHEL-7.4-20170602.n.3-Server-ppc64le-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/s390x/iso/RHEL-7.4-20170602.n.3-Server-s390x-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/x86_64/iso/RHEL-7.4-20170602.n.3-Server-x86_64-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/source/iso/RHEL-7.4-20170602.n.3-Server-source-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Server/source/iso/RHEL-7.4-20170602.n.3-Server-source-dvd2.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Workstation/x86_64/iso/RHEL-7.4-20170602.n.3-Workstation-x86_64-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Workstation/source/iso/RHEL-7.4-20170602.n.3-Workstation-source-dvd1.iso',
'/mnt/redhat/nightly/RHEL-7.4-20170602.n.3/compose/Workstation/source/iso/RHEL-7.4-20170602.n.3-Workstation-source-dvd2.iso'],
'location': 'http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3/compose'},
'msg_id': '2015-05ea75ce-f648-41b5-9e29-da56202a2ba5',
'timestamp': 1449605930.0,
'topic': '/topic/VirtualTopic.eng.pungi.createiso-targets'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.createiso-targets |
|
pungi assigned 13 createiso targets for RHEL-7.4-20170602.n.3 |
|
http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.ostree¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
It can produce ostrees… but it doesn’t seem to be used in production yet.
Here’s an example message published from Fedora when an ostree phase completed succesfully.
You can view the history of messages with the eng.pungi.ostree topic or all pungi messages in datagrepper.
{ 'i': 1,
'msg': { 'arch': 'x86_64',
'commitid': 'f99114401ffce2753bd7cd5401bff056a029bb80474859ab769f68586978248d',
'compose_id': 'Fedora-25-20161002.n.0',
'location': 'http://kojipkgs.fedoraproject.org/compose//branched/Fedora-25-20161002.n.0/compose',
'ref': 'fedora-atomic/25/x86_64/docker-host',
'variant': 'Atomic'},
'timestamp': 1475402944.0,
'topic': '/topic/VirtualTopic.eng.pungi.ostree'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.ostree |
|
pungi ostree compose Fedora-25-20161002.n.0 produced ostree commit f99114401ffce2753bd7cd5401bff056a029bb80474859ab769f68586978248d for x86_64 fedora-atomic/25/x86_64/docker-host |
|
http://kojipkgs.fedoraproject.org/compose//branched/Fedora-25-20161002.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.phase-start¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when the createrepo
phase of a
compose starts.
You can view the history of messages with the eng.pungi.phase-start topic or all pungi messages in datagrepper.
{ 'i': 1,
'msg': { 'compose_id': 'RHEL-7.4-20170602.n.3',
'location': 'http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3/compose',
'phase_name': 'createrepo'},
'timestamp': 1449605930.0,
'topic': '/topic/VirtualTopic.eng.pungi.phase-start'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.phase-start |
|
pungi started the createrepo phase of the RHEL-7.4-20170602.n.3 compose |
|
http://download.lab.bos.redhat.com/nightly/RHEL-7.4-20170602.n.3 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.status-change¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when a compose starts.
You can view the history of messages with the eng.pungi.status-change topic or all pungi messages in datagrepper.
{ 'msg': { 'compose_id': 'OracleJava-7.4-RHEL-7-20170602.n.0',
'location': '/mnt/redhat/nightly/OracleJava-7.4-RHEL-7-20170602.n.0/compose',
'status': 'STARTED'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.pungi.status-change'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.status-change |
|
pungi compose of OracleJava-7.4-RHEL-7-20170602.n.0 started |
|
http://download.lab.bos.redhat.com/nightly/OracleJava-7.4-RHEL-7-20170602.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.status-change¶
Pungi (also called distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when a compose completes.
You can view the history of messages with the eng.pungi.status-change topic or all pungi messages in datagrepper.
{ 'msg': { 'compose_id': 'OracleJava-7.4-RHEL-7-20170602.n.0',
'location': '/mnt/redhat/nightly/OracleJava-7.4-RHEL-7-20170602.n.0/compose',
'status': 'FINISHED'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.pungi.status-change'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.status-change |
|
pungi compose of OracleJava-7.4-RHEL-7-20170602.n.0 just finished |
|
http://download.lab.bos.redhat.com/nightly/OracleJava-7.4-RHEL-7-20170602.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.pungi.status-change¶
Pungi (previously known as distill) is the compose tool on which RCM is trying to standardize… and it’s on the message bus!
Here’s an example message published when a compose is killed.
You can view the history of messages with the eng.pungi.status-change topic or all pungi messages in datagrepper.
{ 'msg': { 'compose_id': 'OracleJava-7.4-RHEL-7-20170602.n.0',
'location': '/mnt/redhat/nightly/OracleJava-7.4-RHEL-7-20170602.n.0/compose',
'status': 'TERMINATED'},
'timestamp': 1449600728.0,
'topic': '/topic/VirtualTopic.eng.pungi.status-change'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
pungi.status-change |
|
pungi compose of OracleJava-7.4-RHEL-7-20170602.n.0 was terminated |
|
http://download.lab.bos.redhat.com/nightly/OracleJava-7.4-RHEL-7-20170602.n.0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.repotracker¶
eng.repotracker.container.tag.added¶
repotracker tracks container repositories, and publishes a message when they change.
An “added” message is published whenever a new tag is added to a repo.
You can view the history of messages with the eng.repotracker.container.tag.added topic or all repotracker messages in datagrepper.
{ 'headers': { 'JMS_AMQP_HEADER': 'true',
'JMS_AMQP_ORIGINAL_ENCODING': '5',
'JMS_AMQP_PROPERTIES': 'true',
'action': 'added',
'amq6100-destination': 'queue://Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'amq6100-originalDestination': 'topic://VirtualTopic.eng.repotracker.container.tag.added',
'arch': 'amd64',
'correlation-id': '8cbc21b0-785f-4bff-a456-53cd9d51dbd8',
'created': '2018-11-02T00:38:43.931368396Z',
'destination': '/topic/VirtualTopic.eng.repotracker.container.tag.added',
'digest': 'sha256:05329d12087818843f353c7d566b4442ceb67d871a049b3b1b88923b72635772',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4075:0:0:1',
'old_digest': 'null',
'original-destination': '/topic/VirtualTopic.eng.repotracker.container.tag.added',
'os': 'linux',
'priority': '4',
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'subscription': '/queue/Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'tag': 'testtag',
'timestamp': '0'},
'i': 0,
'msg': { 'action': 'added',
'arch': 'amd64',
'created': '2018-11-02T00:38:43.931368396Z',
'digest': 'sha256:05329d12087818843f353c7d566b4442ceb67d871a049b3b1b88923b72635772',
'labels': { 'license': 'GPLv3',
'name': 'repotracker',
'vendor': 'Factory 2.0'},
'old_digest': None,
'os': 'linux',
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'tag': 'testtag'},
'msg_id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4075:0:0:1',
'timestamp': 1541166247.0,
'topic': '/topic/VirtualTopic.eng.repotracker.container.tag.added'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
repotracker.container.tag.added |
|
testtag tag was added to the repotracker container repository |
|
|
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.repotracker.container.tag.removed¶
repotracker tracks container repositories, and publishes a message when they change.
A “removed” message is published whenever a tag is removed from a repo.
You can view the history of messages with the eng.repotracker.container.tag.removed topic or all repotracker messages in datagrepper.
{ 'headers': { 'JMS_AMQP_HEADER': 'true',
'JMS_AMQP_ORIGINAL_ENCODING': '5',
'JMS_AMQP_PROPERTIES': 'true',
'action': 'removed',
'amq6100-destination': 'queue://Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'amq6100-originalDestination': 'topic://VirtualTopic.eng.repotracker.container.tag.removed',
'arch': 'null',
'correlation-id': 'd59e960c-f7a7-403d-a7f5-c0ff980fd512',
'created': 'null',
'destination': '/topic/VirtualTopic.eng.repotracker.container.tag.removed',
'digest': 'null',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4206:0:0:1',
'old_digest': 'sha256:edf137791b86ac018ea1c29ddfddf7501fc4b383dc1a805d47aa83c2ff6ef9bc',
'original-destination': '/topic/VirtualTopic.eng.repotracker.container.tag.removed',
'os': 'null',
'priority': '4',
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'subscription': '/queue/Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'tag': 'testtag',
'timestamp': '0'},
'i': 0,
'msg': { 'action': 'removed',
'arch': None,
'created': None,
'digest': None,
'labels': {},
'old_digest': 'sha256:edf137791b86ac018ea1c29ddfddf7501fc4b383dc1a805d47aa83c2ff6ef9bc',
'os': None,
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'tag': 'testtag'},
'msg_id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4206:0:0:1',
'timestamp': 1541169058.0,
'topic': '/topic/VirtualTopic.eng.repotracker.container.tag.removed'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
repotracker.container.tag.removed |
|
testtag tag was removed from the repotracker container repository |
|
|
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.repotracker.container.tag.updated¶
repotracker tracks container repositories, and publishes a message when they change.
An “updated” message is published whenever the image referenced by a tag changes.
You can view the history of messages with the eng.repotracker.container.tag.updated topic or all repotracker messages in datagrepper.
{ 'headers': { 'JMS_AMQP_HEADER': 'true',
'JMS_AMQP_ORIGINAL_ENCODING': '5',
'JMS_AMQP_PROPERTIES': 'true',
'action': 'updated',
'amq6100-destination': 'queue://Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'amq6100-originalDestination': 'topic://VirtualTopic.eng.repotracker.container.tag.updated',
'arch': 'amd64',
'correlation-id': '399f1e13-51fb-435f-ada9-5513d6739cf4',
'created': '2018-11-01T23:29:20.140308268Z',
'destination': '/topic/VirtualTopic.eng.repotracker.container.tag.updated',
'digest': 'sha256:edf137791b86ac018ea1c29ddfddf7501fc4b383dc1a805d47aa83c2ff6ef9bc',
'expires': '0',
'message-id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4150:0:0:1',
'old_digest': 'sha256:05329d12087818843f353c7d566b4442ceb67d871a049b3b1b88923b72635772',
'original-destination': '/topic/VirtualTopic.eng.repotracker.container.tag.updated',
'os': 'linux',
'priority': '4',
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'subscription': '/queue/Consumer.client-datanommer.upshift-dev.VirtualTopic.eng.>',
'tag': 'testtag',
'timestamp': '0'},
'i': 0,
'msg': { 'action': 'updated',
'arch': 'amd64',
'created': '2018-11-01T23:29:20.140308268Z',
'digest': 'sha256:edf137791b86ac018ea1c29ddfddf7501fc4b383dc1a805d47aa83c2ff6ef9bc',
'labels': { 'license': 'GPLv3',
'name': 'repotracker',
'vendor': 'Factory 2.0'},
'old_digest': 'sha256:05329d12087818843f353c7d566b4442ceb67d871a049b3b1b88923b72635772',
'os': 'linux',
'repo': 'quay.io/factory2/repotracker',
'reponame': 'repotracker',
'tag': 'testtag'},
'msg_id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-39068-1541025216899-3:4150:0:0:1',
'timestamp': 1541167705.0,
'topic': '/topic/VirtualTopic.eng.repotracker.container.tag.updated'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
repotracker.container.tag.updated |
|
testtag tag was updated in the repotracker container repository |
|
|
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.resultsdb¶
eng.resultsdb.result.new¶
ResultsDB is a database for test results.
This message gets published whenever resultsdb ingests a new result.
You can view the history of messages with the eng.resultsdb.result.new topic or all resultsdb messages in datagrepper.
{ 'headers': { 'destination': '/topic/VirtualTopic.eng.resultsdb.result.new',
'expires': '1529956989165',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.com-...',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1529352189165'},
'msg': { 'data': { 'brew_task_id': ['16769734'],
'category': ['static-analysis'],
'ci_email': ['platform-ci@com'],
'ci_environment': ['None'],
'ci_irc': ['#baseosci'],
'ci_name': ['Platform CI'],
'ci_team': ['Platform QE'],
'ci_url': [ 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com'],
'component': ['rpm'],
'issuer': ['pmoravco'],
'item': ['foo-4.11.3-3400.el7'],
'log': [ 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com/job/ci-covscan/63806/console'],
'rebuild': [ 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com/job/ci-covscan/63806/rebuild/parameterized'],
'scratch': ['True'],
'system_os': ['None'],
'system_provider': ['None'],
'type': ['brew-build']},
'groups': ['d24e5ea3-7e88-4474-b0ad-360a0a26cf21'],
'href': 'https://resultsdb-api.engineering.com/api/v2.0/results/5231886',
'id': 5231886,
'note': '',
'outcome': 'PASSED',
'ref_url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com/job/ci-covscan/63806/',
'submit_time': '2018-06-18T20:03:08.233992',
'testcase': { 'href': 'https://resultsdb-api.engineering.com/api/v2.0/testcases/baseos-ci.brew-build.covscan.static-analysis',
'name': 'baseos-ci.brew-build.covscan.static-analysis',
'ref_url': 'https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com'}},
'msg_id': 'ID:messaging-devops-broker01.com-42045-1527890187852-2:346021:-1:1:1',
'timestamp': 1529352189.0,
'topic': '/topic/VirtualTopic.eng.resultsdb.result.new'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
resultsdb.result.new |
|
resultsdb saw baseos-ci.brew-build.covscan.static-analysis PASSED for foo-4.11.3-3400.el7 |
|
https://rpm-factory-jenkins.rhev-ci-vms.eng.rdu2.com/job/ci-covscan/63806/ |
|
None |
|
set() |
|
{‘foo’} |
|
Unspecified |
|
|
|
Unspecified |
eng.resultsdb.result.new¶
ResultsDB is a database for test results.
This message gets published whenever resultsdb ingests a new result.
You can view the history of messages with the eng.resultsdb.result.new topic or all resultsdb messages in datagrepper.
{ 'headers': { 'destination': '/topic/VirtualTopic.eng.resultsdb.result.new',
'message-id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-44807-1512072391381-3:1811626:-1:1:1',
'priority': '4',
'timestamp': '1514930340914'},
'i': 0,
'msg': { 'result': { 'id': 2854980,
'log_url': 'https://rpmdiff.engineering.redhat.com/run/185690/17',
'outcome': 'FAILED',
'prev_outcome': None,
'submit_time': '2018-01-02 21:58:58 UTC'},
'task': { 'item': 'qpid-dispatch-1.0.0-5.el6',
'name': 'dist.rpmdiff.analysis.patches',
'type': 'koji_build'}},
'msg_id': 'ID:messaging-devops-broker01.dev1.ext.devlab.redhat.com-44807-1512072391381-3:1811626:-1:1:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.8.2',
'timestamp': 1514930340.0,
'topic': '/topic/VirtualTopic.eng.resultsdb.result.new',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
resultsdb.result.new |
|
resultsdb saw dist.rpmdiff.analysis.patches FAILED for qpid-dispatch-1.0.0-5.el6 |
|
|
|
None |
|
set() |
|
{‘qpid-dispatch’} |
|
Unspecified |
|
|
|
Unspecified |
eng.rhchi¶
eng.rhchi.functional.finished¶
The RHCHI pipeline validates containers.
Messages (like the example given here) are published when the functional phase of the pipeline completes.
You can view the history of messages with the eng.rhchi.functional.finished topic or all rhchi messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'address': 'topic://VirtualTopic.eng.rhchi.functional.finished',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'content-length': '1803',
'destination': '/topic/VirtualTopic.eng.rhchi.functional.finished',
'expires': '0',
'finished': '1.502197302427723E9',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:232481:0:0:1',
'priority': '4',
'rhchi_stage': 'functional',
'status': 'passed',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'url': 'https://rhcs-stage-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cntr_dashost10_e2econtaine-386b5-stable-runtest//1'},
'i': 0,
'msg': { 'container_validation_data': { 'container_img': 'brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/e2e-container-test-product-docker:7.3-968',
'dist_git_branch': 'release-e2e-test-1.0-rhel-7',
'dist_git_hash': '7e99ac5542915fc9f650daddf735fdf924a99ae2'},
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.sanity.finished',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'finished': 1502194605.557325,
'original_topic': 'topic://VirtualTopic.eng.rhchi.sanity.finished',
'rhchi_stage': 'sanity',
'status': 'passed',
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.build.finished',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'finished': 1502194511.0,
'original_topic': 'topic://VirtualTopic.eng.rhchi.build.finished',
'rhchi_stage': 'build',
'status': 'passed',
'triggered_by': None,
'type': 'rhchi',
'url': 'https://brew.engineering.redhat.com/brew/buildinfo?buildID=580580'},
'type': 'rhchi',
'url': 'https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/1075/'}},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:232481:0:0:1',
'timestamp': 1502197289.0,
'topic': '/topic/VirtualTopic.eng.rhchi.functional.finished'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rhchi.functional.finished |
|
The functional phase of the RHCHI pipeline passed for rhel7/e2e-container-test-product-docker |
|
|
|
Unspecified |
|
Unspecified |
|
{‘e2e-container-test-product-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.rhchi.functional.started¶
The RHCHI pipeline validates containers.
Messages (like the example given here) are published when the functional phase of the pipeline starts.
You can view the history of messages with the eng.rhchi.functional.started topic or all rhchi messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'address': 'topic://VirtualTopic.eng.rhchi.functional.started',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'content-length': '1803',
'destination': '/topic/VirtualTopic.eng.rhchi.functional.started',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:230649:0:0:1',
'priority': '4',
'rhchi_stage': 'functional',
'started': '1.502194757670781E9',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'url': 'https://rhcs-stage-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cntr_dashost10_e2econtaine-386b5'},
'i': 0,
'msg': { 'container_validation_data': { 'container_img': 'brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/e2e-container-test-product-docker:7.3-968',
'dist_git_branch': 'release-e2e-test-1.0-rhel-7',
'dist_git_hash': '7e99ac5542915fc9f650daddf735fdf924a99ae2'},
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.sanity.finished',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'finished': 1502194605.557325,
'original_topic': 'topic://VirtualTopic.eng.rhchi.sanity.finished',
'rhchi_stage': 'sanity',
'status': 'passed',
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.build.finished',
'container_chidata_url': 'https://pkgs.devel.redhat.com/cgit/rpms/e2e-container-test-product-docker/plain/CHIData.yaml?h=7e99ac5542915fc9f650daddf735fdf924a99ae2',
'container_name': 'rhel7/e2e-container-test-product-docker',
'container_nvr': 'e2e-container-test-product-docker-7.3-968',
'container_validation_id': 'a9e8936b-be97-4811-b7c0-75a5c5fbce43',
'finished': 1502194511.0,
'original_topic': 'topic://VirtualTopic.eng.rhchi.build.finished',
'rhchi_stage': 'build',
'status': 'passed',
'triggered_by': None,
'type': 'rhchi',
'url': 'https://brew.engineering.redhat.com/brew/buildinfo?buildID=580580'},
'type': 'rhchi',
'url': 'https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/1075/'}},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:230649:0:0:1',
'timestamp': 1502194759.0,
'topic': '/topic/VirtualTopic.eng.rhchi.functional.started'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rhchi.functional.started |
|
The functional phase of the RHCHI pipeline started for rhel7/e2e-container-test-product-docker |
|
https://rhcs-stage-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cntr_dashost10_e2econtaine-386b5 |
|
Unspecified |
|
Unspecified |
|
{‘e2e-container-test-product-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.rhchi.sanity.finished¶
The RHCHI pipeline validates containers.
Messages (like the example given here) are published when the sanity phase of the pipeline completes.
You can view the history of messages with the eng.rhchi.sanity.finished topic or all rhchi messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'False',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'False',
'address': 'topic://VirtualTopic.eng.rhchi.sanity.finished',
'container_name': 'openshift3/metrics-hawkular-metrics',
'container_nvr': 'metrics-hawkular-metrics-docker-3.4.1-29',
'content-length': '881',
'destination': '/topic/VirtualTopic.eng.rhchi.sanity.finished',
'expires': '0',
'finished': '1.500320888567753E9',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-36770-1500288178994-2:18523:0:0:1',
'priority': '4',
'rhchi_stage': 'sanity',
'status': 'passed',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'url': 'https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/324/'},
'i': 0,
'msg': { 'container_validation_data': { 'container_img': { 'container_registry_url': 'brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/metrics-hawkular-metrics:3.4.1-29'},
'container_validation_id': '7a99050d-34c2-432d-a051-f55c3799db41',
'dist_git_branch': 'rhaos-3.4-rhel-7',
'dist_git_hash': '19881dfcf68522e4915cf7a5f0ea35fb95376f1c'},
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.build.finished',
'container_name': 'openshift3/metrics-hawkular-metrics',
'container_nvr': 'metrics-hawkular-metrics-docker-3.4.1-29',
'finished': 1500320505.0,
'original_topic': 'topic://VirtualTopic.eng.rhchi.build.finished',
'rhchi_stage': 'build',
'status': 'passed',
'triggered_by': None,
'type': 'rhchi',
'url': 'https://brew.engineering.redhat.com/brew/buildinfo?buildID=574451'}},
'msg_id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-36770-1500288178994-2:18523:0:0:1',
'timestamp': 1500320889.0,
'topic': '/topic/VirtualTopic.eng.rhchi.sanity.finished'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rhchi.sanity.finished |
|
The sanity phase of the RHCHI pipeline passed for openshift3/metrics-hawkular-metrics |
|
https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/324/ |
|
Unspecified |
|
Unspecified |
|
{‘metrics-hawkular-metrics-docker’} |
|
Unspecified |
|
|
|
Unspecified |
eng.rhchi.sanity.started¶
The RHCHI pipeline validates containers.
Messages (like the example given here) are published when the sanity phase of the pipeline starts.
You can view the history of messages with the eng.rhchi.sanity.started topic or all rhchi messages in datagrepper.
{ 'headers': { 'JMS_AMQP_FirstAcquirer': 'false',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'address': 'topic://VirtualTopic.eng.rhchi.sanity.started',
'container_chidata_url': 'http://git.app.eng.bos.redhat.com/git/rhchi.git/plain/tests/e2e/CHIData.yaml',
'container_name': 'chi-smoke-test',
'container_nvr': 'chi-smoke-test-af3ab946-bf36-484e-94b4-af00a16ddfd7',
'container_validation_id': 'af3ab946-bf36-484e-94b4-af00a16ddfd7',
'content-length': '1105',
'destination': '/topic/VirtualTopic.eng.rhchi.sanity.started',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:264280:0:0:1',
'priority': '4',
'rhchi_stage': 'sanity',
'started': '1.502234821027946E9',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '0',
'url': 'https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/1085/'},
'i': 0,
'msg': { 'container_validation_data': { 'container_img': '',
'dist_git_branch': '',
'dist_git_hash': ''},
'triggered_by': { 'JMS_AMQP_FirstAcquirer': False,
'JMS_AMQP_MESSAGE_FORMAT': 0,
'JMS_AMQP_NATIVE': False,
'address': 'topic://VirtualTopic.eng.rhchi.build.finished',
'container_chidata_url': 'http://git.app.eng.bos.redhat.com/git/rhchi.git/plain/tests/e2e/CHIData.yaml',
'container_name': 'chi-smoke-test',
'container_nvr': 'chi-smoke-test-af3ab946-bf36-484e-94b4-af00a16ddfd7',
'container_validation_id': 'af3ab946-bf36-484e-94b4-af00a16ddfd7',
'finished': 1502234823.80292,
'original_topic': 'topic://VirtualTopic.eng.rhchi.build.finished',
'rhchi_stage': 'build',
'status': 'passed',
'triggered_by': { 'container_chidata_url': 'http://git.app.eng.bos.redhat.com/git/rhchi.git/plain/tests/e2e/CHIData.yaml',
'container_name': 'chi-smoke-test',
'container_nvr': 'chi-smoke-test-af3ab946-bf36-484e-94b4-af00a16ddfd7',
'container_validation_id': 'af3ab946-bf36-484e-94b4-af00a16ddfd7',
'triggered_by': None},
'type': 'rhchi',
'url': 'https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/e2e-smoke-test/7/'}},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-37191-1501276833669-2:264280:0:0:1',
'timestamp': 1502234849.0,
'topic': '/topic/VirtualTopic.eng.rhchi.sanity.started'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rhchi.sanity.started |
|
The sanity phase of the RHCHI pipeline started for chi-smoke-test |
|
https://chi-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/sanity-prod/1085/ |
|
Unspecified |
|
Unspecified |
|
{‘chi-smoke-test-af3ab946-bf36-484e’} |
|
Unspecified |
|
|
|
Unspecified |
eng.robosignatory¶
eng.robosignatory.container.sign¶
Robosignatory is an auto-signing service driven by the UMB. Our plugin for it is called RADAS (RAD auto-signing service).
It publishes messages when it signs containers! Here’s an example:
You can view the history of messages with the eng.robosignatory.container.sign topic or all robosignatory messages in datagrepper.
{ 'headers': { 'content-type': 'text/plain',
'destination': '/topic/VirtualTopic.eng.robosignatory.container.sign',
'expires': '1503893646415',
'message-id': 'ID:messaging-devops-broker01.web.prod.ext.phx2.redhat.com-36838-1502307902532-3:2760:-1:1:3',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.openpaas-prod.VirtualTopic.eng.>',
'timestamp': '1503288846415'},
'i': 5403,
'msg': { 'errors': [],
'manifest_digest': 'sha256:9eba6f4b34e7d4b7223a97268eac35de335d9530c39f0bc4e3b3d41106d511f6',
'pub_task_id': 135422,
'repo': 'redhat-e2e-container-e2e-container-test-product',
'request_id': 'f9e63af7-256d-4bd1-b83d-32fa1ad6abbe',
'request_received_time': '2017-08-21T04:14:04.692167',
'sig_key_id': 'F21541EB',
'signed_claim': 'owGbwMvMwME4uavh1CdRx9eMaxkLksTiiwpyizPT...',
'signing_server_requested': '2017-08-21T04:14:05.748709',
'signing_server_responded': '2017-08-21T04:14:06.322313',
'signing_status': 'success'},
'msg_id': '2017-7868079f-621b-4e14-b139-ebfa95be2c9d',
'timestamp': 1503288846.0,
'topic': '/topic/VirtualTopic.eng.robosignatory.container.sign',
'username': 'fedmsg'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
robosignatory.container.sign |
|
attempt to sign the redhat-e2e-container-e2e-container-test-product container in pub task 135422 with F21541EB was met with success |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.rpmdiff¶
eng.rpmdiff.job.completed¶
The RPMDiff system performs analyses of rpms.
Messages (like the example given here) are published when an analysis job is completed. (An analysis job operates on a single rpm).
You can view the history of messages with the eng.rpmdiff.job.completed topic or all rpmdiff messages in datagrepper.
{ 'i': 0,
'msg': { 'baseline': None,
'errata_id': None,
'nvr': 'openshift-ansible-3.6.65.2-1.git.0.1a149c1.el7',
'overall_score': 'Needs inspection',
'package_name': 'openshift-ansible',
'run_id': 94268,
'source': 'RPMDIFF',
'type': 'ANALYSIS'},
'msg_id': 'ID\\cbrokerbroker-32888-1493960489068-4\\c151704\\c0\\c0\\c1',
'timestamp': 1494464973.0,
'topic': '/topic/VirtualTopic.eng.rpmdiff.job.completed',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rpmdiff.job.completed |
|
rpmdiff analysis of openshift-ansible-3.6.65.2-1.git.0.1a149c1.el7 is completed |
|
|
|
Unspecified |
|
Unspecified |
|
{‘openshift-ansible’} |
|
Unspecified |
|
|
|
Unspecified |
eng.rpmdiff.job.starting¶
The RPMDiff system performs analyses of rpms.
Messages (like the example given here) are published when an comparison job is starting. (A comparison job compares one rpm against a baseline rpm).
You can view the history of messages with the eng.rpmdiff.job.starting topic or all rpmdiff messages in datagrepper.
{ 'i': 0,
'msg': { 'baseline': 'openshift-ansible-3.6.65.1-1.git.0.1f50797.el7',
'errata_id': None,
'nvr': 'openshift-ansible-3.6.65.2-1.git.0.1a149c1.el7',
'overall_score': None,
'package_name': 'openshift-ansible',
'run_id': 94269,
'source': 'RPMDIFF',
'type': 'COMPARISON'},
'msg_id': 'ID\\csomebroker-32888-1493960489068-4\\c151703\\c0\\c0\\c1',
'source_name': 'datanommer',
'source_version': '0.7.0',
'timestamp': 1494464909.0,
'topic': '/topic/VirtualTopic.eng.rpmdiff.job.starting',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
rpmdiff.job.starting |
|
rpmdiff comparison of openshift-ansible is starting (3.6.65.2-1.git.0.1a149c1.el7 against 3.6.65.1-1.git.0.1f50797.el7) |
|
|
|
Unspecified |
|
Unspecified |
|
{‘openshift-ansible’} |
|
Unspecified |
|
|
|
Unspecified |
eng.snitch¶
eng.snitch¶
Simple parser of Snitch messages
You can view the history of messages with the eng.snitch topic or all snitch messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-snitch',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.snitch',
'correlation-id': '6b37e9b3-2c2d-4b3b-a2c1-26521f75b494',
'database': 'data',
'destination': '/topic/VirtualTopic.eng.snitch',
'entityName': 'containerImage',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-465383:541553:0:0:1',
'operationType': 'replace',
'original-destination': '/topic/VirtualTopic.eng.snitch',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'entityData': { '@mongoHidden': { 'docver': [ { '$oid': '5e1c24e8dd19c77896f587d4'}]},
'_id': {'$oid': '5e17f347dd19c77896f4f7c0'},
'architecture': 'arm64',
'certifications#': 0,
'certified': False,
'content_sets': [],
'content_sets#': 0,
'cpe_ids#': 0,
'cpe_ids_rh_base_images#': 0,
'createdBy': 'metaxor',
'creationDate': {'$date': 1578627911612}},
'entityName': 'containerImage'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-46538-1578341806859-3:541553:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1578902763.0,
'topic': '/topic/VirtualTopic.eng.snitch',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
snitch |
|
New DB event (replace): containerImage - 5e17f347dd19c77896f4f7c0 |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.snitch¶
Simple parser of Snitch messages
You can view the history of messages with the eng.snitch topic or all snitch messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'JMSXUserID': 'msg-snitch',
'JMS_AMQP_MESSAGE_FORMAT': '0',
'JMS_AMQP_NATIVE': 'false',
'amq6100_destination': 'queue://Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'amq6100_originalDestination': 'topic://VirtualTopic.eng.snitch',
'correlation-id': '6b37e9b3-2c2d-4b3b-a2c1-26521f75b494',
'database': 'data',
'destination': '/topic/VirtualTopic.eng.snitch',
'entityName': 'containerImage',
'expires': '0',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-465383:541553:0:0:1',
'operationType': 'replace',
'original-destination': '/topic/VirtualTopic.eng.snitch',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '0'},
'i': 0,
'msg': { 'entityData': { '@mongoHidden': { 'docver': [ { '$oid': '5e1c24e8dd19c77896f587d4'}]},
'_id': 'foo',
'architecture': 'arm64',
'certifications#': 0,
'certified': False,
'content_sets': [],
'content_sets#': 0,
'cpe_ids#': 0,
'cpe_ids_rh_base_images#': 0,
'createdBy': 'metaxor',
'creationDate': {'$date': 1578627911612}},
'entityName': 'containerImage'},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-46538-1578341806859-3:541553:0:0:1',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1578902763.0,
'topic': '/topic/VirtualTopic.eng.snitch',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
snitch |
|
New DB event (replace): containerImage - foo |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
|
|
Unspecified |
eng.tower¶
eng.tower¶
Test of Tower2UMB handler
Messages (like the example given here) are published when a job in Tower finishes
You can view the history of messages with the eng.tower topic or all tower messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.tower',
'expires': '1538059641455',
'message-id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-39834-1537414777669-3:506:-1:1:2',
'name': 'Tower2UMB - ping',
'priority': '4',
'project': 'Tower2UMB',
'status': 'failed',
'subscription': '/queue/Consumer.client-datanommer.upshift-stage.VirtualTopic.eng.>',
'timestamp': '1537454841455'},
'i': 0,
'msg': { 'created_by': 'araszka',
'credential': 'ansible',
'extra_vars': '{}',
'finished': '2018-09-20T14:47:20.823051Z',
'friendly_name': 'Job',
'hosts': { 'localhost': { 'changed': 0,
'dark': 1,
'failed': True,
'failures': 0,
'ok': 0,
'processed': 1,
'skipped': 0}},
'id': 37121,
'inventory': 'Tower2UMB',
'limit': '',
'name': 'Tower2UMB - ping',
'playbook': 'playbooks/ping.yml',
'project': 'Tower2UMB',
'started': '2018-09-20T14:47:04.527121Z',
'status': 'failed',
'traceback': '',
'url': 'https://tower.engineering.redhat.com/#/jobs/37121'},
'msg_id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-39834-1537414777669-3:506:-1:1:2',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1537454841.0,
'topic': '/topic/VirtualTopic.eng.tower',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
tower |
|
Tower template Tower2UMB - ping finished - failed |
|
|
|
Unspecified |
|
{‘araszka’} |
|
Unspecified |
|
{37121} |
|
Unspecified |
|
Unspecified |
eng.tower¶
Test of Tower2UMB handler - unknown message format
Messages (like the example given here) are published when a job in Tower finishes
You can view the history of messages with the eng.tower topic or all tower messages in datagrepper.
{ 'certificate': None,
'crypto': None,
'headers': { 'content-type': 'application/json',
'destination': '/topic/VirtualTopic.eng.tower',
'expires': '1538059641455',
'message-id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-39834-1537414777669-3:506:-1:1:2',
'name': 'Tower2UMB - ping',
'priority': '4',
'project': 'Tower2UMB',
'status': 'failed',
'subscription': '/queue/Consumer.client-datanommer.upshift-stage.VirtualTopic.eng.>',
'timestamp': '1537454841455'},
'i': 0,
'msg': 'Bad message format',
'msg_id': 'ID:messaging-devops-broker01.web.stage.ext.phx2.redhat.com-39834-1537414777669-3:506:-1:1:2',
'signature': None,
'source_name': 'datanommer',
'source_version': '0.9.1',
'timestamp': 1537454841.0,
'topic': '/topic/VirtualTopic.eng.tower',
'username': None}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
tower |
|
Unknown message format |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
|
Unspecified |
eng.waiverdb¶
eng.waiverdb.waiver.new¶
WaiverDB is a database for test waivers.
This message gets published whenever a test is “unwaived”.
You can view the history of messages with the eng.waiverdb.waiver.new topic or all waiverdb messages in datagrepper.
{ 'headers': { 'content-length': '390',
'destination': '/topic/VirtualTopic.eng.waiverdb.waiver.new',
'expires': '1544017394359',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-39733-1543394753117-2:1774:-1:1:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1543412594359'},
'i': 0,
'msg': { 'comment': 'Expected.',
'id': 32,
'product_version': 'rhel-8',
'proxied_by': None,
'subject': { 'item': 'rh-amazon-rhui-client-3.0.9-1.el8',
'type': 'koji_build'},
'subject_identifier': 'rh-amazon-rhui-client-3.0.9-1.el8',
'subject_type': 'koji_build',
'testcase': 'osci.brew-build.installability.functional',
'timestamp': '2018-11-28T13:43:13.895190',
'username': 'mminar',
'waived': False},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-39733-1543394753117-2:1774:-1:1:1',
'timestamp': 1543412594.0,
'topic': '/topic/VirtualTopic.eng.waiverdb.waiver.new'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
waiverdb.waiver.new |
|
mminar unwaived osci.brew-build.installability.functional on rh-amazon-rhui-client-3.0.9-1.el8 (rhel-8) |
|
|
|
mminar |
|
{‘mminar’} |
|
{‘rh-amazon-rhui-client’} |
|
Unspecified |
|
|
|
Unspecified |
eng.waiverdb.waiver.new¶
WaiverDB is a database for test waivers.
This message gets published whenever a new waiver is created.
You can view the history of messages with the eng.waiverdb.waiver.new topic or all waiverdb messages in datagrepper.
{ 'headers': { 'content-length': '451',
'destination': '/topic/VirtualTopic.eng.waiverdb.waiver.new',
'expires': '1544022879589',
'message-id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-39733-1543394753117-2:2457:-1:1:1',
'priority': '4',
'subscription': '/queue/Consumer.client-datanommer.upshift-prod.VirtualTopic.eng.>',
'timestamp': '1543418079589'},
'i': 0,
'msg': { 'comment': 'SELinux policy BaseOSCI tests(extended socket class '
'tests) are broken not the build',
'id': 36,
'product_version': 'rhel-8',
'proxied_by': None,
'subject': { 'item': 'selinux-policy-3.14.1-48.el8',
'type': 'koji_build'},
'subject_identifier': 'selinux-policy-3.14.1-48.el8',
'subject_type': 'koji_build',
'testcase': 'baseos-ci.brew-build.tier1.functional',
'timestamp': '2018-11-28T15:14:39.056328',
'username': 'lvrabec',
'waived': True},
'msg_id': 'ID:messaging-devops-broker02.web.prod.ext.phx2.redhat.com-39733-1543394753117-2:2457:-1:1:1',
'timestamp': 1543418079.0,
'topic': '/topic/VirtualTopic.eng.waiverdb.waiver.new'}
The example message above, when passed to various routines in the
fedmsg.meta
module, will produce the following outputs:
|
waiverdb.waiver.new |
|
lvrabec waived baseos-ci.brew-build.tier1.functional on selinux-policy-3.14.1-48.el8 (rhel-8) |
|
|
|
lvrabec |
|
{‘lvrabec’} |
|
{‘selinux-policy’} |
|
Unspecified |
|
|
|
Unspecified |