List of Message Topics

This document lists all the topics coming out the Fedora Infrastructure fedmsg bus. Example messages are included as well as descriptions and sample output from fedmsg.meta.

Note

All topics from Fedora Infrastructure are prefixed with org.fedoraproject.prod., but the topic_prefix is omitted here for brevity. For instance, the item listed as git.branch will actually be broadcast as org.fedoraproject.prod.git.branch.

Note

Message bodies can contain some useful information, but be wary. We have done as good a job as we can securing fedmsg, but it is still a new system. If you receive a message from pkgdb claiming that “ralph” is the new owner of the kernel, you should still check with the actual pkgdb service that this is the case. Write code against fedmsg messages as a tip, but always check the authoritative source before taking any programmatic action.

anitya

anitya.distro.add

These messages are published when a new Linux distribution is added to the database of anitya.

You can view the history of messages with the anitya.distro.add topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': { 'name': 'CentOS'},
           'message': { 'agent': 'foobar', 'distro': u'CentOS'},
           'project': None},
  'msg_id': u'2016-55d13473-2e48-4b6e-9542-3bc1882152ef',
  'timestamp': 1467814080,
  'topic': u'org.release-monitoring.prod.anitya.distro.add',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.distro.add
fedmsg.meta.msg2subtitle() foobar added the distro named “CentOS” to anitya
fedmsg.meta.msg2link() https://release-monitoring.org/distros
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘foobar’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘distros/CentOS’])
fedmsg.meta.msg2icon() 4cc7d54f-996c-46c6-aa24-c1b0d8748348-icon
fedmsg.meta.msg2secondary_icon() 4cc7d54f-996c-46c6-aa24-c1b0d8748348-secondary_icon

anitya.distro.edit

These messages are published when a Linux distribution’s entry is edited in the anitya database.

You can view the history of messages with the anitya.distro.edit topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 5,
  'msg': { 'distro': { 'name': 'Debia'},
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'new': 'Debian',
                        'old': 'Debia'},
           'project': None},
  'msg_id': '2014-746c39cf-9fb0-4ed1-a817-d57bc901e027',
  'timestamp': 1412328814,
  'topic': 'org.release-monitoring.prod.anitya.distro.edit',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.distro.edit
fedmsg.meta.msg2subtitle() pingou changed a distro name from “Debia” to “Debian”
fedmsg.meta.msg2link() https://release-monitoring.org/distros
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘distros/Debian’, ‘distros/Debia’])
fedmsg.meta.msg2icon() 4c23803f-4f71-4e5b-8301-7d18bd5b9330-icon
fedmsg.meta.msg2secondary_icon() 4c23803f-4f71-4e5b-8301-7d18bd5b9330-secondary_icon

anitya.distro.remove

These messages are published when an admin removes a distribution (in the anitya database…)

You can view the history of messages with the anitya.distro.remove topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': { 'name': 'Arch'},
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'distro': 'Arch'},
           'project': None},
  'msg_id': '2014-745132e5-17eb-4785-8663-fa89801a08ee',
  'timestamp': 1418315977,
  'topic': 'org.release-monitoring.prod.anitya.distro.remove',
  'username': 'pierrey'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.distro.remove
fedmsg.meta.msg2subtitle() pingou deleted the distro “Arch”
fedmsg.meta.msg2link() https://release-monitoring.org/distros
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘distros/Arch’])
fedmsg.meta.msg2icon() e1b16521-ea90-48a5-8be2-8908ab45172a-icon
fedmsg.meta.msg2secondary_icon() e1b16521-ea90-48a5-8be2-8908ab45172a-secondary_icon

anitya.project.add

These messages are published when someone adds a new project to anitya’s database.

You can view the history of messages with the anitya.project.add topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 8,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'project': 'arrow'},
           'project': { 'backend': 'PyPI',
                        'created_on': 1412328939.0,
                        'homepage': 'https://pypi.python.org/pypi/arrow',
                        'id': 5314,
                        'name': 'arrow',
                        'regex': None,
                        'updated_on': 1412328939.0,
                        'version': None,
                        'version_url': None,
                        'versions': []}},
  'msg_id': '2014-c95e6b4c-d033-43d9-9eb1-e1f92ac87c75',
  'timestamp': 1412328939,
  'topic': 'org.release-monitoring.prod.anitya.project.add',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.add
fedmsg.meta.msg2subtitle() ralph added the project “arrow” to anitya
fedmsg.meta.msg2link() https://release-monitoring.org/project/5314/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/arrow’])
fedmsg.meta.msg2icon() e04bcaf5-835f-468d-bf12-9084b23a4125-icon
fedmsg.meta.msg2secondary_icon() e04bcaf5-835f-468d-bf12-9084b23a4125-secondary_icon

anitya.project.add.tried

These messages are published when someone tries to add a new project to anitya’s database, but that project was already present.

You can view the history of messages with the anitya.project.add.tried topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'project': 'ansi2html'},
           'project': { 'created_on': 1386839688.0,
                        'homepage': 'https://github.com/ralphbean/ansi2html',
                        'id': 4,
                        'logs': None,
                        'name': 'ansi2html',
                        'packages': [],
                        'regex': 'DEFAULT:ansi2html',
                        'updated_on': 1386839688.0,
                        'version': [],
                        'version_url': 'PYPI-DEFAULT:ansi2html'}},
  'msg_id': '2013-154429ec-842e-4d7f-acae-8d7434b4cbff',
  'timestamp': 1386821688,
  'topic': 'org.release-monitoring.prod.anitya.project.add.tried',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.add.tried
fedmsg.meta.msg2subtitle() ralph tried to add the project “ansi2html” to anitya (but it already exists there)
fedmsg.meta.msg2link() https://release-monitoring.org/project/4/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/ansi2html’])
fedmsg.meta.msg2icon() 28a35b23-09d8-468f-aa4d-d97a9a15a4ca-icon
fedmsg.meta.msg2secondary_icon() 28a35b23-09d8-468f-aa4d-d97a9a15a4ca-secondary_icon

anitya.project.edit

These messages are published when someone edits the details of a project in anitya’s database.

You can view the history of messages with the anitya.project.edit topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 6,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'fields': ['homepage'],
                        'project': 'arrow'},
           'project': { 'backend': 'PyPI',
                        'created_on': 1412328939.0,
                        'homepage': 'http://crsmithdev.com/arrow',
                        'id': 5314,
                        'name': 'arrow',
                        'regex': None,
                        'updated_on': 1412328939.0,
                        'version': None,
                        'version_url': None,
                        'versions': []}},
  'msg_id': '2014-f25b6634-d7b9-4f2d-9f93-23ef73034024',
  'timestamp': 1412329027,
  'topic': 'org.release-monitoring.prod.anitya.project.edit',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.edit
fedmsg.meta.msg2subtitle() ralph edited the following fields of the “arrow” project: homepage
fedmsg.meta.msg2link() https://release-monitoring.org/project/5314/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/arrow’])
fedmsg.meta.msg2icon() d8f0f515-549f-4d2b-a4dd-5f1b212361d2-icon
fedmsg.meta.msg2secondary_icon() d8f0f515-549f-4d2b-a4dd-5f1b212361d2-secondary_icon

anitya.project.flag

These messages are published when an user flags a project in the anitya database to ask an admin to do something on a project.

You can view the history of messages with the anitya.project.flag topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'project': 'generic-colouriser',
                        'reason': 'Delete in favor of the correctly configured 7894.'},
           'project': { 'backend': 'Github',
                        'created_on': 1425912743.0,
                        'homepage': 'http://kassiopeia.juls.savba.sk/~garabik/software/grc.html',
                        'id': 5777,
                        'name': 'generic-colouriser',
                        'regex': None,
                        'updated_on': 1427848695.0,
                        'version': 'v1.9',
                        'version_url': 'garabik/grc',
                        'versions': ['v1.9', 'v1.7']}},
  'msg_id': '2015-7b2fca29-7409-43f2-949f-c688437ba5d4',
  'source_name': 'datanommer',
  'source_version': '0.6.5',
  'timestamp': 1445900487.0,
  'topic': 'org.release-monitoring.prod.anitya.project.flag'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.flag
fedmsg.meta.msg2subtitle() pingou flagged the project “generic-colouriser”
fedmsg.meta.msg2link() https://release-monitoring.org/project/5777/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/generic-colouriser’])
fedmsg.meta.msg2icon() fb3e2e50-61eb-489b-8ffb-2d1be1b0ff3b-icon
fedmsg.meta.msg2secondary_icon() fb3e2e50-61eb-489b-8ffb-2d1be1b0ff3b-secondary_icon

anitya.project.flag

These messages are published when an user flags a project in the anitya database to ask an admin to do something on a project.

You can view the history of messages with the anitya.project.flag topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'project': 'generic-colouriser',
                        'reason': 'Delete in favor of the correctly configured 7894.'},
           'packages': [ { 'distro': 'Fedora',
                           'package_name': 'generic-colouriser'}],
           'project': { 'backend': 'GitHub',
                        'created_on': 1425912743.0,
                        'homepage': 'http://kassiopeia.juls.savba.sk/~garabik/software/grc.html',
                        'id': 5777,
                        'name': 'generic-colouriser',
                        'regex': None,
                        'updated_on': 1427848695.0,
                        'version': 'v1.9',
                        'version_url': 'garabik/grc',
                        'versions': ['v1.9', 'v1.7']}},
  'msg_id': '2015-7b2fca29-7409-43f2-949f-c688437ba5d4',
  'source_name': 'datanommer',
  'source_version': '0.6.5',
  'timestamp': 1445900487.0,
  'topic': 'org.release-monitoring.prod.anitya.project.flag'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.flag
fedmsg.meta.msg2subtitle() pingou flagged the project “generic-colouriser”
fedmsg.meta.msg2link() https://release-monitoring.org/project/5777/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([‘generic-colouriser’])
fedmsg.meta.msg2objects() set([‘projects/generic-colouriser’])
fedmsg.meta.msg2icon() d965e49d-f5d8-4673-bc36-7ebfe528e5e3-icon
fedmsg.meta.msg2secondary_icon() d965e49d-f5d8-4673-bc36-7ebfe528e5e3-secondary_icon

anitya.project.flag.set

These messages are published when an user change the status of a flag in the anitya database.

You can view the history of messages with the anitya.project.flag.set topic or all anitya messages in datagrepper.

{ 'i': 4,
  'msg': { 'distro': None,
           'message': { 'agent': 'pingou@fedoraproject.org',
                        'flag': 184,
                        'state': 'closed'},
           'project': None},
  'msg_id': '2016-fc73c74c-fc5a-4f65-8ae9-87145bae82e4',
  'source_name': 'datanommer',
  'source_version': '0.6.5',
  'timestamp': 1468318351.0,
  'topic': 'org.release-monitoring.prod.anitya.project.flag.set'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.flag.set
fedmsg.meta.msg2subtitle() pingou closed flag “184”
fedmsg.meta.msg2link() https://release-monitoring.org/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘flag/184’])
fedmsg.meta.msg2icon() 666a052e-b6a7-4e9d-8837-39db9beb3561-icon
fedmsg.meta.msg2secondary_icon() 666a052e-b6a7-4e9d-8837-39db9beb3561-secondary_icon

anitya.project.map.new

These messages are published when someone maps an upstream project to a package name in a particular distribution (in the anitya database…)

You can view the history of messages with the anitya.project.map.new topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 7,
  'msg': { 'distro': { 'name': 'Fedora'},
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'distro': 'Fedora',
                        'new': 'python-arrow',
                        'project': 'arrow'},
           'project': { 'backend': 'PyPI',
                        'created_on': 1412328939.0,
                        'homepage': 'http://crsmithdev.com/arrow',
                        'id': 5314,
                        'name': 'arrow',
                        'regex': None,
                        'updated_on': 1412329027.0,
                        'version': None,
                        'version_url': None,
                        'versions': []}},
  'msg_id': '2014-9ebf960a-115e-4568-a615-34cc7d8d462e',
  'timestamp': 1412329216,
  'topic': 'org.release-monitoring.prod.anitya.project.map.new',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.map.new
fedmsg.meta.msg2subtitle() ralph mapped the name of “arrow” in Fedora to “python-arrow”
fedmsg.meta.msg2link() https://release-monitoring.org/project/5314/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘python-arrow’])
fedmsg.meta.msg2objects() set([‘projects/arrow’, ‘mappings/Fedora/python-arrow’, ‘distros/Fedora’])
fedmsg.meta.msg2icon() c6d123c5-8b0a-47fc-a1ef-fd13e65257c4-icon
fedmsg.meta.msg2secondary_icon() c6d123c5-8b0a-47fc-a1ef-fd13e65257c4-secondary_icon

anitya.project.map.remove

These messages are published when someone removes a mapping between an upstream project and a package name in a particular distribution (in the anitya database…)

You can view the history of messages with the anitya.project.map.remove topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 10,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'distro': 'Fedora',
                        'project': 'guake'},
           'project': { 'backend': 'Github',
                        'created_on': 1412237149.0,
                        'homepage': 'http://guake.org',
                        'id': 5311,
                        'name': 'guake',
                        'regex': '',
                        'updated_on': 1412237231.0,
                        'version': '0.5.0',
                        'version_url': 'guake/guake'}},
  'msg_id': '2014-1d43e5ab-e398-4007-8269-26b4f209d55b',
  'timestamp': 1412330764,
  'topic': 'org.release-monitoring.prod.anitya.project.map.remove',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.map.remove
fedmsg.meta.msg2subtitle() pingou deleted the mapping of “guake” project on “Fedora”
fedmsg.meta.msg2link() https://release-monitoring.org/project/5311/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/guake’])
fedmsg.meta.msg2icon() f759360b-5e22-45b9-8733-cc30c58130d9-icon
fedmsg.meta.msg2secondary_icon() f759360b-5e22-45b9-8733-cc30c58130d9-secondary_icon

anitya.project.map.update

These messages are published when someone updates the mapping between an upstream project and a package name in a particular distribution (in the anitya database…)

You can view the history of messages with the anitya.project.map.update topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 8,
  'msg': { 'distro': { 'name': 'Fedora'},
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'distro': 'Fedora',
                        'edited': ['package_name'],
                        'new': 'guake',
                        'prev': 'guake2',
                        'project': 'guake'},
           'project': { 'backend': 'Github',
                        'created_on': 1412237149.0,
                        'homepage': 'http://guake.org',
                        'id': 5311,
                        'name': 'guake',
                        'regex': None,
                        'updated_on': 1412237231.0,
                        'version': '0.5.0',
                        'version_url': 'guake/guake',
                        'versions': []}},
  'msg_id': '2014-5bd228ac-4ba1-452f-b6d2-b4df53c9af14',
  'timestamp': 1412329667,
  'topic': 'org.release-monitoring.prod.anitya.project.map.update',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.map.update
fedmsg.meta.msg2subtitle() ralph updated the name of “guake” in “Fedora” from “guake2” to “guake”
fedmsg.meta.msg2link() https://release-monitoring.org/project/5311/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘guake’, ‘guake2’])
fedmsg.meta.msg2objects() set([‘projects/guake’, ‘mappings/Fedora/guake2’, ‘mappings/Fedora/guake’, ‘distros/Fedora’])
fedmsg.meta.msg2icon() 1110ce43-b251-4b17-b1f8-82190808df1c-icon
fedmsg.meta.msg2secondary_icon() 1110ce43-b251-4b17-b1f8-82190808df1c-secondary_icon

anitya.project.remove

These messages are published when someone removes a project from anitya’s database.

You can view the history of messages with the anitya.project.remove topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 11,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://ralph.id.fedoraproject.org/',
                        'project': 'guake'},
           'project': { 'backend': 'GitHub',
                        'created_on': 1412237149.0,
                        'homepage': 'http://guake.org',
                        'id': 5311,
                        'name': 'guake',
                        'regex': None,
                        'updated_on': 1412237231.0,
                        'version': '0.5.0',
                        'version_url': 'guake/guake',
                        'versions': []}},
  'msg_id': '2014-94864be5-f649-4b3f-8694-32f238ac7174',
  'timestamp': 1412331340,
  'topic': 'org.release-monitoring.prod.anitya.project.remove',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.remove
fedmsg.meta.msg2subtitle() ralph deleted the “guake” project
fedmsg.meta.msg2link() https://release-monitoring.org/project/5311/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/guake’])
fedmsg.meta.msg2icon() 0bb480f4-9968-49c8-9854-f04476cabd4a-icon
fedmsg.meta.msg2secondary_icon() 0bb480f4-9968-49c8-9854-f04476cabd4a-secondary_icon

anitya.project.version.remove

These messages are published when an admin removes a version from a particular project (in the anitya database…)

You can view the history of messages with the anitya.project.version.remove topic or all anitya messages in datagrepper.

{ 'i': 1,
  'msg': { 'distro': None,
           'message': { 'agent': 'http://pingou.id.fedoraproject.org/',
                        'project': '3proxy',
                        'version': '0.7.1.1'},
           'project': { 'backend': 'custom',
                        'created_on': 1409917223.0,
                        'homepage': 'http://www.3proxy.ru/download/',
                        'id': 3,
                        'name': '3proxy',
                        'regex': None,
                        'updated_on': 1412690620.0,
                        'version': '0.7.1.1',
                        'version_url': 'http://www.3proxy.ru/download/',
                        'versions': []}},
  'msg_id': '2014-7926f638-1d0c-470c-b589-de84f5d34fad',
  'timestamp': 1415118527,
  'topic': 'org.release-monitoring.prod.anitya.project.version.remove',
  'username': 'pingou'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.version.remove
fedmsg.meta.msg2subtitle() pingou deleted the version 0.7.1.1 of “3proxy”
fedmsg.meta.msg2link() https://release-monitoring.org/project/3/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘pingou’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘projects/3proxy’])
fedmsg.meta.msg2icon() c347fdae-9a8d-43d0-9b34-bc1e8c31a361-icon
fedmsg.meta.msg2secondary_icon() c347fdae-9a8d-43d0-9b34-bc1e8c31a361-secondary_icon

anitya.project.version.update

The purpose of anitya is to monitor upstream projects and to try and detect when they release new tarballs.

This message is an example of what gets published when the first tarball of a project is ever seen by anitya.

You can view the history of messages with the anitya.project.version.update topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'distro': None,
           'message': { 'agent': 'anitya',
                        'old_version': '',
                        'packages': [ { 'distro': 'Fedora',
                                        'package_name': '2ping'}],
                        'project': { 'backend': 'custom',
                                     'created_on': 1412174944.0,
                                     'homepage': 'http://www.finnie.org/software/2ping/',
                                     'id': 2,
                                     'name': '2ping',
                                     'regex': None,
                                     'updated_on': 1412179539.0,
                                     'version': '2.1.1',
                                     'version_url': 'http://www.finnie.org/software/2ping/'},
                        'upstream_version': '2.1.1',
                        'versions': ['2.1.1']},
           'project': { 'backend': 'custom',
                        'created_on': 1412174944.0,
                        'homepage': 'http://www.finnie.org/software/2ping/',
                        'id': 2,
                        'name': '2ping',
                        'regex': None,
                        'updated_on': 1412179539.0,
                        'version': '2.1.1',
                        'version_url': 'http://www.finnie.org/software/2ping/'}},
  'msg_id': '2014-f4dfc3e4-8909-45d7-b929-1862efb373cf',
  'timestamp': 1412234961,
  'topic': 'org.release-monitoring.prod.anitya.project.version.update',
  'username': 'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.version.update
fedmsg.meta.msg2subtitle() A new version of “2ping” has been detected: “2.1.1”, packaged as “2ping”
fedmsg.meta.msg2link() https://release-monitoring.org/project/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘anitya’])
fedmsg.meta.msg2packages() set([‘2ping’])
fedmsg.meta.msg2objects() set([‘projects/2ping’])
fedmsg.meta.msg2icon() d8e911dd-f3b3-4eec-9fe3-0c9895e25983-icon
fedmsg.meta.msg2secondary_icon() Unspecified

anitya.project.version.update

The purpose of anitya is to monitor upstream projects and to try and detect when they release new tarballs.

These messages are the ones that get published when a tarball is found that is newer than the one last seen in the anitya database.

You can view the history of messages with the anitya.project.version.update topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'distro': None,
           'message': { 'agent': 'anitya',
                        'old_version': '2.1.0',
                        'packages': [ { 'distro': 'Fedora',
                                        'package_name': '2ping'}],
                        'project': { 'backend': 'custom',
                                     'created_on': 1412174944.0,
                                     'homepage': 'http://www.finnie.org/software/2ping/',
                                     'id': 2,
                                     'name': '2ping',
                                     'regex': None,
                                     'updated_on': 1412179539.0,
                                     'version': '2.1.1',
                                     'version_url': 'http://www.finnie.org/software/2ping/'},
                        'upstream_version': '2.1.1',
                        'versions': ['2.1.1']},
           'project': { 'backend': 'custom',
                        'created_on': 1412174944.0,
                        'homepage': 'http://www.finnie.org/software/2ping/',
                        'id': 2,
                        'name': '2ping',
                        'regex': None,
                        'updated_on': 1412179539.0,
                        'version': '2.1.1',
                        'version_url': 'http://www.finnie.org/software/2ping/'}},
  'msg_id': '2014-f4dfc3e4-8909-45d7-b929-1862efb373cf',
  'timestamp': 1412234961,
  'topic': 'org.release-monitoring.prod.anitya.project.version.update',
  'username': 'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.version.update
fedmsg.meta.msg2subtitle() A new version of “2ping” has been detected: “2.1.1” newer than “2.1.0”, packaged as “2ping”
fedmsg.meta.msg2link() https://release-monitoring.org/project/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘anitya’])
fedmsg.meta.msg2packages() set([‘2ping’])
fedmsg.meta.msg2objects() set([‘projects/2ping’])
fedmsg.meta.msg2icon() e519dd9a-db4a-4ca7-a3c1-1caa28e7413e-icon
fedmsg.meta.msg2secondary_icon() Unspecified

anitya.project.version.update

The purpose of anitya is to monitor upstream projects and to try and detect when they release new tarballs.

These messages are the ones that get published when a tarball is found that is newer than the one last seen in the anitya database.

You can view the history of messages with the anitya.project.version.update topic or all anitya messages in datagrepper.

{ 'i': 17,
  'msg': { 'distro': None,
           'message': { 'agent': 'anitya',
                        'old_version': '0.9.9',
                        'packages': [ { 'distro': 'Fedora',
                                        'package_name': 'python-sqlalchemy'},
                                      { 'distro': 'Fedora',
                                        'package_name': 'python-sqlalchemy0.5'}],
                        'project': { 'backend': 'pypi',
                                     'created_on': 1412175085.0,
                                     'homepage': 'https://pypi.python.org/pypi/SQLAlchemy',
                                     'id': 4034,
                                     'name': 'SQLAlchemy',
                                     'regex': None,
                                     'updated_on': 1426167440.0,
                                     'version': '1.0.0b1',
                                     'version_url': None,
                                     'versions': [ '1.0.0b1',
                                                   '0.9.9',
                                                   '0.9.8',
                                                   '0.9.7']},
                        'upstream_version': '1.0.0b1',
                        'versions': ['1.0.0b1', '0.9.9', '0.9.8', '0.9.7']},
           'project': { 'backend': 'pypi',
                        'created_on': 1412175085.0,
                        'homepage': 'https://pypi.python.org/pypi/SQLAlchemy',
                        'id': 4034,
                        'name': 'SQLAlchemy',
                        'regex': None,
                        'updated_on': 1426296430.0,
                        'version': '1.0.0b1',
                        'version_url': None,
                        'versions': ['1.0.0b1', '0.9.9', '0.9.8', '0.9.7']}},
  'msg_id': '2015-b2e3fab5-12a6-47b0-9ffc-c21d5789a2d0',
  'source_name': 'datanommer',
  'source_version': '0.6.4',
  'timestamp': 1426296431.0,
  'topic': 'org.release-monitoring.prod.anitya.project.version.update'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.version.update
fedmsg.meta.msg2subtitle() A new version of “SQLAlchemy” has been detected: “1.0.0b1” newer than “0.9.9”, packaged as “python-sqlalchemy and python-sqlalchemy0.5”
fedmsg.meta.msg2link() https://release-monitoring.org/project/4034/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘anitya’])
fedmsg.meta.msg2packages() set([‘python-sqlalchemy’, ‘python-sqlalchemy0.5’])
fedmsg.meta.msg2objects() set([‘projects/SQLAlchemy’])
fedmsg.meta.msg2icon() 4884868f-df36-459e-9a74-993c304b71f0-icon
fedmsg.meta.msg2secondary_icon() Unspecified

anitya.project.version.update

The purpose of anitya is to monitor upstream projects and to try and detect when they release new tarballs.

These messages are the ones that get published when a tarball is found that is older than the one last seen in the anitya database.

You can view the history of messages with the anitya.project.version.update topic or all anitya messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'distro': None,
           'message': { 'agent': 'anitya',
                        'odd_change': True,
                        'old_version': '2.1.1',
                        'packages': [ { 'distro': 'Fedora',
                                        'package_name': '2ping'}],
                        'project': { 'backend': 'custom',
                                     'created_on': 1412174944.0,
                                     'homepage': 'http://www.finnie.org/software/2ping/',
                                     'id': 2,
                                     'name': '2ping',
                                     'regex': None,
                                     'updated_on': 1412179539.0,
                                     'version': '2.1.1',
                                     'version_url': 'http://www.finnie.org/software/2ping/'},
                        'upstream_version': '2.1.0',
                        'versions': ['2.1.1']},
           'project': { 'backend': 'custom',
                        'created_on': 1412174944.0,
                        'homepage': 'http://www.finnie.org/software/2ping/',
                        'id': 2,
                        'name': '2ping',
                        'regex': None,
                        'updated_on': 1412179539.0,
                        'version': '2.1.1',
                        'version_url': 'http://www.finnie.org/software/2ping/'}},
  'msg_id': '2014-f4dfc3e4-8909-45d7-b929-1862efb373cf',
  'timestamp': 1412234961,
  'topic': 'org.release-monitoring.prod.anitya.project.version.update',
  'username': 'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() anitya.project.version.update
fedmsg.meta.msg2subtitle() A new version of “2ping” has been detected: “2.1.0”, packaged as “2ping”
fedmsg.meta.msg2link() https://release-monitoring.org/project/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘anitya’])
fedmsg.meta.msg2packages() set([‘2ping’])
fedmsg.meta.msg2objects() set([‘projects/2ping’])
fedmsg.meta.msg2icon() 24971e8e-4827-4add-94b3-a7fc4fe76e17-icon
fedmsg.meta.msg2secondary_icon() Unspecified

ansible

ansible.playbook.complete

These messages are published when an admin finishes an ansible playbook run. We use that system to manage the servers that run fedoraproject.org. Here’s an example with a playbook that has been checked into our SCM repo.

You can view the history of messages with the ansible.playbook.complete topic or all ansible messages in datagrepper.

{ 'i': 2,
  'msg': { 'playbook': '/srv/web/infra/ansible/playbooks/groups/badges-backend.yml',
           'results': { 'badges-backend01.phx2.fedoraproject.org': { 'changed': 1,
                                                                     'failures': 0,
                                                                     'ok': 56,
                                                                     'skipped': 9,
                                                                     'unreachable': 0},
                        'badges-backend01.stg.phx2.fedoraproject.org': { 'changed': 1,
                                                                         'failures': 0,
                                                                         'ok': 56,
                                                                         'skipped': 9,
                                                                         'unreachable': 0}},
           'userid': 'ralph'},
  'timestamp': 1375753955.771203,
  'topic': 'org.fedoraproject.prod.ansible.playbook.complete',
  'username': 'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ansible.playbook.complete
fedmsg.meta.msg2subtitle() ralph’s playbooks/groups/badges-backend.yml playbook run completed
fedmsg.meta.msg2link() http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/groups/badges-backend.yml
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘playbooks/groups/badges-backend.yml’, ‘inventory/badges-backend01.stg.phx2.fedoraproject.org’, ‘inventory/badges-backend01.phx2.fedoraproject.org’])
fedmsg.meta.msg2icon() b682016a-9089-4091-8254-b02e54a1a362-icon
fedmsg.meta.msg2secondary_icon() b682016a-9089-4091-8254-b02e54a1a362-secondary_icon

ansible.playbook.complete

These messages are published when an admin finishes an ansible playbook run. We use that system to manage the servers that run fedoraproject.org. Here’s an example with a playbook that is not actually checked into our SCM repo.

You can view the history of messages with the ansible.playbook.complete topic or all ansible messages in datagrepper.

{ 'i': 2,
  'msg': { 'playbook': '/home/fedora/ralph/ansible/playbooks/groups/badges-backend.yml',
           'results': { 'badges-backend01.phx2.fedoraproject.org': { 'changed': 1,
                                                                     'failures': 0,
                                                                     'ok': 56,
                                                                     'skipped': 9,
                                                                     'unreachable': 0},
                        'badges-backend01.stg.phx2.fedoraproject.org': { 'changed': 1,
                                                                         'failures': 0,
                                                                         'ok': 56,
                                                                         'skipped': 9,
                                                                         'unreachable': 0}},
           'userid': 'ralph'},
  'timestamp': 1375753955.771203,
  'topic': 'org.fedoraproject.prod.ansible.playbook.complete',
  'username': 'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ansible.playbook.complete
fedmsg.meta.msg2subtitle() ralph’s badges-backend.yml playbook run completed
fedmsg.meta.msg2link() None
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘inventory/badges-backend01.stg.phx2.fedoraproject.org’, ‘uncontrolled-playbooks/badges-backend.yml’, ‘inventory/badges-backend01.phx2.fedoraproject.org’])
fedmsg.meta.msg2icon() 38112d01-1828-418d-8c80-38dff77e827c-icon
fedmsg.meta.msg2secondary_icon() 38112d01-1828-418d-8c80-38dff77e827c-secondary_icon

ansible.playbook.start

These messages are published when an admin begins an ansible playbook run. We use that system to manage the servers that run fedoraproject.org.

You can view the history of messages with the ansible.playbook.start topic or all ansible messages in datagrepper.

{ 'i': 1,
  'msg': { 'check': False,
           'extra_vars': { },
           'inventory': '/srv/web/infra/ansible/inventory/',
           'playbook': '/srv/web/infra/ansible/playbooks/groups/badges-backend.yml',
           'playbook_checksum': False,
           'userid': 'ralph'},
  'timestamp': 1375753735.32427,
  'topic': 'org.fedoraproject.prod.ansible.playbook.start',
  'username': 'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ansible.playbook.start
fedmsg.meta.msg2subtitle() ralph started an ansible run of playbooks/groups/badges-backend.yml
fedmsg.meta.msg2link() http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/groups/badges-backend.yml
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘playbooks/groups/badges-backend.yml’])
fedmsg.meta.msg2icon() f88782b5-1001-4364-b4c7-39358fb34ffa-icon
fedmsg.meta.msg2secondary_icon() f88782b5-1001-4364-b4c7-39358fb34ffa-secondary_icon

askbot

askbot.post.delete

Messages with the askbot.post.delete topic get sent when either a question or an answer are deleted from Ask Fedora. The example here is one of an answer being deleted.

You can view the history of messages with the askbot.post.delete topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'instance': { 'comment_count': 0,
                         'pk': 12,
                         'post_type': 'answer',
                         'summary': 'oh, ok.. coolio\n ...',
                         'text': 'oh, ok.. coolio',
                         'vote_down_count': 0,
                         'vote_up_count': 0},
           'thread': { 'pk': 7,
                       'tagnames': [''],
                       'title': 'test 3 is a charm'},
           'topmost_post_id': 10},
  'timestamp': 1359949257.459819,
  'topic': 'org.fedoraproject.prod.askbot.post.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.delete
fedmsg.meta.msg2subtitle() ralph deleted an answer on ‘test 3 is a charm’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/10/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/7’])
fedmsg.meta.msg2icon() 0764e290-8f30-4d66-a344-8101a397827d-icon
fedmsg.meta.msg2secondary_icon() 0764e290-8f30-4d66-a344-8101a397827d-secondary_icon

askbot.post.delete

Messages with the askbot.post.delete topic get sent when either a question or an answer are deleted from Ask Fedora. The example here is one of an question being deleted.

You can view the history of messages with the askbot.post.delete topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'instance': { 'comment_count': 1,
                         'pk': 10,
                         'post_type': 'question',
                         'summary': 'this is a test message.\n ...',
                         'text': 'this is a test message.',
                         'vote_down_count': 0,
                         'vote_up_count': 0},
           'thread': { 'pk': 7,
                       'tagnames': [''],
                       'title': 'test 3 is a charm'},
           'topmost_post_id': 10},
  'timestamp': 1359949397.539748,
  'topic': 'org.fedoraproject.prod.askbot.post.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.delete
fedmsg.meta.msg2subtitle() ralph deleted the question ‘test 3 is a charm’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/10/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/7’])
fedmsg.meta.msg2icon() 04770a4e-5f9b-40e6-b369-2ec2f94ad68c-icon
fedmsg.meta.msg2secondary_icon() 04770a4e-5f9b-40e6-b369-2ec2f94ad68c-secondary_icon

askbot.post.edit

Messages get emitted on this topic anytime a question is updated. An ‘update’ includes a new question, a new answer, and a modification to either. This example is one of a new answer being posted to an Ask Fedora question.

You can view the history of messages with the askbot.post.edit topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'created': True,
           'diff': 'I know the answer\n\nlololololol I do!     I swear.\n ...',
           'newly_mentioned_users': ['lmacken'],
           'post': { 'comment_count': 0,
                     'pk': 5,
                     'post_type': 'answer',
                     'summary': 'I know the answer\n\nlololololol I do!     I swear.\n ...',
                     'text': 'I know the answer\r\n\r\nlololololol I do!     I swear.',
                     'vote_down_count': 0,
                     'vote_up_count': 0},
           'thread': { 'pk': 1,
                       'tagnames': ['cool'],
                       'title': 'watwatwatwata'},
           'timestamp': 1359946481.0,
           'topmost_post_id': 1},
  'timestamp': 1359946482.179817,
  'topic': 'org.fedoraproject.prod.askbot.post.edit',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.edit
fedmsg.meta.msg2subtitle() ralph suggested an answer to the question ‘watwatwatwata’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/1/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’, ‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/1’, ‘tags/cool’])
fedmsg.meta.msg2icon() 1ca0248d-bbe1-41d0-a5ce-f13be3e92d7e-icon
fedmsg.meta.msg2secondary_icon() 1ca0248d-bbe1-41d0-a5ce-f13be3e92d7e-secondary_icon

askbot.post.edit

Messages get emitted on this topic anytime an Ask Fedora question is updated. The snippet we have below is an example of a user posting a brand new question to Ask Fedora.

You can view the history of messages with the askbot.post.edit topic or all askbot messages in datagrepper.

{ 'i': 2,
  'msg': { 'agent': 'ralph',
           'created': True,
           'diff': 'lololol\n\nthis is my entry, I hope that you like it so very much.\n ...',
           'newly_mentioned_users': [],
           'post': { 'comment_count': 0,
                     'pk': 4,
                     'post_type': 'question',
                     'summary': 'lololol\n\nthis is my entry, I hope that you like it so very much.\n ...',
                     'text': 'lololol\r\n\r\nthis is my entry, I hope that you like it so very much.',
                     'vote_down_count': 0,
                     'vote_up_count': 0},
           'thread': { 'pk': 3,
                       'tagnames': ['lolol'],
                       'title': 'I have a new question'},
           'timestamp': 1359946267.0,
           'topmost_post_id': 3},
  'timestamp': 1359946267.401213,
  'topic': 'org.fedoraproject.prod.askbot.post.edit',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.edit
fedmsg.meta.msg2subtitle() ralph asked the question ‘I have a new question’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/3/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/3’, ‘tags/lolol’])
fedmsg.meta.msg2icon() ba863e3e-9797-4845-8153-194ddc4af7bb-icon
fedmsg.meta.msg2secondary_icon() ba863e3e-9797-4845-8153-194ddc4af7bb-secondary_icon

askbot.post.edit

Messages get emitted on this topic anytime a question is updated. An ‘update’ includes a new question, a new answer, and a modification to either. This example is one of a answer being modified on Ask Fedora.

You can view the history of messages with the askbot.post.edit topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'created': False,
           'diff': '<p>this is my test <del>answer</del><ins>answer.ok?</ins></p>\n',
           'newly_mentioned_users': [],
           'post': { 'comment_count': 0,
                     'pk': 6,
                     'post_type': 'answer',
                     'summary': 'this is my test answer.    ok?\n ...',
                     'text': 'this is my test answer.    ok?',
                     'vote_down_count': 0,
                     'vote_up_count': 0},
           'thread': { 'pk': 3,
                       'tagnames': ['lolol'],
                       'title': 'I have a new question'},
           'timestamp': 1359947977.0,
           'topmost_post_id': 3},
  'timestamp': 1359947978.125892,
  'topic': 'org.fedoraproject.prod.askbot.post.edit',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.edit
fedmsg.meta.msg2subtitle() ralph updated an answer to the question ‘I have a new question’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/3/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/3’, ‘tags/lolol’])
fedmsg.meta.msg2icon() 4023bb7d-8c3b-4049-92e3-e76aaa61c637-icon
fedmsg.meta.msg2secondary_icon() 4023bb7d-8c3b-4049-92e3-e76aaa61c637-secondary_icon

askbot.post.edit

Messages get emitted on this topic anytime a question is updated. An ‘update’ includes a new question, a new answer, and a modification to either. This example is one of a question being modified on Ask Fedora.

You can view the history of messages with the askbot.post.edit topic or all askbot messages in datagrepper.

{ 'i': 2,
  'msg': { 'agent': 'ralph',
           'created': False,
           'diff': '<p>alskdfj... the diff is actually here',
           'newly_mentioned_users': [],
           'post': { 'comment_count': 0,
                     'pk': 2,
                     'post_type': 'question',
                     'summary': 'alskdfjalskdjf alkjasdalskdjf ...',
                     'text': 'alskdfjalskdjf alkjasdalskdjf ...',
                     'vote_down_count': 0,
                     'vote_up_count': 0},
           'thread': { 'pk': 2,
                       'tagnames': ['town'],
                       'title': 'alskdjflaksjdf lakjsf a'},
           'timestamp': 1359947640.0,
           'topmost_post_id': 2},
  'timestamp': 1359947640.986208,
  'topic': 'org.fedoraproject.prod.askbot.post.edit',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.edit
fedmsg.meta.msg2subtitle() ralph updated the question ‘alskdjflaksjdf lakjsf a’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/2’, ‘tags/town’])
fedmsg.meta.msg2icon() f3aad7dd-496b-4103-811d-3fa8dbe30aa4-icon
fedmsg.meta.msg2secondary_icon() f3aad7dd-496b-4103-811d-3fa8dbe30aa4-secondary_icon

askbot.post.flag_offensive.add

Sent when a user flags an Ask Fedora question or answer as “offensive”.

You can view the history of messages with the askbot.post.flag_offensive.add topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'instance': { 'comment_count': 0,
                         'pk': 3,
                         'post_type': 'question',
                         'summary': 'I think I know... totally.    asldkj for sure.\n ...',
                         'text': 'I think I know... totally.    asldkj for sure.',
                         'vote_down_count': 0,
                         'vote_up_count': 1},
           'thread': { 'pk': 2,
                       'tagnames': ['town', 'ohok'],
                       'title': 'alskdjflaksjdf lakjsf a'},
           'topmost_post_id': 2},
  'timestamp': 1359947156.346592,
  'topic': 'org.fedoraproject.prod.askbot.post.flag_offensive.add',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.flag_offensive.add
fedmsg.meta.msg2subtitle() ralph flagged a question as offensive!
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/2’, ‘tags/ohok’, ‘tags/town’])
fedmsg.meta.msg2icon() 7bb490d0-8eaa-49fe-a288-2abd2af0d3d9-icon
fedmsg.meta.msg2secondary_icon() 7bb490d0-8eaa-49fe-a288-2abd2af0d3d9-secondary_icon

askbot.post.flag_offensive.delete

Sent when a user *un*flags an Ask Fedora question or answer as “offensive”.

You can view the history of messages with the askbot.post.flag_offensive.delete topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'instance': { 'comment_count': 0,
                         'pk': 3,
                         'post_type': 'answer',
                         'summary': 'I think I know... totally.    asldkj for sure.\n ...',
                         'text': 'I think I know... totally.    asldkj for sure.',
                         'vote_down_count': 0,
                         'vote_up_count': 1},
           'thread': { 'pk': 2,
                       'tagnames': ['town', 'ohok'],
                       'title': 'alskdjflaksjdf lakjsf a'},
           'topmost_post_id': 2},
  'timestamp': 1359947128.523792,
  'topic': 'org.fedoraproject.prod.askbot.post.flag_offensive.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.post.flag_offensive.delete
fedmsg.meta.msg2subtitle() ralph unflagged an answer as offensive…
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘threads/2’, ‘tags/ohok’, ‘tags/town’])
fedmsg.meta.msg2icon() 6c3d1a16-f11b-452e-97f1-f84523edef9c-icon
fedmsg.meta.msg2secondary_icon() 6c3d1a16-f11b-452e-97f1-f84523edef9c-secondary_icon

askbot.tag.update

Messages get emitted on this topic when a question on Ask Fedora changes tags. It includes information about what tags the package now has, what question the tags are for, and who did the changing. The msg['msg']['tags'] field describes which tags changed while the msg['msg']['thread']['tagnames'] field describes all tags on the thread in question.

You can view the history of messages with the askbot.tag.update topic or all askbot messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'tags': ['asldkjfalskdjfalskj', 'asldkjf', 'asldkjfalskdjf'],
           'thread': { 'pk': 2,
                       'tagnames': [ 'town',
                                     'ohok',
                                     'asldkjfalskdjfalskj',
                                     'asldkjf'],
                       'title': 'some title'},
           'timestamp': 1359945296.0,
           'topmost_post_id': 2},
  'timestamp': 1359945296.629136,
  'topic': 'org.fedoraproject.prod.askbot.tag.update',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() askbot.tag.update
fedmsg.meta.msg2subtitle() ralph altered tags on askbot question ‘some title’
fedmsg.meta.msg2link() https://ask.fedoraproject.org/question/2/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘tags/asldkjfalskdjfalskj’, ‘tags/asldkjfalskdjf’, ‘tags/asldkjf’, ‘threads/2’])
fedmsg.meta.msg2icon() d5615fb3-16aa-44b3-9e77-9faa1e701936-icon
fedmsg.meta.msg2secondary_icon() d5615fb3-16aa-44b3-9e77-9faa1e701936-secondary_icon

autocloud

autocloud.compose.complete

These messages are published when tests for a compose completes in Autocloud app.

You can view the history of messages with the autocloud.compose.complete topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_job_id': 37,
            u'date': u'20160419',
            u'id': u'Fedora-24-20160419.n.1',
            u'release': u'24',
            u'respin': 1,
            u'results': { u'failed': 0, u'success': 6},
            u'status': u'completed',
            u'type': u'nightly'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.compose.complete',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.compose.complete
fedmsg.meta.msg2subtitle() Fedora-24-20160419.n.1 tests have completed
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/37
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/compose/completed’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 6e82710c-d9b1-4eb9-99b8-01cf714bbbc1-secondary_icon

autocloud.compose.queued

These messages are published when compose queued for testing in Autocloud app.

You can view the history of messages with the autocloud.compose.queued topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_job_id': 37,
            u'date': u'20160419',
            u'id': u'Fedora-24-20160419.n.1',
            u'release': u'24',
            u'respin': 1,
            u'status': u'queued',
            u'type': u'nightly'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.compose.queued',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.compose.queued
fedmsg.meta.msg2subtitle() Fedora-24-20160419.n.1 is queued for testing
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/37
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/compose/queued’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 136e51ce-a8b4-4271-9704-a02dd794b67e-secondary_icon

autocloud.compose.running

These messages are published when tests for a compose has started running in Autocloud app.

You can view the history of messages with the autocloud.compose.running topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_job_id': 37,
            u'date': u'20160419',
            u'id': u'Fedora-24-20160419.n.1',
            u'release': u'24',
            u'respin': 1,
            u'status': u'running',
            u'type': u'nightly'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.compose.running',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.compose.running
fedmsg.meta.msg2subtitle() Fedora-24-20160419.n.1 tests have started running
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/37
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/compose/running’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 5df15c12-9a98-47ff-8d1b-7544f8bdb639-secondary_icon

autocloud.image.aborted

These messages are published when tests for an image aborts in Autocloud app.

You can view the history of messages with the autocloud.image.aborted topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_id': u'Fedora-24-20160420.n.0',
            u'compose_url': u'http://kojipkgs.fedoraproject.org/compose//" +             "branched/Fedora-24-20160420.n.0/compose/CloudImages/x86_64/" +             "images/Fedora-Cloud-Base-24-20160420.n.0.x86_64.qcow2',
            u'family': u'Base',
            u'image_name': u'Fedora-Cloud-Base-24-20160420.n.0',
            u'job_id': 27,
            u'release': u'24',
            u'status': u'aborted',
            u'type': u'qcow2'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.image.aborted',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.image.aborted
fedmsg.meta.msg2subtitle() The tests for the Fedora-Cloud-Base-24-20160420.n.0 (24)(Fedora-24-20160420.n.0) have been aborted
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/27/output
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/image/aborted’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 3e6e4433-637c-42e4-a8ab-ee665739fc0c-secondary_icon

autocloud.image.failed

These messages are published when tests for an image failed in Autocloud app.

You can view the history of messages with the autocloud.image.failed topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_id': u'Fedora-24-20160420.n.0',
            u'compose_url': u'http://kojipkgs.fedoraproject.org/compose//" +             "branched/Fedora-24-20160420.n.0/compose/CloudImages/x86_64/" +             "images/Fedora-Cloud-Base-24-20160420.n.0.x86_64.qcow2',
            u'family': u'Base',
            u'image_name': u'Fedora-Cloud-Base-24-20160420.n.0',
            u'job_id': 27,
            u'release': u'24',
            u'status': u'failed',
            u'type': u'qcow2'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.image.failed',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.image.failed
fedmsg.meta.msg2subtitle() The tests for the Fedora-Cloud-Base-24-20160420.n.0 (24)(Fedora-24-20160420.n.0) failed
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/27/output
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/image/failed’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 55e05839-d4e0-48b6-9694-810b23e0cfe3-secondary_icon

autocloud.image.queued

These messages are published when an image is queued for testing in Autocloud app.

You can view the history of messages with the autocloud.image.queued topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_id': u'Fedora-24-20160420.n.0',
            u'compose_url': u'http://kojipkgs.fedoraproject.org/compose//" +             "branched/Fedora-24-20160420.n.0/compose/CloudImages/x86_64/" +             "images/Fedora-Cloud-Base-24-20160420.n.0.x86_64.qcow2',
            u'family': u'Base',
            u'image_name': u'Fedora-Cloud-Base-24-20160420.n.0',
            u'job_id': 27,
            u'release': u'24',
            u'status': u'queued',
            u'type': u'qcow2'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.image.queued',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.image.queued
fedmsg.meta.msg2subtitle() Fedora-Cloud-Base-24-20160420.n.0 (24)(Fedora-24-20160420.n.0) is queued for testing
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/27/output
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/image/queued’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 7ab49a46-13d7-4cf0-829d-764cd07ca49f-secondary_icon

autocloud.image.running

These messages are published when tests for an image starts in Autocloud app.

You can view the history of messages with the autocloud.image.running topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_id': u'Fedora-24-20160420.n.0',
            u'compose_url': u'http://kojipkgs.fedoraproject.org/compose//" +             "branched/Fedora-24-20160420.n.0/compose/CloudImages/x86_64/" +             "images/Fedora-Cloud-Base-24-20160420.n.0.x86_64.qcow2',
            u'family': u'Base',
            u'image_name': u'Fedora-Cloud-Base-24-20160420.n.0',
            u'job_id': 27,
            u'release': u'24',
            u'status': u'running',
            u'type': u'qcow2'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.image.running',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.image.running
fedmsg.meta.msg2subtitle() The tests for the Fedora-Cloud-Base-24-20160420.n.0 (24)(Fedora-24-20160420.n.0) have started running
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/27/output
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/image/running’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 412296e0-cb45-42b1-b5ca-aa7b0816b58b-secondary_icon

autocloud.image.success

These messages are published when tests for an image successfully completes in Autocloud app.

You can view the history of messages with the autocloud.image.success topic or all autocloud messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose_id': u'Fedora-24-20160420.n.0',
            u'compose_url': u'http://kojipkgs.fedoraproject.org/compose//" +             "branched/Fedora-24-20160420.n.0/compose/CloudImages/x86_64/" +             "images/Fedora-Cloud-Base-24-20160420.n.0.x86_64.qcow2',
            u'family': u'Base',
            u'image_name': u'Fedora-Cloud-Base-24-20160420.n.0',
            u'job_id': 27,
            u'release': u'24',
            u'status': u'success',
            u'type': u'qcow2'},
  u'msg_id': u'2015-4b5aae66-b713-4c22-bb4a-1277d4402375',
  u'timestamp': 1379638157.759283,
  u'topic': u'org.fedoraproject.prod.autocloud.image.success',
  u'username': u'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() autocloud.image.success
fedmsg.meta.msg2subtitle() The tests for Fedora-Cloud-Base-24-20160420.n.0 (24)(Fedora-24-20160420.n.0) were a success
fedmsg.meta.msg2link() https://apps.fedoraproject.org/autocloud/jobs/27/output
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘autocloud/image/success’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() f2a3d07a-7d78-45a4-9177-421d8966c401-secondary_icon

bodhi

bodhi.buildroot_override.tag

The Bodhi Updates System publishes messages on this topic whenever a user requests a buildroot override for an update.

You can view the history of messages with the bodhi.buildroot_override.tag topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'override': { 'build': { 'nvr': 'fedmsg-1.0-1', 'override': 1},
                         'submitter': { 'name': 'lmacken'}}},
  'timestamp': 1344344053.23372,
  'topic': 'org.fedoraproject.prod.bodhi.buildroot_override.tag'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.buildroot_override.tag
fedmsg.meta.msg2subtitle() lmacken submitted a buildroot override for fedmsg-1.0-1
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/overrides/fedmsg-1.0-1
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘fedmsg’])
fedmsg.meta.msg2objects() set([‘packages/fedmsg’])
fedmsg.meta.msg2icon() a47aa8a2-a799-4d82-bd02-a07146781526-icon
fedmsg.meta.msg2secondary_icon() a47aa8a2-a799-4d82-bd02-a07146781526-secondary_icon

bodhi.buildroot_override.untag

The Bodhi Updates System publishes messages on this topic whenever a user explicitly removes a previously requested buildroot override.

You can view the history of messages with the bodhi.buildroot_override.untag topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'override': { 'build': { 'nvr': 'fedmsg-1.0-1', 'override': 1},
                         'submitter': { 'name': 'lmacken'}}},
  'timestamp': 1344964395.207541,
  'topic': 'org.fedoraproject.prod.bodhi.buildroot_override.untag'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.buildroot_override.untag
fedmsg.meta.msg2subtitle() lmacken expired a buildroot override for fedmsg-1.0-1
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/overrides/fedmsg-1.0-1
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘fedmsg’])
fedmsg.meta.msg2objects() set([‘packages/fedmsg’])
fedmsg.meta.msg2icon() bc7e9c79-08f6-4363-9a88-174abf4968da-icon
fedmsg.meta.msg2secondary_icon() bc7e9c79-08f6-4363-9a88-174abf4968da-secondary_icon

bodhi.errata.publish

Bodhi2, along with many other services, moved away from sending its own email notifications to instead publish fedmsg messages that the FMN system would be responsible for forwarding.

This message type comes from that move. It represents the “errata” for a package when it it mashed into a repository.

You can view the history of messages with the bodhi.errata.publish topic or all bodhi messages in datagrepper.

{ 'i': 2,
  'msg': { 'body': 'This is the body of the errata email',
           'subject': 'This is the subject of the errata email',
           'update': { 'alias': None,
                       'bugs': [],
                       'builds': [ { 'nvr': 'tzdata-2014i-1.fc19',
                                     'override': None}],
                       'close_bugs': True,
                       'comments': [ { 'anonymous': False,
                                       'bug_feedback': [],
                                       'id': 484236,
                                       'karma': 0,
                                       'karma_critpath': 0,
                                       'testcase_feedback': [],
                                       'text': 'ralph edited this update. ',
                                       'timestamp': '2015-01-28 03:02:44',
                                       'update': 54046,
                                       'update_id': 54046,
                                       'user': { 'avatar': None,
                                                 'buildroot_overrides': [ ],
                                                 'name': 'bodhi',
                                                 'stacks': []},
                                       'user_id': 1681}],
                       'critpath': False,
                       'cves': [],
                       'date_approved': None,
                       'date_modified': '2015-01-28 03:02:55',
                       'date_pushed': None,
                       'date_submitted': '2014-10-29 20:02:57',
                       'karma': 0,
                       'locked': False,
                       'notes': 'the update notes go here...',
                       'old_updateid': None,
                       'pushed': False,
                       'release': { 'branch': None,
                                    'candidate_tag': 'f19-updates-candidate',
                                    'dist_tag': 'f19',
                                    'id_prefix': 'FEDORA',
                                    'long_name': 'Fedora 19',
                                    'name': 'F19',
                                    'override_tag': 'f19-override',
                                    'pending_stable_tag': 'f19-updates-pending',
                                    'pending_testing_tag': 'f19-updates-testing-pending',
                                    'stable_tag': 'f19-updates',
                                    'state': 'disabled',
                                    'testing_tag': 'f19-updates-testing',
                                    'version': None},
                       'request': 'testing',
                       'require_bugs': True,
                       'require_testcases': True,
                       'requirements': 'rpmlint',
                       'severity': 'unspecified',
                       'stable_karma': 3,
                       'status': 'pending',
                       'suggest': 'unspecified',
                       'title': 'tzdata-2014i-1.fc19',
                       'type': 'enhancement',
                       'unstable_karma': -3,
                       'user': { 'avatar': None,
                                 'buildroot_overrides': [],
                                 'name': 'ralph',
                                 'stacks': [ { 'description': 'This stack is so hack!',
                                               'groups': [],
                                               'name': 'Hackey',
                                               'packages': [],
                                               'requirements': 'depcheck upgradepath',
                                               'users': [1711]}]}}},
  'msg_id': '2015-21b9ae33-3fdf-42ab-aecb-5717d0d76018',
  'timestamp': 1422302779,
  'topic': 'org.fedoraproject.prod.bodhi.errata.publish',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.errata.publish
fedmsg.meta.msg2subtitle() This is the subject of the errata email
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/tzdata-2014i-1.fc19
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘tzdata’])
fedmsg.meta.msg2objects() set([‘packages/tzdata’])
fedmsg.meta.msg2icon() 7ad4c1cb-994f-4554-a537-4162e2ae893f-icon
fedmsg.meta.msg2secondary_icon() 7ad4c1cb-994f-4554-a537-4162e2ae893f-secondary_icon

bodhi.masher.start

This message is published by an admin when they send a request to the Bodhi2 backend, telling it to start a mash.

You can view the history of messages with the bodhi.masher.start topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'updates': [ 'qt-creator-3.4.1-3.fc23',
                        'rakudo-star-0.0.2015.06-1.fc21',
                        'rakudo-star-0.0.2015.06-1.fc22',
                        'nqp-0.0.2015.06-1.fc21',
                        'nqp-0.0.2015.06-1.fc22',
                        'moarvm-0.2015.06-1.fc21',
                        'moarvm-0.2015.06-1.fc22',
                        'libetonyek-0.1.3-1.fc22',
                        'bind-9.10.2-2.P1.fc22,bind-dyndb-ldap-7.0-5.fc22,dnsperf-2.0.0.0-16.fc22',
                        'gap-pkg-autodoc-2015.04.29-2.fc22',
                        'hawaii-widget-styles-0.5.0-1.fc21',
                        'php-pear-PHP-CodeSniffer-2.3.3-1.fc21',
                        'php-pear-PHP-CodeSniffer-2.3.3-1.fc22',
                        'hawaii-widget-styles-0.5.0-1.fc22',
                        'MySQL-python-1.3.6-3.fc22',
                        'xdg-app-0.3.5-1.fc21',
                        'linux-firmware-20150521-53.git3161bfa4.fc22,ivtv-firmware-20080701-28',
                        'xdg-app-0.3.5-1.fc22',
                        'selinux-policy-3.13.1-105.18.fc21',
                        'dnf-plugins-core-0.1.9-1.fc22']},
  'msg_id': '2015-d370d1cd-4015-4c30-a249-792605db003f',
  'timestamp': 1439929069,
  'topic': 'org.fedoraproject.prod.bodhi.masher.start',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.masher.start
fedmsg.meta.msg2subtitle() ralph requested a mash of 20 updates
fedmsg.meta.msg2link() None
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘gap-pkg-autodoc’, ‘nqp’, ‘dnf-plugins-core’, ‘hawaii-widget-styles’, ‘bind’, ‘libetonyek’, ‘xdg-app’, ‘ivtv-firmware’, ‘qt-creator’, ‘php-pear-PHP-CodeSniffer’, ‘linux-firmware’, ‘MySQL-python’, ‘bind-dyndb-ldap’, ‘selinux-policy’, ‘moarvm’, ‘rakudo-star’, ‘dnsperf’])
fedmsg.meta.msg2objects() set([‘packages/gap-pkg-autodoc’, ‘packages/php-pear-PHP-CodeSniffer’, ‘packages/nqp’, ‘packages/MySQL-python’, ‘packages/rakudo-star’, ‘packages/hawaii-widget-styles’, ‘packages/moarvm’, ‘packages/selinux-policy’, ‘packages/libetonyek’, ‘packages/dnsperf’, ‘packages/linux-firmware’, ‘packages/bind’, ‘packages/ivtv-firmware’, ‘packages/dnf-plugins-core’, ‘packages/xdg-app’, ‘packages/qt-creator’, ‘packages/bind-dyndb-ldap’])
fedmsg.meta.msg2icon() 8aedb373-3731-492e-80ea-1a37ef55efee-icon
fedmsg.meta.msg2secondary_icon() 8aedb373-3731-492e-80ea-1a37ef55efee-secondary_icon

bodhi.mashtask.complete

The Bodhi Masher publishes messages on this topic whenever it finishes its work.

Note that, these messages are broken (serverside) due to this issue.

You can view the history of messages with the bodhi.mashtask.complete topic or all bodhi messages in datagrepper.

{ 'msg': { 'repo': 'test_repo', 'success': False},
  'topic': 'org.fedoraproject.prod.bodhi.mashtask.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.mashtask.complete
fedmsg.meta.msg2subtitle() bodhi masher failed to mash test_repo
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() Unspecified
fedmsg.meta.msg2icon() a97ec1d9-7358-42df-9bdc-46c8016ab43d-icon
fedmsg.meta.msg2secondary_icon() a97ec1d9-7358-42df-9bdc-46c8016ab43d-secondary_icon

bodhi.mashtask.mashing

The Bodhi Masher publishes messages on this topic whenever it starts mashing a particular repository.

Note that, these messages are broken (serverside) due to this issue.

You can view the history of messages with the bodhi.mashtask.mashing topic or all bodhi messages in datagrepper.

{ 'msg': { 'repo': 'test_repo', 'updates': []},
  'topic': 'org.fedoraproject.prod.bodhi.mashtask.mashing'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.mashtask.mashing
fedmsg.meta.msg2subtitle() bodhi masher started mashing test_repo
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘repos/test_repo’])
fedmsg.meta.msg2icon() 3d9647ef-18f6-4605-9f12-22b03b50c3ec-icon
fedmsg.meta.msg2secondary_icon() 3d9647ef-18f6-4605-9f12-22b03b50c3ec-secondary_icon

bodhi.mashtask.start

The Bodhi Masher publishes messages on this topic whenever it begins its work.

Note that, these messages are broken (serverside) due to this issue.

You can view the history of messages with the bodhi.mashtask.start topic or all bodhi messages in datagrepper.

{ 'msg': { }, 'topic': 'org.fedoraproject.prod.bodhi.mashtask.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.mashtask.start
fedmsg.meta.msg2subtitle() bodhi masher started a push
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() Unspecified
fedmsg.meta.msg2icon() 3a5cea8a-c276-420d-9417-42ff89a9811b-icon
fedmsg.meta.msg2secondary_icon() 3a5cea8a-c276-420d-9417-42ff89a9811b-secondary_icon

bodhi.mashtask.sync.done

The Bodhi Masher publishes messages on this topic when it finishes syncing.

Note that, these messages are broken (serverside) due to this issue.

You can view the history of messages with the bodhi.mashtask.sync.done topic or all bodhi messages in datagrepper.

{ 'msg': { 'repo': 'test_repo'},
  'topic': 'org.fedoraproject.prod.bodhi.mashtask.sync.done'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.mashtask.sync.done
fedmsg.meta.msg2subtitle() bodhi masher finished waiting for test_repo to hit the master mirror
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() Unspecified
fedmsg.meta.msg2icon() 2e903ba2-abe7-4223-aede-fdd5595a13ff-icon
fedmsg.meta.msg2secondary_icon() 2e903ba2-abe7-4223-aede-fdd5595a13ff-secondary_icon

bodhi.mashtask.sync.wait

The Bodhi Masher publishes messages on this topic when it begins waiting to sync.

Note that, these messages are broken (serverside) due to this issue.

You can view the history of messages with the bodhi.mashtask.sync.wait topic or all bodhi messages in datagrepper.

{ 'msg': { 'repo': 'test_repo'},
  'topic': 'org.fedoraproject.prod.bodhi.mashtask.sync.wait'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.mashtask.sync.wait
fedmsg.meta.msg2subtitle() bodhi masher is waiting for test_repo to hit the master mirror
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() Unspecified
fedmsg.meta.msg2icon() c87497be-b26f-4f93-8b0b-5bfd165360ca-icon
fedmsg.meta.msg2secondary_icon() c87497be-b26f-4f93-8b0b-5bfd165360ca-secondary_icon

bodhi.stack.delete

Bodhi2 introduced the concept of stacks of packages that can be grouped for to share requirements. That system publishes messages like this anytime a user deletes a stack.

You can view the history of messages with the bodhi.stack.delete topic or all bodhi messages in datagrepper.

{ 'i': 2,
  'msg': { 'agent': 'ralph',
           'stack': { 'description': 'the greatest game you will ever play',
                      'groups': [],
                      'name': 'hacking',
                      'packages': [ { 'builds': [],
                                      'committers': [],
                                      'name': 'nethack',
                                      'requirements': 'depcheck upgradepath',
                                      'stack': 9,
                                      'stack_id': 9,
                                      'test_cases': []}],
                      'requirements': 'depcheck upgradepath',
                      'users': [ { 'avatar': None,
                                   'buildroot_overrides': [],
                                   'name': 'ralph',
                                   'stacks': [1, 8, 9]}]}},
  'msg_id': '2015-21b9ae33-3fdf-42ab-aecb-5717d0d76018',
  'timestamp': 1422302779,
  'topic': 'org.fedoraproject.prod.bodhi.stack.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.stack.delete
fedmsg.meta.msg2subtitle() ralph deleted the “hacking” stack
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/stacks/hacking
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘nethack’])
fedmsg.meta.msg2objects() set([‘packages/nethack’, ‘stacks/hacking’])
fedmsg.meta.msg2icon() eb6ba4a5-32ad-4771-8a1f-a6efb25ba14c-icon
fedmsg.meta.msg2secondary_icon() eb6ba4a5-32ad-4771-8a1f-a6efb25ba14c-secondary_icon

bodhi.stack.save

Bodhi2 introduced the concept of stacks of packages that can be grouped for to share requirements. That system publishes messages like this anytime a user modifies or creates a new stack.

You can view the history of messages with the bodhi.stack.save topic or all bodhi messages in datagrepper.

{ 'i': 2,
  'msg': { 'agent': 'ralph',
           'stack': { 'description': 'the greatest game you will ever play',
                      'groups': [],
                      'name': 'hacking',
                      'packages': [ { 'builds': [],
                                      'committers': [],
                                      'name': 'nethack',
                                      'requirements': 'depcheck upgradepath',
                                      'stack': 9,
                                      'stack_id': 9,
                                      'test_cases': []}],
                      'requirements': 'depcheck upgradepath',
                      'users': [ { 'avatar': None,
                                   'buildroot_overrides': [],
                                   'name': 'ralph',
                                   'stacks': [1, 8, 9]}]}},
  'msg_id': '2015-21b9ae33-3fdf-42ab-aecb-5717d0d76018',
  'timestamp': 1422302779,
  'topic': 'org.fedoraproject.prod.bodhi.stack.save',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.stack.save
fedmsg.meta.msg2subtitle() ralph updated the “hacking” stack
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/stacks/hacking
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘nethack’])
fedmsg.meta.msg2objects() set([‘packages/nethack’, ‘stacks/hacking’])
fedmsg.meta.msg2icon() 157591d2-e5c5-4ccc-9e9a-eee4192f905a-icon
fedmsg.meta.msg2secondary_icon() 157591d2-e5c5-4ccc-9e9a-eee4192f905a-secondary_icon

bodhi.update.comment

The Bodhi Updates System publishes messages on this topic whenever a user comments on a bodhi update.

You can view the history of messages with the bodhi.update.comment topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'comment': { 'anonymous': False,
                        'author': 'ralph',
                        'group': None,
                        'karma': -1,
                        'text': "Can you believe how much testing we're doing? /cc @codeblock.",
                        'timestamp': 1344344050.0,
                        'update_title': 'fedmsg-1.0-1'}},
  'timestamp': 1344344053.23372,
  'topic': 'org.fedoraproject.prod.bodhi.update.comment'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.comment
fedmsg.meta.msg2subtitle() ralph commented on bodhi update fedmsg-1.0-1 (karma: -1)
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/fedmsg-1.0-1
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’, ‘codeblock’])
fedmsg.meta.msg2packages() set([‘fedmsg’])
fedmsg.meta.msg2objects() set([‘packages/fedmsg’])
fedmsg.meta.msg2icon() c2e6af53-60a0-4bdf-9eca-8a2b0fae0e72-icon
fedmsg.meta.msg2secondary_icon() c2e6af53-60a0-4bdf-9eca-8a2b0fae0e72-secondary_icon

bodhi.update.complete.testing

The Bodhi Updates System publishes messages on this topic whenever an update completes it’s push to the testing repository. Here’s a straightforward example:

You can view the history of messages with the bodhi.update.complete.testing topic or all bodhi messages in datagrepper.

{ 'i': 88,
  'msg': { 'update': { 'status': 'testing',
                       'submitter': { 'name': 'ralph'},
                       'title': 'fedmsg-0.2.7-2.el6'}},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.bodhi.update.complete.testing'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.complete.testing
fedmsg.meta.msg2subtitle() ralph’s fedmsg-0.2.7-2.el6 bodhi update completed push to testing
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/fedmsg-0.2.7-2.el6
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘fedmsg’])
fedmsg.meta.msg2objects() set([‘packages/fedmsg’])
fedmsg.meta.msg2icon() b0695dd9-0525-43ad-b473-17d41c32430f-icon
fedmsg.meta.msg2secondary_icon() b0695dd9-0525-43ad-b473-17d41c32430f-secondary_icon

bodhi.update.edit

Bodhi2 publishes this kind of message when a package maintainer edits a pre-existing update.

You can view the history of messages with the bodhi.update.edit topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'ralph',
           'update': { 'alias': None,
                       'bugs': [],
                       'builds': [ { 'nvr': 'tzdata-2014i-1.fc19',
                                     'override': None}],
                       'close_bugs': True,
                       'comments': [ { 'anonymous': False,
                                       'bug_feedback': [],
                                       'id': 484236,
                                       'karma': 0,
                                       'karma_critpath': 0,
                                       'testcase_feedback': [],
                                       'text': 'ralph edited this update. ',
                                       'timestamp': '2015-01-28 03:02:44',
                                       'update': 54046,
                                       'update_id': 54046,
                                       'user': { 'avatar': None,
                                                 'buildroot_overrides': [ ],
                                                 'name': 'bodhi',
                                                 'stacks': []},
                                       'user_id': 1681}],
                       'critpath': False,
                       'cves': [],
                       'date_approved': None,
                       'date_modified': '2015-01-28 03:02:55',
                       'date_pushed': None,
                       'date_submitted': '2014-10-29 20:02:57',
                       'karma': 0,
                       'locked': False,
                       'notes': 'the update notes go here...',
                       'old_updateid': None,
                       'pushed': False,
                       'release': { 'branch': None,
                                    'candidate_tag': 'f19-updates-candidate',
                                    'dist_tag': 'f19',
                                    'id_prefix': 'FEDORA',
                                    'long_name': 'Fedora 19',
                                    'name': 'F19',
                                    'override_tag': 'f19-override',
                                    'pending_stable_tag': 'f19-updates-pending',
                                    'pending_testing_tag': 'f19-updates-testing-pending',
                                    'stable_tag': 'f19-updates',
                                    'state': 'disabled',
                                    'testing_tag': 'f19-updates-testing',
                                    'version': None},
                       'request': 'testing',
                       'require_bugs': True,
                       'require_testcases': True,
                       'requirements': 'rpmlint',
                       'severity': 'unspecified',
                       'stable_karma': 3,
                       'status': 'pending',
                       'suggest': 'unspecified',
                       'title': 'tzdata-2014i-1.fc19',
                       'type': 'enhancement',
                       'unstable_karma': -3,
                       'user': { 'avatar': None,
                                 'buildroot_overrides': [],
                                 'name': 'ralph',
                                 'stacks': [ { 'description': 'This stack is so hack!',
                                               'groups': [],
                                               'name': 'Hackey',
                                               'packages': [],
                                               'requirements': 'depcheck upgradepath',
                                               'users': [1711]}]}}},
  'msg_id': '2015-2b398e44-8012-455f-bfeb-195b9dda18f6',
  'timestamp': 1422414175,
  'topic': 'org.fedoraproject.prod.bodhi.update.edit',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.edit
fedmsg.meta.msg2subtitle() ralph edited tzdata-2014i-1.fc19
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/tzdata-2014i-1.fc19
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘tzdata’])
fedmsg.meta.msg2objects() set([‘packages/tzdata’])
fedmsg.meta.msg2icon() 79311602-cdaa-4d2d-b48d-2038a0788ab8-icon
fedmsg.meta.msg2secondary_icon() 79311602-cdaa-4d2d-b48d-2038a0788ab8-secondary_icon

bodhi.update.eject

The Bodhi Updates System publishes messages on this topic whenever an update is ejected from the mash due to some failure:

You can view the history of messages with the bodhi.update.eject topic or all bodhi messages in datagrepper.

{ 'i': 88,
  'msg': { 'reason': 'some reason',
           'release': { 'dist_tag': 'el6',
                        'locked': True,
                        'long_name': 'Fedora EPEL 6',
                        'name': 'EL6'},
           'repo': 'test_repo',
           'request': 'testing',
           'update': { 'status': 'testing',
                       'submitter': { 'name': 'ralph'},
                       'title': 'fedmsg-0.2.7-2.el6'}},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.bodhi.update.eject'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.eject
fedmsg.meta.msg2subtitle() ralph’s fedmsg-0.2.7-2.el6 bodhi update was ejected from the test_repo mash. Reason: “some reason”
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/fedmsg-0.2.7-2.el6
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘fedmsg’])
fedmsg.meta.msg2objects() set([‘packages/fedmsg’])
fedmsg.meta.msg2icon() 62952fc2-ca08-4915-98f0-f48d0107b54b-icon
fedmsg.meta.msg2secondary_icon() 62952fc2-ca08-4915-98f0-f48d0107b54b-secondary_icon

bodhi.update.karma.threshold

Bodhi2 publishes these messages when an update reaches the stable or unstable karma thresholds.

You can view the history of messages with the bodhi.update.karma.threshold topic or all bodhi messages in datagrepper.

{ 'i': 2,
  'msg': { 'status': 'stable',
           'update': { 'alias': 'FEDORA-EPEL-2015-0238',
                       'bugs': [],
                       'builds': [ { 'nvr': 'tzdata-2014i-1.fc19',
                                     'override': None}],
                       'close_bugs': True,
                       'comments': [ { 'anonymous': False,
                                       'bug_feedback': [],
                                       'id': 484236,
                                       'karma': 0,
                                       'karma_critpath': 0,
                                       'testcase_feedback': [],
                                       'text': 'ralph edited this update. ',
                                       'timestamp': '2015-01-28 03:02:44',
                                       'update': 54046,
                                       'update_id': 54046,
                                       'user': { 'avatar': None,
                                                 'buildroot_overrides': [ ],
                                                 'name': 'bodhi',
                                                 'stacks': []},
                                       'user_id': 1681}],
                       'critpath': False,
                       'cves': [],
                       'date_approved': None,
                       'date_modified': '2015-01-28 03:02:55',
                       'date_pushed': None,
                       'date_submitted': '2014-10-29 20:02:57',
                       'karma': 0,
                       'locked': False,
                       'notes': 'the update notes go here...',
                       'old_updateid': None,
                       'pushed': False,
                       'release': { 'branch': None,
                                    'candidate_tag': 'f19-updates-candidate',
                                    'dist_tag': 'f19',
                                    'id_prefix': 'FEDORA',
                                    'long_name': 'Fedora 19',
                                    'name': 'F19',
                                    'override_tag': 'f19-override',
                                    'pending_stable_tag': 'f19-updates-pending',
                                    'pending_testing_tag': 'f19-updates-testing-pending',
                                    'stable_tag': 'f19-updates',
                                    'state': 'disabled',
                                    'testing_tag': 'f19-updates-testing',
                                    'version': None},
                       'request': 'testing',
                       'require_bugs': True,
                       'require_testcases': True,
                       'requirements': 'rpmlint',
                       'severity': 'unspecified',
                       'stable_karma': 3,
                       'status': 'pending',
                       'suggest': 'unspecified',
                       'title': 'tzdata-2014i-1.fc19',
                       'type': 'enhancement',
                       'unstable_karma': -3,
                       'user': { 'avatar': None,
                                 'buildroot_overrides': [],
                                 'name': 'ralph',
                                 'stacks': [ { 'description': 'This stack is so hack!',
                                               'groups': [],
                                               'name': 'Hackey',
                                               'packages': [],
                                               'requirements': 'depcheck upgradepath',
                                               'users': [1711]}]}}},
  'msg_id': '2015-21b9ae33-3fdf-42ab-aecb-5717d0d76018',
  'timestamp': 1422302779,
  'topic': 'org.fedoraproject.prod.bodhi.update.karma.threshold',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.karma.threshold
fedmsg.meta.msg2subtitle() tzdata-2014i-1.fc19 reached the stable karma threshold
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-0238
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘tzdata’])
fedmsg.meta.msg2objects() set([‘packages/tzdata’])
fedmsg.meta.msg2icon() 65ebb5b2-30bd-4246-825f-0227d1e7dd4f-icon
fedmsg.meta.msg2secondary_icon() 65ebb5b2-30bd-4246-825f-0227d1e7dd4f-secondary_icon

bodhi.update.request.obsolete

The Bodhi Updates System publishes messages on this topic whenever a user requests that an update be obsoleted.

You can view the history of messages with the bodhi.update.request.obsolete topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'lmacken',
           'update': { 'submitter': 'lmacken', 'title': 'foo'}},
  'topic': 'org.fedoraproject.prod.bodhi.update.request.obsolete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.obsolete
fedmsg.meta.msg2subtitle() lmacken obsoleted foo
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/foo
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘foo’])
fedmsg.meta.msg2objects() set([‘packages/foo’])
fedmsg.meta.msg2icon() f7444cc7-f215-47fd-8ba5-99c346403947-icon
fedmsg.meta.msg2secondary_icon() f7444cc7-f215-47fd-8ba5-99c346403947-secondary_icon

bodhi.update.request.revoke

The Bodhi Updates System publishes messages on this topic whenever a user revokes a prior request on an update.

You can view the history of messages with the bodhi.update.request.revoke topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'lmacken',
           'update': { 'submitter': 'lmacken', 'title': 'foo'}},
  'topic': 'org.fedoraproject.prod.bodhi.update.request.revoke'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.revoke
fedmsg.meta.msg2subtitle() lmacken revoked foo
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/foo
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘foo’])
fedmsg.meta.msg2objects() set([‘packages/foo’])
fedmsg.meta.msg2icon() 4a5c5a40-ec81-4f37-8134-ac09192015e3-icon
fedmsg.meta.msg2secondary_icon() 4a5c5a40-ec81-4f37-8134-ac09192015e3-secondary_icon

bodhi.update.request.stable

The Bodhi Updates System publishes messages on this topic whenever a user requests that an update be marked as stable.

You can view the history of messages with the bodhi.update.request.stable topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'lmacken',
           'update': { 'submitter': 'lmacken', 'title': 'foo'}},
  'topic': 'org.fedoraproject.prod.bodhi.update.request.stable'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.stable
fedmsg.meta.msg2subtitle() lmacken submitted foo to stable
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/foo
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘foo’])
fedmsg.meta.msg2objects() set([‘packages/foo’])
fedmsg.meta.msg2icon() 7fffddcd-20a1-4bda-a8d6-d9d2c628254b-icon
fedmsg.meta.msg2secondary_icon() 7fffddcd-20a1-4bda-a8d6-d9d2c628254b-secondary_icon

bodhi.update.request.testing

The Bodhi Updates System publishes messages on this topic whenever a user requests that an update be pushed to the testing repository. Some updates may contain multiple packages, which can be a little tricky if you’re not ready for it. Here’s an example of that:

You can view the history of messages with the bodhi.update.request.testing topic or all bodhi messages in datagrepper.

{ 'i': 2,
  'msg': { 'agent': 'lmacken',
           'update': { 'approved': None,
                       'bugs': [],
                       'builds': [ { 'nvr': 'gnome-settings-daemon-3.6.1-1.fc18',
                                     'package': { 'committers': [ 'hadess',
                                                                  'ofourdan',
                                                                  'mkasik',
                                                                  'cosimoc'],
                                                  'name': 'gnome-settings-daemon',
                                                  'suggest_reboot': False}},
                                   { 'nvr': 'control-center-3.6.1-1.fc18',
                                     'package': { 'committers': [ 'ctrl-center-team',
                                                                  'ofourdan',
                                                                  'ssp',
                                                                  'ajax',
                                                                  'alexl',
                                                                  'jrb',
                                                                  'mbarnes',
                                                                  'caolanm',
                                                                  'davidz',
                                                                  'mclasen',
                                                                  'rhughes',
                                                                  'hadess',
                                                                  'johnp',
                                                                  'caillon',
                                                                  'whot',
                                                                  'rstrode'],
                                                  'name': 'control-center',
                                                  'suggest_reboot': False}}],
                       'close_bugs': True,
                       'comments': [ { 'anonymous': False,
                                       'author': 'bodhi',
                                       'group': None,
                                       'karma': 0,
                                       'text': 'This update has been submitted for testing by hadess. ',
                                       'timestamp': 1349718539.0,
                                       'update_title': 'gnome-settings-daemon-3.6.1-1.fc18 control-center-3.6.1-1.fc18'}],
                       'critpath': False,
                       'critpath_approved': False,
                       'date_modified': None,
                       'date_pushed': None,
                       'date_submitted': 1349718534.0,
                       'karma': 0,
                       'nagged': None,
                       'notes': "This update fixes numerous bugs in the new Input Sources support, the Network panel and adds a help screen accessible via Wacom tablets's buttons.",
                       'release': { 'dist_tag': 'f18',
                                    'id_prefix': 'FEDORA',
                                    'locked': True,
                                    'long_name': 'Fedora 18',
                                    'name': 'F18'},
                       'request': 'testing',
                       'stable_karma': 3,
                       'status': 'pending',
                       'submitter': 'hadess',
                       'title': 'gnome-settings-daemon-3.6.1-1.fc18 control-center-3.6.1-1.fc18',
                       'type': 'bugfix',
                       'unstable_karma': -3,
                       'updateid': None}},
  'timestamp': 1349718539.0,
  'topic': 'org.fedoraproject.prod.bodhi.update.request.testing'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.testing
fedmsg.meta.msg2subtitle() lmacken submitted gnome-settings-daemon-3.6.1-1.fc18 contr… to testing
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/gnome-settings-daemon-3.6.1-1.fc18 control-center-3.6.1-1.fc18
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’, ‘hadess’])
fedmsg.meta.msg2packages() set([‘gnome-settings-daemon’, ‘control-center’])
fedmsg.meta.msg2objects() set([‘packages/gnome-settings-daemon’, ‘packages/control-center’])
fedmsg.meta.msg2icon() 23cc51e2-3621-40a1-958e-6472fe0e2c0d-icon
fedmsg.meta.msg2secondary_icon() 23cc51e2-3621-40a1-958e-6472fe0e2c0d-secondary_icon

bodhi.update.request.testing

The Bodhi Updates System publishes messages on this topic whenever a user requests that an update be pushed to the testing repository.

You can view the history of messages with the bodhi.update.request.testing topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'lmacken',
           'update': { 'submitter': 'lmacken', 'title': 'foo'}},
  'topic': 'org.fedoraproject.prod.bodhi.update.request.testing'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.testing
fedmsg.meta.msg2subtitle() lmacken submitted foo to testing
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/foo
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘foo’])
fedmsg.meta.msg2objects() set([‘packages/foo’])
fedmsg.meta.msg2icon() c2b4ce33-ce00-4335-800b-67e8b78d4432-icon
fedmsg.meta.msg2secondary_icon() c2b4ce33-ce00-4335-800b-67e8b78d4432-secondary_icon

bodhi.update.request.unpush

The Bodhi Updates System publishes messages on this topic whenever a user requests that an update be unpushed.

You can view the history of messages with the bodhi.update.request.unpush topic or all bodhi messages in datagrepper.

{ 'msg': { 'agent': 'lmacken',
           'update': { 'submitter': 'lmacken', 'title': 'foo'}},
  'topic': 'org.fedoraproject.prod.bodhi.update.request.unpush'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.request.unpush
fedmsg.meta.msg2subtitle() lmacken unpushed foo
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/foo
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘lmacken’])
fedmsg.meta.msg2packages() set([‘foo’])
fedmsg.meta.msg2objects() set([‘packages/foo’])
fedmsg.meta.msg2icon() 1b652bfa-bd0c-4e7b-9a77-0def3efa7214-icon
fedmsg.meta.msg2secondary_icon() 1b652bfa-bd0c-4e7b-9a77-0def3efa7214-secondary_icon

bodhi.update.requirements_met.stable

Bodhi2 publishes these messages when an update reaches the stable testing threshold.

You can view the history of messages with the bodhi.update.requirements_met.stable topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'update': { 'alias': 'FEDORA-2018-e1f68e9766',
                       'autokarma': True,
                       'bugs': [],
                       'builds': [ { 'ci_url': None,
                                     'epoch': 0,
                                     'nvr': 'python-josepy-1.1.0-1.fc28',
                                     'release_id': 21,
                                     'signed': True,
                                     'type': 'rpm'}],
                       'close_bugs': False,
                       'comments': [ { 'anonymous': False,
                                       'bug_feedback': [],
                                       'id': 771029,
                                       'karma': 0,
                                       'karma_critpath': 0,
                                       'testcase_feedback': [],
                                       'text': 'This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes',
                                       'timestamp': '2018-04-21 18:00:24',
                                       'update_id': 112982,
                                       'user': { 'avatar': None,
                                                 'email': None,
                                                 'groups': [],
                                                 'id': 91,
                                                 'name': 'bodhi',
                                                 'openid': None,
                                                 'show_popups': True},
                                       'user_id': 91}],
                       'compose': None,
                       'content_type': 'rpm',
                       'critpath': False,
                       'date_approved': None,
                       'date_modified': None,
                       'date_pushed': '2018-04-18 16:19:48',
                       'date_stable': None,
                       'date_submitted': '2018-04-17 18:20:04',
                       'date_testing': '2018-04-18 16:19:48',
                       'greenwave_summary_string': 'all required tests passed',
                       'karma': 0,
                       'locked': False,
                       'meets_testing_requirements': True,
                       'notes': 'Update to 1.1.0.',
                       'old_updateid': None,
                       'pushed': True,
                       'release': { 'branch': 'f28',
                                    'candidate_tag': 'f28-updates-candidate',
                                    'composes': [ { 'content_type': 'rpm',
                                                    'release_id': 21,
                                                    'request': 'testing',
                                                    'security': True}],
                                    'dist_tag': 'f28',
                                    'id_prefix': 'FEDORA',
                                    'long_name': 'Fedora 28',
                                    'name': 'F28',
                                    'override_tag': 'f28-override',
                                    'pending_signing_tag': 'f28-signing-pending',
                                    'pending_stable_tag': 'f28-updates-pending',
                                    'pending_testing_tag': 'f28-updates-testing-pending',
                                    'stable_tag': 'f28-updates',
                                    'state': 'current',
                                    'testing_tag': 'f28-updates-testing',
                                    'version': '28'},
                       'request': None,
                       'require_bugs': True,
                       'require_testcases': True,
                       'requirements': '',
                       'severity': 'unspecified',
                       'stable_karma': 1,
                       'status': 'testing',
                       'submitter': 'elyscape',
                       'suggest': 'unspecified',
                       'test_cases': [],
                       'test_gating_status': 'passed',
                       'title': 'python-josepy-1.1.0-1.fc28',
                       'type': 'enhancement',
                       'unstable_karma': -1,
                       'updateid': 'FEDORA-2018-e1f68e9766',
                       'url': 'https://bodhi.fedoraproject.org/updates/FEDORA-2018-e1f68e9766',
                       'user': { 'avatar': None,
                                 'groups': [{ 'name': 'packager'}],
                                 'id': 3225,
                                 'name': 'elyscape',
                                 'openid': None,
                                 'show_popups': True}}},
  'msg_id': '2018-a3a06a6c-77da-4093-aafe-1e96a26a74bc',
  'timestamp': 1524333630,
  'topic': 'org.fedoraproject.prod.bodhi.update.requirements_met.stable',
  'username': 'bodhi'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.update.requirements_met.stable
fedmsg.meta.msg2subtitle() python-josepy-1.1.0-1.fc28 reached the stable testing threshold
fedmsg.meta.msg2link() https://bodhi.fedoraproject.org/updates/FEDORA-2018-e1f68e9766
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘elyscape’])
fedmsg.meta.msg2packages() set([‘python-josepy’])
fedmsg.meta.msg2objects() set([‘packages/python-josepy’])
fedmsg.meta.msg2icon() 25770105-0f5c-440d-a73e-d64fe615aa15-icon
fedmsg.meta.msg2secondary_icon() 25770105-0f5c-440d-a73e-d64fe615aa15-secondary_icon

bodhi.updates.epel.sync

These messages are published when new updates (fresh out of the “mash” process) are synced out to the master mirror.

Here’s an example for the epel 6 testing repos:

You can view the history of messages with the bodhi.updates.epel.sync topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'bytes': '28493k',
           'deleted': '0',
           'release': '6',
           'repo': 'epel-testing'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.bodhi.updates.epel.sync'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.updates.epel.sync
fedmsg.meta.msg2subtitle() New EPEL 6 epel-testing content synced out (28493k changed with 0 files deleted)
fedmsg.meta.msg2link() https://download.fedoraproject.org/pub/epel/testing/6/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘epel/epel-testing/6’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

bodhi.updates.fedora.sync

These messages are published when a new compose of Fedora Atomic is synced out to the master mirror.

You can view the history of messages with the bodhi.updates.fedora.sync topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'bytes': '60.38M',
           'deleted': '0',
           'release': '21',
           'repo': 'atomic'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.bodhi.updates.fedora.sync'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.updates.fedora.sync
fedmsg.meta.msg2subtitle() New Fedora 21 atomic content synced out (60.38M changed with 0 files deleted)
fedmsg.meta.msg2link() https://download.fedoraproject.org/pub/fedora/linux/atomic/21/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘fedora/atomic/21’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

bodhi.updates.fedora.sync

These messages are published when new updates (fresh out of the “mash” process) are synced out to the master mirror.

Here’s an example for the fedora 20 stable repos:

You can view the history of messages with the bodhi.updates.fedora.sync topic or all bodhi messages in datagrepper.

{ 'i': 1,
  'msg': { 'bytes': '2.8M', 'deleted': '0', 'release': '20', 'repo': 'updates'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.bodhi.updates.fedora.sync'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bodhi.updates.fedora.sync
fedmsg.meta.msg2subtitle() New Fedora 20 updates content synced out (2.8M changed with 0 files deleted)
fedmsg.meta.msg2link() https://download.fedoraproject.org/pub/fedora/linux/updates/20/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘fedora/updates/20’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

bugzilla

bugzilla.bug.new

Even Red Hat’s Bugzilla instance is hooked into fedmsg.

Messages of this type are published whenever someone files a new bug on the Fedora or Fedora EPEL products.

Note that the event field is left empty ({}) for new bug events.

You can view the history of messages with the bugzilla.bug.new topic or all bugzilla messages in datagrepper.

{ 'i': 1,
  'msg': { 'bug': { 'actual_time': 0.0,
                    'alias': [],
                    'assigned_to': '',
                    'attachments': [],
                    'blocks': [],
                    'cc': [ 'package-review@lists.fedoraproject.org',
                            'puiterwijk@gmail.com'],
                    'classification': 'Fedora',
                    'comments': [ { 'author': 'puiterwijk@gmail.com',
                                    'bug_id': 968947,
                                    'count': 0,
                                    'creation_time': 1369924708.0,
                                    'creator': 'puiterwijk@gmail.com',
                                    'creator_id': 330125,
                                    'id': 5962818,
                                    'is_private': False,
                                    'text': '\nSpec URL: http://puiterwijk.fedorapeople..',
                                    'time': 1369924708.0}],
                    'component': 'Package Review',
                    'components': ['Package Review'],
                    'creation_time': 1369924680.0,
                    'creator': 'puiterwijk@gmail.com',
                    'depends_on': [],
                    'description': '\nSpec URL: http://puiterwijk.fedorapeople..',
                    'docs_contact': '',
                    'estimated_time': 0.0,
                    'external_bugs': [],
                    'fixed_in': '',
                    'flags': [ { 'creation_date': 1392337756.0,
                                 'id': 1703755,
                                 'is_active': 1,
                                 'modification_date': 1392337756.0,
                                 'name': 'needinfo',
                                 'requestee': 'puiterwijk@gmail.com',
                                 'setter': 'rbean@redhat.com',
                                 'status': '?',
                                 'type_id': 16}],
                    'groups': [],
                    'id': 968947,
                    'is_cc_accessible': True,
                    'is_confirmed': True,
                    'is_creator_accessible': True,
                    'is_open': True,
                    'keywords': [],
                    'last_change_time': 1392337756.0,
                    'op_sys': 'Unspecified',
                    'platform': 'Unspecified',
                    'priority': 'unspecified',
                    'product': 'Fedora',
                    'qa_contact': 'extras-qa@fedoraproject.org',
                    'remaining_time': 0.0,
                    'resolution': '',
                    'see_also': [],
                    'severity': 'unspecified',
                    'status': 'ASSIGNED',
                    'summary': 'Review Request: gallery3-openid - OpenID authentication for Gallery3',
                    'target_milestone': '---',
                    'target_release': ['---'],
                    'url': '',
                    'version': 'rawhide',
                    'versions': ['rawhide'],
                    'weburl': 'https://bugzilla.redhat.com/show_bug.cgi?id=968947',
                    'whiteboard': ''},
           'event': { }},
  'msg_id': '2014-0bc98222-a864-4aea-bc6b-e3b090d2cc3d',
  'timestamp': 1395760459,
  'topic': 'org.fedoraproject.prod.bugzilla.bug.new',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bugzilla.bug.new
fedmsg.meta.msg2subtitle() puiterwijk filed a new bug RHBZ#968947 ‘Review Request: gallery3-openid - OpenID…’
fedmsg.meta.msg2link() https://bugzilla.redhat.com/show_bug.cgi?id=968947
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘puiterwijk’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘Fedora/Package Review/968947’])
fedmsg.meta.msg2icon() 75a952aa-788d-422e-a7ae-9dcda03d76e5-icon
fedmsg.meta.msg2secondary_icon() 75a952aa-788d-422e-a7ae-9dcda03d76e5-secondary_icon

bugzilla.bug.update

Even Red Hat’s Bugzilla instance is hooked into fedmsg.

Messages of this type are published whenever someone updates a bug on the Fedora or Fedora EPEL products.

You can view the history of messages with the bugzilla.bug.update topic or all bugzilla messages in datagrepper.

{ 'i': 1,
  'msg': { 'bug': { 'actual_time': 0.0,
                    'alias': [],
                    'assigned_to': 'rbean@redhat.com',
                    'attachments': [],
                    'blocks': [],
                    'cc': [ 'package-review@lists.fedoraproject.org',
                            'puiterwijk@gmail.com',
                            'rbean@redhat.com'],
                    'classification': 'Fedora',
                    'comments': [ { 'author': 'puiterwijk@gmail.com',
                                    'bug_id': 968947,
                                    'count': 0,
                                    'creation_time': 1369924708.0,
                                    'creator': 'puiterwijk@gmail.com',
                                    'creator_id': 330125,
                                    'id': 5962818,
                                    'is_private': False,
                                    'text': '\nSpec URL: http://puiterwijk.fedorapeople..',
                                    'time': 1369924708.0},
                                  { 'author': 'puiterwijk@gmail.com',
                                    'bug_id': 968947,
                                    'count': 1,
                                    'creation_time': 1369924717.0,
                                    'creator': 'puiterwijk@gmail.com',
                                    'creator_id': 330125,
                                    'id': 5962819,
                                    'is_private': False,
                                    'text': 'This package built on koji:    http://koj...',
                                    'time': 1369924717.0},
                                  { 'author': 'rbean@redhat.com',
                                    'bug_id': 968947,
                                    'count': 2,
                                    'creation_time': 1369950294.0,
                                    'creator': 'rbean@redhat.com',
                                    'creator_id': 269108,
                                    'id': 5964283,
                                    'is_private': False,
                                    'text': 'Some preliminary comments:\n\n* The ...',
                                    'time': 1369950294.0}],
                    'component': 'Package Review',
                    'components': ['Package Review'],
                    'creation_time': 1369924680.0,
                    'creator': 'puiterwijk@gmail.com',
                    'depends_on': [],
                    'description': '\nSpec URL: http://puiterwijk.fedorapeople..',
                    'docs_contact': '',
                    'estimated_time': 0.0,
                    'external_bugs': [],
                    'fixed_in': '',
                    'flags': [ { 'creation_date': 1392337756.0,
                                 'id': 1703755,
                                 'is_active': 1,
                                 'modification_date': 1392337756.0,
                                 'name': 'needinfo',
                                 'requestee': 'puiterwijk@gmail.com',
                                 'setter': 'rbean@redhat.com',
                                 'status': '?',
                                 'type_id': 16}],
                    'groups': [],
                    'id': 968947,
                    'is_cc_accessible': True,
                    'is_confirmed': True,
                    'is_creator_accessible': True,
                    'is_open': True,
                    'keywords': [],
                    'last_change_time': 1392337756.0,
                    'op_sys': 'Unspecified',
                    'platform': 'Unspecified',
                    'priority': 'unspecified',
                    'product': 'Fedora',
                    'qa_contact': 'extras-qa@fedoraproject.org',
                    'remaining_time': 0.0,
                    'resolution': '',
                    'see_also': [],
                    'severity': 'unspecified',
                    'status': 'ASSIGNED',
                    'summary': 'Review Request: gallery3-openid - OpenID authentication for Gallery3',
                    'target_milestone': '---',
                    'target_release': ['---'],
                    'url': '',
                    'version': 'rawhide',
                    'versions': ['rawhide'],
                    'weburl': 'https://bugzilla.redhat.com/show_bug.cgi?id=968947',
                    'whiteboard': ''},
           'event': { 'changes': [ { 'added': 'ASSIGNED',
                                     'field_name': 'status',
                                     'removed': 'NEW'},
                                   { 'added': 'rbean@redhat.com',
                                     'field_name': 'cc',
                                     'removed': ''},
                                   { 'added': 'rbean@redhat.com',
                                     'field_name': 'assigned_to',
                                     'removed': 'nobody@fedoraproject.org'}],
                      'when': 1369949333.0,
                      'who': 'rbean@redhat.com'}},
  'msg_id': '2014-0bc98222-a864-4aea-bc6b-e3b090d2cc3d',
  'timestamp': 1395760459,
  'topic': 'org.fedoraproject.prod.bugzilla.bug.update',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() bugzilla.bug.update
fedmsg.meta.msg2subtitle() ralph updated ‘status’, ‘cc’, and ‘assigned_to’ on RHBZ#968947 ‘Review Request: gallery3-openid - OpenID…’
fedmsg.meta.msg2link() https://bugzilla.redhat.com/show_bug.cgi?id=968947
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘puiterwijk’, ‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘Fedora/Package Review/968947’])
fedmsg.meta.msg2icon() 760939ad-a9db-432b-9938-dac706a57b50-icon
fedmsg.meta.msg2secondary_icon() 760939ad-a9db-432b-9938-dac706a57b50-secondary_icon

buildsys

buildsys.build.state.change

Koji emits messages on this topic anytime the state of a build changes.

The state codes can be pretty cryptic (they are just integers and are the enums used by koji internally):

>>> import koji
>>> koji.BUILD_STATES
{
    'BUILDING': 0,
    'COMPLETE': 1,
    'DELETED': 2,
    'FAILED': 3,
    'CANCELED': 4,
}

The example here is one of a build being cancelled on the primary koji instance.

You can view the history of messages with the buildsys.build.state.change topic or all buildsys messages in datagrepper.

{ 'msg': { 'attribute': 'state',
           'build_id': 614503,
           'instance': 'primary',
           'name': 'plasma-systemsettings',
           'new': 4,
           'old': 4,
           'owner': 'dvratil',
           'release': '1.fc23',
           'task_id': 9053697,
           'version': '5.2.1'},
  'msg_id': '2015-51be4c8e-8ab6-4dcb-ac0d-37b257765c71',
  'timestamp': 1424789698.0,
  'topic': 'org.fedoraproject.prod.buildsys.build.state.change'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.build.state.change
fedmsg.meta.msg2subtitle() dvratil’s plasma-systemsettings-5.2.1-1.fc23 was cancelled
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/buildinfo?buildID=614503
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘dvratil’])
fedmsg.meta.msg2packages() set([‘plasma-systemsettings’])
fedmsg.meta.msg2objects() set([‘primary/builds/plasma-systemsettings/5.2.1/1.fc23’])
fedmsg.meta.msg2icon() 1f267c67-60b5-43ec-9f77-0b1de3ef3858-icon
fedmsg.meta.msg2secondary_icon() 1f267c67-60b5-43ec-9f77-0b1de3ef3858-secondary_icon

buildsys.build.state.change

Koji emits messages on this topic anytime the state of a build changes.

The state codes can be pretty cryptic (they are just integers and are the enums used by koji internally):

>>> import koji
>>> koji.BUILD_STATES
{
    'BUILDING': 0,
    'COMPLETE': 1,
    'DELETED': 2,
    'FAILED': 3,
    'CANCELED': 4,
}

The example here is one of a build succeeding on the primary koji instance.

You can view the history of messages with the buildsys.build.state.change topic or all buildsys messages in datagrepper.

{ 'msg': { 'attribute': 'state',
           'build_id': 612324,
           'instance': 'primary',
           'name': 'ansible',
           'new': 1,
           'old': 0,
           'owner': 'kevin',
           'release': '1.el7',
           'task_id': 8973154,
           'version': '1.8.3'},
  'msg_id': '2015-6395fb7a-e5a7-4b95-858a-ff7b80410e7f',
  'timestamp': 1424216566.0,
  'topic': 'org.fedoraproject.prod.buildsys.build.state.change'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.build.state.change
fedmsg.meta.msg2subtitle() kevin’s ansible-1.8.3-1.el7 completed
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/buildinfo?buildID=612324
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘kevin’])
fedmsg.meta.msg2packages() set([‘ansible’])
fedmsg.meta.msg2objects() set([‘primary/builds/ansible/1.8.3/1.el7’])
fedmsg.meta.msg2icon() ece2f367-3c57-45e5-b4fb-e77c96b391d8-icon
fedmsg.meta.msg2secondary_icon() ece2f367-3c57-45e5-b4fb-e77c96b391d8-secondary_icon

buildsys.build.state.change

Koji emits messages on this topic anytime the state of a build changes.

The state codes can be pretty cryptic (they are just integers and are the enums used by koji internally):

>>> import koji
>>> koji.BUILD_STATES
{
    'BUILDING': 0,
    'COMPLETE': 1,
    'DELETED': 2,
    'FAILED': 3,
    'CANCELED': 4,
}

The example here is one of a build failing on a secondary arch koji instance.

You can view the history of messages with the buildsys.build.state.change topic or all buildsys messages in datagrepper.

{ 'msg': { 'attribute': 'state',
           'build_id': 288888,
           'instance': 's390',
           'name': '64tass',
           'new': 3,
           'old': 0,
           'owner': 'sharkcz',
           'release': '1.fc22',
           'task_id': 1739950,
           'version': '1.51.727'},
  'msg_id': '2015-e3483831-5f88-401b-b20d-05537e6a010d',
  'timestamp': 1424787586.0,
  'topic': 'org.fedoraproject.prod.buildsys.build.state.change'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.build.state.change
fedmsg.meta.msg2subtitle() sharkcz’s 64tass-1.51.727-1.fc22 failed to build (s390)
fedmsg.meta.msg2link() http://s390.koji.fedoraproject.org/koji/buildinfo?buildID=288888
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘sharkcz’])
fedmsg.meta.msg2packages() set([‘64tass’])
fedmsg.meta.msg2objects() set([‘s390/builds/64tass/1.51.727/1.fc22’])
fedmsg.meta.msg2icon() 5da93140-d8c0-4a86-ae4e-7fd8c3a34574-icon
fedmsg.meta.msg2secondary_icon() 5da93140-d8c0-4a86-ae4e-7fd8c3a34574-secondary_icon

buildsys.build.state.change

Koji emits messages on this topic anytime the state of a build changes.

The state codes can be pretty cryptic (they are just integers and are the enums used by koji internally):

>>> import koji
>>> koji.BUILD_STATES
{
    'BUILDING': 0,
    'COMPLETE': 1,
    'DELETED': 2,
    'FAILED': 3,
    'CANCELED': 4,
}

The example here is one of a new build starting.

You can view the history of messages with the buildsys.build.state.change topic or all buildsys messages in datagrepper.

{ 'i': 1,
  'msg': { 'attribute': 'state',
           'build_id': 12345,
           'instance': 'primary',
           'name': 'eclipse-ptp',
           'new': 0,
           'old': 3,
           'owner': 'ralph',
           'release': '1.fc19',
           'task_id': 4642,
           'version': '6.0.3'},
  'timestamp': 1359604772.178867,
  'topic': 'org.fedoraproject.prod.buildsys.build.state.change',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.build.state.change
fedmsg.meta.msg2subtitle() ralph’s eclipse-ptp-6.0.3-1.fc19 started building
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/buildinfo?buildID=12345
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([‘eclipse-ptp’])
fedmsg.meta.msg2objects() set([‘primary/builds/eclipse-ptp/6.0.3/1.fc19’])
fedmsg.meta.msg2icon() 94d2f475-eb63-4b10-83cb-78a0857780e4-icon
fedmsg.meta.msg2secondary_icon() 94d2f475-eb63-4b10-83cb-78a0857780e4-secondary_icon

buildsys.build.state.change

Koji emits messages on this topic anytime the state of a build changes.

The state codes can be tricky, (they’re the ones used internally by koji).

>>> import koji
>>> koji.BUILD_STATES
{
    'BUILDING': 0,
    'COMPLETE': 1,
    'DELETED': 2,
    'FAILED': 3,
    'CANCELED': 4,
}

This example message shows one where for some reason or another, koji was unable to publish the name of the owner of a build. The ‘owner’ field is set to None.

You can view the history of messages with the buildsys.build.state.change topic or all buildsys messages in datagrepper.

{ 'i': 1,
  'msg': { 'attribute': 'state',
           'build_id': 12345,
           'instance': 'primary',
           'name': 'eclipse-ptp',
           'new': 0,
           'old': 3,
           'owner': None,
           'release': '1.fc19',
           'task_id': 4642,
           'version': '6.0.3'},
  'timestamp': 1359604772.178867,
  'topic': 'org.fedoraproject.prod.buildsys.build.state.change',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.build.state.change
fedmsg.meta.msg2subtitle() eclipse-ptp-6.0.3-1.fc19 started building
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/buildinfo?buildID=12345
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘eclipse-ptp’])
fedmsg.meta.msg2objects() set([‘primary/builds/eclipse-ptp/6.0.3/1.fc19’])
fedmsg.meta.msg2icon() 7b7df253-73cf-4465-a875-f77a3f0c2de3-icon
fedmsg.meta.msg2secondary_icon() 7b7df253-73cf-4465-a875-f77a3f0c2de3-secondary_icon

buildsys.package.list.change

Koji emits these messages a package listing changes.

You can view the history of messages with the buildsys.package.list.change topic or all buildsys messages in datagrepper.

{ 'i': 2,
  'msg': { 'package': 'almanah', 'tag': 'f17'},
  'timestamp': 1361903735.0,
  'topic': 'org.fedoraproject.prod.buildsys.package.list.change'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.package.list.change
fedmsg.meta.msg2subtitle() Package list change for almanah: ‘f17’
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘almanah’])
fedmsg.meta.msg2objects() set([‘primary/tags/f17’])
fedmsg.meta.msg2icon() 09cb9f95-ff29-4a87-92d6-3533ec594a23-icon
fedmsg.meta.msg2secondary_icon() 09cb9f95-ff29-4a87-92d6-3533ec594a23-secondary_icon

buildsys.repo.done

Koji emits these messages when repo initialization finishes.

You can view the history of messages with the buildsys.repo.done topic or all buildsys messages in datagrepper.

{ 'i': 2,
  'msg': { 'repo_id': 23456, 'tag': 'f19-build', 'tag_id': 12345},
  'timestamp': 1359655886.353586,
  'topic': 'org.fedoraproject.prod.buildsys.repo.done',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.repo.done
fedmsg.meta.msg2subtitle() Repo done: f19-build
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taginfo?tagID=12345
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘primary/repos/f19-build’])
fedmsg.meta.msg2icon() 02f1a2d9-be0b-427b-9a74-39a116515737-icon
fedmsg.meta.msg2secondary_icon() 02f1a2d9-be0b-427b-9a74-39a116515737-secondary_icon

buildsys.repo.init

Koji emits these messages when a repository begins initializing.

You can view the history of messages with the buildsys.repo.init topic or all buildsys messages in datagrepper.

{ 'i': 2,
  'msg': { 'repo_id': 23456, 'tag': 'f19-build', 'tag_id': 12345},
  'timestamp': 1359655886.353586,
  'topic': 'org.fedoraproject.prod.buildsys.repo.init',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.repo.init
fedmsg.meta.msg2subtitle() Repo initialized: f19-build
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taginfo?tagID=12345
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘primary/repos/f19-build’])
fedmsg.meta.msg2icon() 21c05f2c-549f-4e36-921b-1c58e5f72250-icon
fedmsg.meta.msg2secondary_icon() 21c05f2c-549f-4e36-921b-1c58e5f72250-secondary_icon

buildsys.rpm.sign

Koji emits these messages a package is signed with GPG.

For more information, see the sigul project.

You can view the history of messages with the buildsys.rpm.sign topic or all buildsys messages in datagrepper.

{ 'crypto': 'x509',
  'i': 15,
  'msg': { 'build': { 'id': 607658},
           'instance': 'primary',
           'rpm': { 'arch': 'i686',
                    'build_id': 607658,
                    'buildroot_id': 2877398,
                    'buildtime': 1422465286,
                    'epoch': None,
                    'external_repo_id': 0,
                    'external_repo_name': 'INTERNAL',
                    'id': 5928874,
                    'name': 'gstreamer1-plugins-base-devel',
                    'payloadhash': '05bc945666248817e0b5346f811bbac0',
                    'release': '1.fc21',
                    'size': 266720,
                    'version': '1.4.5'},
           'sighash': '8f84058e6bbcae89701271e8b0c43d1d',
           'sigkey': 'ab845621'},
  'msg_id': '2015-271fd050-3198-46f8-b0b1-4bcf6e70bdd0',
  'timestamp': 1422465977,
  'topic': 'org.fedoraproject.prod.buildsys.rpm.sign',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.rpm.sign
fedmsg.meta.msg2subtitle() Koji build gstreamer1-plugins-base-devel-1.4.5-1.fc21.i686.rpm signed with sigkey ‘ab845621’
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/buildinfo?buildID=607658
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘gstreamer1-plugins-base-devel’])
fedmsg.meta.msg2objects() set([‘signatures/gstreamer1-plugins-base-devel’])
fedmsg.meta.msg2icon() 212a570d-aa32-43d2-a342-f514a08cc570-icon
fedmsg.meta.msg2secondary_icon() 212a570d-aa32-43d2-a342-f514a08cc570-secondary_icon

buildsys.tag

Koji emits these messages when a build has a certain tag added to it.

You can view the history of messages with the buildsys.tag topic or all buildsys messages in datagrepper.

{ 'i': 1,
  'msg': { 'name': 'stage',
           'owner': 'ralph',
           'release': '3.fc18',
           'tag': 'f18-updates-testing-pending',
           'tag_id': 216,
           'user': 'bodhi',
           'version': '4.1.1'},
  'timestamp': 1359603469.21164,
  'topic': 'org.fedoraproject.prod.buildsys.tag',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.tag
fedmsg.meta.msg2subtitle() ralph’s stage-4.1.1-3.fc18 tagged into f18-updates-testing-pending by bodhi
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taginfo?tagID=216
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘bodhi’, ‘ralph’])
fedmsg.meta.msg2packages() set([‘stage’])
fedmsg.meta.msg2objects() set([‘primary/tags/f18-updates-testing-pending’, ‘primary/builds/stage/4.1.1/3.fc18’])
fedmsg.meta.msg2icon() 2aeb6aaf-36ac-4a0f-8e73-2201a00a191a-icon
fedmsg.meta.msg2secondary_icon() 2aeb6aaf-36ac-4a0f-8e73-2201a00a191a-secondary_icon

buildsys.task.state.change

Koji emits messages on this topic anytime the state of a scratch build changes.

For reasons internal to koji itself, the state codes for scratch builds are not as cryptic as the ones for regular builds. It is worth noting that the task state codes are different from the build state codes. If you wanted to know the numeric equivalents, you could check with koji itself:

>>> import koji
>>> koji.TASK_STATES
{
    'FREE': 0,
    'OPEN': 1,
    'CLOSED': 2,
    'CANCELED': 3,
    'ASSIGNED': 4,
    'FAILED': 5,
}

Here’s an example message of a scratch build failing.

You can view the history of messages with the buildsys.task.state.change topic or all buildsys messages in datagrepper.

{ 'i': 1,
  'msg': { 'attribute': 'state',
           'id': 6380373,
           'method': 'build',
           'new': 'FAILED',
           'old': 'OPEN',
           'owner': 'ralph',
           'srpm': 'python-websocket-client-0.12.0-1.fc20.src.rpm'},
  'msg_id': '2014-991dbbad-b5f5-4f62-b889-d3b637d0cb49',
  'timestamp': 1389298512,
  'topic': 'org.fedoraproject.prod.buildsys.task.state.change',
  'username': 'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.task.state.change
fedmsg.meta.msg2subtitle() ralph’s scratch build of python-websocket-client-0.12.0-1.fc20.src.rpm failed
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taskinfo?taskID=6380373
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘primary/scratch_builds/python-websocket-client-0.12.0-1.fc20.src.rpm’])
fedmsg.meta.msg2icon() 47929245-2e92-47b2-9f51-9cc945a56551-icon
fedmsg.meta.msg2secondary_icon() 47929245-2e92-47b2-9f51-9cc945a56551-secondary_icon

buildsys.task.state.change

Koji emits messages on this topic anytime the state of a scratch build changes.

For reasons internal to koji itself, the state codes for scratch builds are not as cryptic as the ones for regular builds. It is worth noting that the task state codes are different from the build state codes. If you wanted to know the numeric equivalents, you could check with koji itself:

>>> import koji
>>> koji.TASK_STATES
{
    'FREE': 0,
    'OPEN': 1,
    'CLOSED': 2,
    'CANCELED': 3,
    'ASSIGNED': 4,
    'FAILED': 5,
}

Here’s an example message of a scratch build failing.

You can view the history of messages with the buildsys.task.state.change topic or all buildsys messages in datagrepper.

{ 'i': 1,
  'msg': { 'attribute': 'state',
           'id': 6380373,
           'info': { 'arch': 'noarch',
                     'awaited': None,
                     'channel_id': 1,
                     'children': [],
                     'completion_time': None,
                     'create_time': '2015-06-22 14:04:40.523486',
                     'host_id': 60,
                     'id': 10177586,
                     'label': None,
                     'method': 'build',
                     'owner': 456,
                     'parent': None,
                     'priority': 20,
                     'request': [ 'cli-build/1434981816.694115.CAAulQZy/pagure-0.1.18-1.fc21.src.rpm',
                                  'epel7-candidate',
                                  { 'scratch': True}],
                     'start_time': '2015-06-22 14:04:41.44985',
                     'state': 1,
                     'waiting': None},
           'method': 'build',
           'new': 'FAILED',
           'old': 'OPEN',
           'owner': 'ralph',
           'srpm': 'python-websocket-client-0.12.0-1.fc20.src.rpm'},
  'msg_id': '2014-991dbbad-b5f5-4f62-b889-d3b637d0cb49',
  'timestamp': 1389298512,
  'topic': 'org.fedoraproject.prod.buildsys.task.state.change',
  'username': 'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.task.state.change
fedmsg.meta.msg2subtitle() ralph’s scratch build of python-websocket-client-0.12.0-1.fc20.src.rpm for epel7-candidate failed
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taskinfo?taskID=6380373
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘primary/scratch_builds/python-websocket-client-0.12.0-1.fc20.src.rpm’])
fedmsg.meta.msg2icon() beafe5e4-1c30-4afb-89fe-5a700349c2af-icon
fedmsg.meta.msg2secondary_icon() beafe5e4-1c30-4afb-89fe-5a700349c2af-secondary_icon

buildsys.task.state.change

Koji emits messages on this topic anytime the state of a scratch build changes.

For reasons internal to koji itself, the state codes for scratch builds are not as cryptic as the ones for regular builds. It is worth noting that the task state codes are different from the build state codes. If you wanted to know the numeric equivalents, you could check with koji itself:

>>> import koji
>>> koji.TASK_STATES
{
    'FREE': 0,
    'OPEN': 1,
    'CLOSED': 2,
    'CANCELED': 3,
    'ASSIGNED': 4,
    'FAILED': 5,
}

Here’s an example message of a new scratch build starting.

You can view the history of messages with the buildsys.task.state.change topic or all buildsys messages in datagrepper.

{ u'i': 1,
  u'msg': { u'attribute': u'state',
            u'id': 6380373,
            u'method': u'build',
            u'new': u'OPEN',
            u'old': u'FREE',
            u'owner': u'ralph',
            u'srpm': 'python-websocket-client-0.12.0-1.fc20.src.rpm'},
  u'msg_id': u'2014-10b5b1b6-42c7-4d64-aeae-5029b9515d47',
  u'timestamp': 1389298195,
  u'topic': u'org.fedoraproject.prod.buildsys.task.state.change',
  u'username': u'root'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.task.state.change
fedmsg.meta.msg2subtitle() ralph’s scratch build of python-websocket-client-0.12.0-1.fc20.src.rpm started
fedmsg.meta.msg2link() http://koji.stg.fedoraproject.org/koji/taskinfo?taskID=6380373
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘primary/scratch_builds/python-websocket-client-0.12.0-1.fc20.src.rpm’])
fedmsg.meta.msg2icon() 69b3e70f-d9aa-4d20-91e1-c451fdf03cfb-icon
fedmsg.meta.msg2secondary_icon() 69b3e70f-d9aa-4d20-91e1-c451fdf03cfb-secondary_icon

buildsys.untag

Koji emits these messages anytime a tag is removed from a build.

You can view the history of messages with the buildsys.untag topic or all buildsys messages in datagrepper.

{ 'i': 85,
  'msg': { 'name': 'globus-gram-job-manager-sge',
           'owner': 'ralph',
           'release': '2.fc16',
           'tag': 'f16-updates-pending',
           'tag_id': 216,
           'user': 'bodhi',
           'version': '1.5'},
  'timestamp': 1359655345.774982,
  'topic': 'org.fedoraproject.prod.buildsys.untag',
  'username': 'apache'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() buildsys.untag
fedmsg.meta.msg2subtitle() ralph’s globus-gram-job-manager-sge-1.5-2.fc16 untagged from f16-updates-pending by bodhi
fedmsg.meta.msg2link() http://koji.fedoraproject.org/koji/taginfo?tagID=216
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘bodhi’, ‘ralph’])
fedmsg.meta.msg2packages() set([‘globus-gram-job-manager-sge’])
fedmsg.meta.msg2objects() set([‘primary/builds/globus-gram-job-manager-sge/1.5/2.fc16’, ‘primary/tags/f16-updates-pending’])
fedmsg.meta.msg2icon() 09c6b3e4-abe0-4f1d-bb63-573cceebad18-icon
fedmsg.meta.msg2secondary_icon() 09c6b3e4-abe0-4f1d-bb63-573cceebad18-secondary_icon

ci

ci.pipeline.allpackages.complete

These messages are published when the All Packages CI pipeline announces having completed successfully running the entire pipeline on a package.

You can view the history of messages with the ci.pipeline.allpackages.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'headers': { },
  'i': 1,
  'msg': { 'CI_NAME': 'upstream-fedora-f28-pipeline',
           'CI_TYPE': 'custom',
           'branch': 'f28',
           'build_id': '335',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/upstream-fedora-f28-pipeline/detail/upstream-fedora-f28-pipeline/335/pipeline/',
           'message-content': '',
           'namespace': 'rpms',
           'nvr': '',
           'original_spec_nvr': '',
           'ref': 'x86_64',
           'repo': 'gdb',
           'rev': '35cdcb6a32562b632c075f2fd42793f7492dcdb3',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.allpackages.complete',
           'username': 'jankratochvil'},
  'msg_id': '2018-1436f172-aa90-49f2-9ff0-9b34608f38e8',
  'source_name': 'datanommer',
  'source_version': '0.8.2',
  'timestamp': 1522055492.0,
  'topic': 'org.centos.prod.ci.pipeline.allpackages.complete',
  'username': None}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.allpackages.complete
fedmsg.meta.msg2subtitle() Commit “35cdcb6a” of package rpms/gdb passed the All Packages CI pipeline on branch f28
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/upstream-fedora-f28-pipeline/detail/upstream-fedora-f28-pipeline/335/pipeline/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘jankratochvil’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/gdb/35cdcb6a32562b632c075f2fd42793f7492dcdb3/f28/allpackages/complete’])
fedmsg.meta.msg2icon() 0fef3658-3e8b-490d-b5e4-dbdc7ec0bfab-icon
fedmsg.meta.msg2secondary_icon() 0fef3658-3e8b-490d-b5e4-dbdc7ec0bfab-secondary_icon

ci.pipeline.allpackages.package.running

These messages are published when the Allpackages CI pipeline announces that the build of a package is running.

You can view the history of messages with the ci.pipeline.allpackages.package.running topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'headers': { },
  'i': 1,
  'msg': { 'CI_NAME': 'upstream-fedora-f28-pipeline',
           'CI_TYPE': 'custom',
           'branch': 'f28',
           'build_id': '335',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/upstream-fedora-f28-pipeline/detail/upstream-fedora-f28-pipeline/335/pipeline/',
           'message-content': '',
           'namespace': 'rpms',
           'nvr': '',
           'original_spec_nvr': '',
           'ref': 'x86_64',
           'repo': 'gdb',
           'rev': '35cdcb6a32562b632c075f2fd42793f7492dcdb3',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.allpackages.package.running',
           'username': 'jankratochvil'},
  'msg_id': '2018-cfb9a40e-3220-4dcf-a5aa-270a6cee975c',
  'source_name': 'datanommer',
  'source_version': '0.8.2',
  'timestamp': 1522054091.0,
  'topic': 'org.centos.prod.ci.pipeline.allpackages.package.running',
  'username': None}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.allpackages.package.running
fedmsg.meta.msg2subtitle() Commit 35cdcb6a of package rpms/gdb is being built in the All Packages CI pipeline on branch f28
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/upstream-fedora-f28-pipeline/detail/upstream-fedora-f28-pipeline/335/pipeline/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘jankratochvil’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/gdb/35cdcb6a32562b632c075f2fd42793f7492dcdb3/f28/allpackages/package/running’])
fedmsg.meta.msg2icon() ee90e61e-173d-4be2-9228-883e2e46d046-icon
fedmsg.meta.msg2secondary_icon() ee90e61e-173d-4be2-9228-883e2e46d046-secondary_icon

ci.pipeline.complete

These messages are published when the Atomic CI pipeline announces having aborted a run of the pipeline on a package.

You can view the history of messages with the ci.pipeline.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'ABORTED',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.complete
fedmsg.meta.msg2subtitle() Commit “591b0d2f” of package rpms/vim was aborted on the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/complete’])
fedmsg.meta.msg2icon() 0237d489-2004-40e9-81cc-cd10d0c14fb5-icon
fedmsg.meta.msg2secondary_icon() 0237d489-2004-40e9-81cc-cd10d0c14fb5-secondary_icon

ci.pipeline.complete

These messages are published when the Atomic CI pipeline announces having errored a run of the pipeline on a package.

This means the pipeline could run the tests but the tests themselves failed (as opposed to the pipeline failed to run the tests).

You can view the history of messages with the ci.pipeline.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'UNSTABLE',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.complete
fedmsg.meta.msg2subtitle() Commit “591b0d2f” of package rpms/vim errored the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/complete’])
fedmsg.meta.msg2icon() 64d14bf8-3bf7-4847-9c56-5b4da1329a02-icon
fedmsg.meta.msg2secondary_icon() 64d14bf8-3bf7-4847-9c56-5b4da1329a02-secondary_icon

ci.pipeline.complete

These messages are published when the Atomic CI pipeline announces having failed a run of the pipeline on a package.

This means the pipeline failed to run the tests (as opposed to run the tests but these failed).

You can view the history of messages with the ci.pipeline.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'FAILEd',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.complete
fedmsg.meta.msg2subtitle() Commit “591b0d2f” of package rpms/vim failed the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/complete’])
fedmsg.meta.msg2icon() 5ad81408-9097-49b6-afd6-6a0be29ffde5-icon
fedmsg.meta.msg2secondary_icon() 5ad81408-9097-49b6-afd6-6a0be29ffde5-secondary_icon

ci.pipeline.complete

These messages are published when the Atomic CI pipeline announces having completed successfully running the entire pipeline on a package.

You can view the history of messages with the ci.pipeline.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.complete
fedmsg.meta.msg2subtitle() Commit “591b0d2f” of package rpms/vim passed the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/complete’])
fedmsg.meta.msg2icon() 8aab7f2d-2bc3-4ef4-b317-2a9f162b7ab3-icon
fedmsg.meta.msg2secondary_icon() 8aab7f2d-2bc3-4ef4-b317-2a9f162b7ab3-secondary_icon

ci.pipeline.compose.complete

These messages are published when the Atomic CI pipeline announces that a compose containing a specified package has completed.

You can view the history of messages with the ci.pipeline.compose.complete topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-ostree-compose',
           'CI_STATUS': 'passed',
           'CI_TYPE': 'custom',
           'branch': 'master',
           'build_id': '772',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-ostree-compose/772/',
           'compose_rev': '7a8b6262efe6a4a5194bf48eb4577527fd05c23ff4f2192c276dc98deaa8e718',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/master/ostree',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/master/x86_64/atomic-host',
           'repo': 'device-mapper-multipath',
           'rev': '7327f260a8a90058efd576b8ce12d78e403d269d',
           'status': 'SUCCESS',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.compose.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-f3a0d6ca-d0d1-4d2c-a578-040cbfc9e2b0',
  'source_version': '0.7.0',
  'timestamp': 1498242025.0,
  'topic': 'org.centos.prod.ci.pipeline.compose.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.compose.complete
fedmsg.meta.msg2subtitle() Commit 7327f260 of package rpms/device-mapper-multipath passed a compose in the Atomic CI pipeline on branch master
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-ostree-compose/772/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/device-mapper-multipath/7327f260a8a90058efd576b8ce12d78e403d269d/master/compose/complete’])
fedmsg.meta.msg2icon() 2d310751-94e0-4d00-8e0a-9b0977413cc7-icon
fedmsg.meta.msg2secondary_icon() 2d310751-94e0-4d00-8e0a-9b0977413cc7-secondary_icon

ci.pipeline.compose.running

These messages are published when the Atomic CI pipeline announces that a compose containing a specified package is running.

You can view the history of messages with the ci.pipeline.compose.running topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-ostree-compose',
           'CI_TYPE': 'custom',
           'branch': 'master',
           'build_id': '772',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-ostree-compose/772/',
           'compose_rev': '',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/rawhide/ostree',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/rawhide/x86_64/atomic-host',
           'repo': 'device-mapper-multipath',
           'rev': '7327f260a8a90058efd576b8ce12d78e403d269d',
           'status': 'success',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.compose.running',
           'username': 'fedora-atomic'},
  'msg_id': '2017-0b1258d6-dfe6-434c-8754-4af0b83ede64',
  'source_version': '0.7.0',
  'timestamp': 1498241532.0,
  'topic': 'org.centos.prod.ci.pipeline.compose.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.compose.running
fedmsg.meta.msg2subtitle() Commit 7327f260 of package rpms/device-mapper-multipath is being part of a compose in the Atomic CI pipeline on branch master
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-ostree-compose/772/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/device-mapper-multipath/7327f260a8a90058efd576b8ce12d78e403d269d/master/compose/running’])
fedmsg.meta.msg2icon() d1475602-4abd-477b-a5f0-e6f02c331580-icon
fedmsg.meta.msg2secondary_icon() d1475602-4abd-477b-a5f0-e6f02c331580-secondary_icon

ci.pipeline.compose.test.integration.complete

These messages are published when the Atomic CI pipeline announces that the integration test of a compose containing a specified package has completed.

You can view the history of messages with the ci.pipeline.compose.test.integration.complete topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-atomic-host-tests',
           'CI_STATUS': 'failed',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '377',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-atomic-host-tests/377/',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'kernel',
           'rev': '7b272f5f610d89eb9077640c3fc13b6472e4c31d',
           'status': 'FAILED',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-2f33b69b-6336-4e67-98fa-fc17d0a004bc',
  'source_version': '0.7.0',
  'timestamp': 1498577008.0,
  'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.compose.test.integration.complete
fedmsg.meta.msg2subtitle() Commit 7b272f5f of package rpms/kernel failed its tests as part of a compose in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-atomic-host-tests/377/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/kernel/7b272f5f610d89eb9077640c3fc13b6472e4c31d/f26/compose/test/integration/complete’])
fedmsg.meta.msg2icon() d0d2b241-4da3-4f3d-9ca6-0502e2916ffc-icon
fedmsg.meta.msg2secondary_icon() d0d2b241-4da3-4f3d-9ca6-0502e2916ffc-secondary_icon

ci.pipeline.compose.test.integration.queued

These messages are published when the Atomic CI pipeline announces that the integration test of a compose containing a specified package are queued.

You can view the history of messages with the ci.pipeline.compose.test.integration.queued topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-ostree-boot-sanity',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '537',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-ostree-boot-sanity/537/',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'grub2',
           'rev': '77d0810cf0c2dae524736a0c39decffb95c20f4c',
           'status': 'success',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.queued',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b8b527ce-c03a-48fa-9ff2-d2ee2be9de6d',
  'source_version': '0.7.0',
  'timestamp': 1498512283.0,
  'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.queued'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.compose.test.integration.queued
fedmsg.meta.msg2subtitle() Commit 77d0810c of package rpms/grub2 is queued for tests as part of a compose in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-ostree-boot-sanity/537/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/grub2/77d0810cf0c2dae524736a0c39decffb95c20f4c/f26/compose/test/integration/queued’])
fedmsg.meta.msg2icon() 9f67e29b-9add-4f03-adda-02e1bcfe7245-icon
fedmsg.meta.msg2secondary_icon() 9f67e29b-9add-4f03-adda-02e1bcfe7245-secondary_icon

ci.pipeline.compose.test.integration.running

These messages are published when the Atomic CI pipeline announces that the integration test of a compose containing a specified package are running.

You can view the history of messages with the ci.pipeline.compose.test.integration.running topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-atomic-host-tests',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '377',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-atomic-host-tests/377/',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'kernel',
           'rev': '7b272f5f610d89eb9077640c3fc13b6472e4c31d',
           'status': 'success',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.running',
           'username': 'fedora-atomic'},
  'msg_id': '2017-cb05d8b5-24d5-4ac0-9424-a21af20ae15c',
  'source_version': '0.7.0',
  'timestamp': 1498575078.0,
  'topic': 'org.centos.prod.ci.pipeline.compose.test.integration.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.compose.test.integration.running
fedmsg.meta.msg2subtitle() Commit 7b272f5f of package rpms/kernel is being tested as part of a compose in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-atomic-host-tests/377/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/kernel/7b272f5f610d89eb9077640c3fc13b6472e4c31d/f26/compose/test/integration/running’])
fedmsg.meta.msg2icon() 1e3af4db-f21f-449c-af81-315c6dd2aa00-icon
fedmsg.meta.msg2secondary_icon() 1e3af4db-f21f-449c-af81-315c6dd2aa00-secondary_icon

ci.pipeline.image.complete

These messages are published when the Atomic CI pipeline announces that the build of the image generated from the compose containing a specified package has completed.

You can view the history of messages with the ci.pipeline.image.complete topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-ostree-image-compose',
           'CI_STATUS': 'passed',
           'CI_TYPE': 'custom',
           'branch': 'f25',
           'build_id': '123',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-ostree-image-compose/123/',
           'compose_rev': 'ce1d81054a2b79a99d66ea413fac25ce94734daa4fec387c39ee03d8e0506158',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f25/ostree',
           'image_name': 'fedora-atomic-25.71-ce1d81054a2b79a.qcow2',
           'image_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f25/images/fedora-atomic-25.71-ce1d81054a2b79a.qcow2',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f25/x86_64/atomic-host',
           'repo': 'grub2',
           'rev': '77d0810cf0c2dae524736a0c39decffb95c20f4c',
           'status': 'FAILED',
           'test_guidance': '',
           'topic': 'org.centos.prod.ci.pipeline.image.complete',
           'type': 'qcow2',
           'username': 'fedora-atomic'},
  'msg_id': '2017-49a59f79-24fb-487a-ba13-bb0901acdab5',
  'source_version': '0.7.0',
  'timestamp': 1498220998.0,
  'topic': 'org.centos.prod.ci.pipeline.image.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.image.complete
fedmsg.meta.msg2subtitle() Commit 77d0810c of package rpms/grub2 failed being built in an image in the Atomic CI pipeline on branch f25
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-ostree-image-compose/123/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/grub2/77d0810cf0c2dae524736a0c39decffb95c20f4c/f25/image/complete’])
fedmsg.meta.msg2icon() bfc2badb-864c-4da0-ab83-348c41056e0d-icon
fedmsg.meta.msg2secondary_icon() bfc2badb-864c-4da0-ab83-348c41056e0d-secondary_icon

ci.pipeline.image.running

These messages are published when the Atomic CI pipeline announces that the build of the image generated from the compose containing a specified package is running.

You can view the history of messages with the ci.pipeline.image.running topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '11',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/11/',
           'compose_rev': 'c6ab48d6bb155131de5f16350903c80494e6eecac52a00d369b8b920ccd6dafd',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'image_name': "''",
           'image_url': "''",
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'NetworkManager',
           'rev': '0cc505ca294de0daa6260bd80e65e18a318b8057',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.stage.ci.pipeline.image.running',
           'type': 'qcow2',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b61a647a-8f98-4f2b-afe9-aa5a7f2ea257',
  'source_version': '0.7.0',
  'timestamp': 1500918319.0,
  'topic': 'org.centos.stage.ci.pipeline.image.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.image.running
fedmsg.meta.msg2subtitle() Commit 0cc505ca of package rpms/NetworkManager is being built in an image in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/11/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/NetworkManager/0cc505ca294de0daa6260bd80e65e18a318b8057/f26/image/running’])
fedmsg.meta.msg2icon() 829b64b6-4c21-4939-8f5b-f3d9f4356a1b-icon
fedmsg.meta.msg2secondary_icon() 829b64b6-4c21-4939-8f5b-f3d9f4356a1b-secondary_icon

ci.pipeline.image.test.smoke.complete

These messages are published when the Atomic CI pipeline announces that the image generated from the compose containing a specified package has completed its tests.

You can view the history of messages with the ci.pipeline.image.test.smoke.complete topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '132',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/132/',
           'compose_rev ': 'b1777ffee14021a94d0b027fbcd841a15bd7cdeebd97527b742eab4e666dc9ec',
           'compose_url ': 'http: //artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'image_name': 'fedora-atomic-26.223-b1777ffee14021a.qcow2',
           'image_url ': 'http: //artifacts.ci.centos.org/artifacts/fedora-atomic/f26/images/fedora-atomic-26.223-b1777ffee14021a.qcow2 ',
           'message-content ': '',
           'namespace': 'rpms',
           'ref ': 'fedora/f26/x86_64/atomic-host',
           'repo': 'nspr',
           'rev': 'fff28640d156c8b5e7302b7736e16442087b6007',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.image.test.smoke.complete',
           'type ': 'qcow2',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b61a647a-8f98-4f2b-afe9-aa5a7f2ea257',
  'source_version': '0.7.0',
  'timestamp': 1500918319.0,
  'topic': 'org.centos.prod.ci.pipeline.image.test.smoke.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.image.test.smoke.complete
fedmsg.meta.msg2subtitle() Commit fff28640 of package rpms/nspr passed its tests in an image in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/132/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/nspr/fff28640d156c8b5e7302b7736e16442087b6007/f26/image/test/smoke/complete’])
fedmsg.meta.msg2icon() 85ce2858-c24f-4441-bb8c-c3de9d279a68-icon
fedmsg.meta.msg2secondary_icon() 85ce2858-c24f-4441-bb8c-c3de9d279a68-secondary_icon

ci.pipeline.image.test.smoke.running

These messages are published when the Atomic CI pipeline announces that the image generated from the compose containing a specified package has completed its tests.

You can view the history of messages with the ci.pipeline.image.test.smoke.running topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '132',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/132/',
           'compose_rev': 'b1777ffee14021a94d0b027fbcd841a15bd7cdeebd97527b742eab4e666dc9ec',
           'compose_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/ostree',
           'image_name': 'fedora-atomic-26.223-b1777ffee14021a.qcow2',
           'image_url': 'http://artifacts.ci.centos.org/artifacts/fedora-atomic/f26/images/fedora-atomic-26.223-b1777ffee14021a.qcow2',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'nspr',
           'rev': 'fff28640d156c8b5e7302b7736e16442087b6007',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.image.test.smoke.running',
           'type': 'qcow2',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b61a647a-8f98-4f2b-afe9-aa5a7f2ea257',
  'source_version': '0.7.0',
  'timestamp': 1500918319.0,
  'topic': 'org.centos.prod.ci.pipeline.image.test.smoke.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.image.test.smoke.running
fedmsg.meta.msg2subtitle() Commit fff28640 of package rpms/nspr is being tested in an image in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/132/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/nspr/fff28640d156c8b5e7302b7736e16442087b6007/f26/image/test/smoke/running’])
fedmsg.meta.msg2icon() ef1dac2e-4383-4ff1-8156-b20f963a6cbb-icon
fedmsg.meta.msg2secondary_icon() ef1dac2e-4383-4ff1-8156-b20f963a6cbb-secondary_icon

ci.pipeline.package.complete

These messages are published when the Atomic CI pipeline announces that the build of a package completed.

You can view the history of messages with the ci.pipeline.package.complete topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '8',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/8/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/NetworkManager_repo/NetworkManager-1.8.2-2.fc26.673.0cc505c.x86_64.rpm',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'NetworkManager',
           'rev': '0cc505ca294de0daa6260bd80e65e18a318b8057',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.stage.ci.pipeline.package.complete',
           'username': 'fedora-atomic'},
  'msg_id': '2017-3a8e6539-d16d-49da-8a33-ac4c3f75dd27',
  'source_version': '0.7.0',
  'timestamp': 1500665940.0,
  'topic': 'org.centos.prod.ci.pipeline.package.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.complete
fedmsg.meta.msg2subtitle() Commit 0cc505ca of package rpms/NetworkManager passed building in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/8/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/NetworkManager/0cc505ca294de0daa6260bd80e65e18a318b8057/f26/package/complete’])
fedmsg.meta.msg2icon() 5ba82f87-8a2f-48be-9205-706bf5e0b3ef-icon
fedmsg.meta.msg2secondary_icon() 5ba82f87-8a2f-48be-9205-706bf5e0b3ef-secondary_icon

ci.pipeline.package.ignore

These messages are published when the Atomic CI pipeline announces that it ignores a commit made on dist-git.

You can view the history of messages with the ci.pipeline.package.ignore topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-2-0',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '47',
           'build_url': 'https://ci.centos.org/job/ci-pipeline-2-0/47/',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'protobuf',
           'rev': 'ada94828daa8fcd0bb68ce13e3ad123545d1c7cc',
           'status': 'success',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.package.ignore',
           'username': 'fedora-atomic'},
  'msg_id': '2017-e3ce244c-a1ea-496f-9a6f-2245dd5ea110',
  'source_version': '0.7.0',
  'timestamp': 1498625602.0,
  'topic': 'org.centos.prod.ci.pipeline.package.ignore'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.ignore
fedmsg.meta.msg2subtitle() Commit “ada94828” of package rpms/protobuf is being ignored by the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://ci.centos.org/job/ci-pipeline-2-0/47/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/protobuf/ada94828daa8fcd0bb68ce13e3ad123545d1c7cc/f26/package/ignore’])
fedmsg.meta.msg2icon() cfad0edb-431c-4bde-b53c-6312fc08dd45-icon
fedmsg.meta.msg2secondary_icon() cfad0edb-431c-4bde-b53c-6312fc08dd45-secondary_icon

ci.pipeline.package.queued

These messages are published when the Atomic CI pipeline announces that the build of a package is queued.

You can view the history of messages with the ci.pipeline.package.queued topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-trigger',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '39',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-trigger/39/',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'NetworkManager',
           'rev': '0cc505ca294de0daa6260bd80e65e18a318b8057',
           'status': 'success',
           'test_guidance': "''",
           'topic': 'org.centos.stage.ci.pipeline.package.queued',
           'username': 'fedora-atomic'},
  'msg_id': '2017-4864d380-a500-4f71-a40e-fe59cc150824',
  'source_version': '0.7.0',
  'timestamp': 1500651841.0,
  'topic': 'org.centos.prod.ci.pipeline.package.queued'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.queued
fedmsg.meta.msg2subtitle() Commit 0cc505ca of package rpms/NetworkManager is queued to be built in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-trigger/39/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/NetworkManager/0cc505ca294de0daa6260bd80e65e18a318b8057/f26/package/queued’])
fedmsg.meta.msg2icon() 8d31f3b8-1605-4ba2-9d7f-5489a53fa760-icon
fedmsg.meta.msg2secondary_icon() 8d31f3b8-1605-4ba2-9d7f-5489a53fa760-secondary_icon

ci.pipeline.package.running

These messages are published when the Atomic CI pipeline announces that the build of a package is running.

You can view the history of messages with the ci.pipeline.package.running topic or all ci messages in datagrepper.

{ 'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '5',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/5/',
           'message-content': '',
           'namespace': 'rpms',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'NetworkManager',
           'rev': '0cc505ca294de0daa6260bd80e65e18a318b8057',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.stage.ci.pipeline.package.running',
           'username': 'fedora-atomic'},
  'msg_id': '2017-66ce76b7-0519-4807-a9b0-831c61b1da6c',
  'source_version': '0.7.0',
  'timestamp': 1500651862.0,
  'topic': 'org.centos.stage.ci.pipeline.package.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.running
fedmsg.meta.msg2subtitle() Commit 0cc505ca of package rpms/NetworkManager is being built in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/5/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/NetworkManager/0cc505ca294de0daa6260bd80e65e18a318b8057/f26/package/running’])
fedmsg.meta.msg2icon() f0037de5-1471-49b7-9da5-c8a6c542d16a-icon
fedmsg.meta.msg2secondary_icon() f0037de5-1471-49b7-9da5-c8a6c542d16a-secondary_icon

ci.pipeline.package.test.functional.complete

These messages are published when the Atomic CI pipeline announces having completed the function tests of a package.

You can view the history of messages with the ci.pipeline.package.test.functional.complete topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.package.test.functional.queued',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.package.test.functional.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.test.functional.complete
fedmsg.meta.msg2subtitle() Commit 591b0d2f of package rpms/vim passed its functional tests in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/package/test/functional/complete’])
fedmsg.meta.msg2icon() ae2195f6-1d94-43d1-96c5-8ec12fb263be-icon
fedmsg.meta.msg2secondary_icon() ae2195f6-1d94-43d1-96c5-8ec12fb263be-secondary_icon

ci.pipeline.package.test.functional.queued

These messages are published when the Atomic CI pipeline announces queuing the function tests of a package.

You can view the history of messages with the ci.pipeline.package.test.functional.queued topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.package.test.functional.queued',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.package.test.functional.queued'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.test.functional.queued
fedmsg.meta.msg2subtitle() Commit 591b0d2f of package rpms/vim is queued for functional testing in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/package/test/functional/queued’])
fedmsg.meta.msg2icon() 10a288b4-128c-4f8d-896e-94404bece8b3-icon
fedmsg.meta.msg2secondary_icon() 10a288b4-128c-4f8d-896e-94404bece8b3-secondary_icon

ci.pipeline.package.test.functional.running

These messages are published when the Atomic CI pipeline announces running the function tests of a package.

You can view the history of messages with the ci.pipeline.package.test.functional.running topic or all ci messages in datagrepper.

{ 'crypto': 'x509',
  'i': 1,
  'msg': { 'CI_NAME': 'ci-pipeline-f26',
           'CI_TYPE': 'custom',
           'branch': 'f26',
           'build_id': '91',
           'build_url': 'https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/',
           'message-content': '',
           'namespace': 'rpms',
           'package_url': 'http://artifacts.ci.centos.org/fedora-atomic/f26/repo/vim_repo/',
           'ref': 'fedora/f26/x86_64/atomic-host',
           'repo': 'vim',
           'rev': '591b0d2fc67a45e4ad13bdc3e312d5554852426a',
           'status': 'SUCCESS',
           'test_guidance': "''",
           'topic': 'org.centos.prod.ci.pipeline.package.test.functional.queued',
           'username': 'fedora-atomic'},
  'msg_id': '2017-b420134c-0e39-4f70-8e5f-0975d7019e4b',
  'timestamp': 1501741048,
  'topic': 'org.centos.prod.ci.pipeline.package.test.functional.running'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() ci.pipeline.package.test.functional.running
fedmsg.meta.msg2subtitle() Commit 591b0d2f of package rpms/vim is running its functional tests in the Atomic CI pipeline on branch f26
fedmsg.meta.msg2link() https://jenkins-continuous-infra.apps.ci.centos.org/job/ci-pipeline-f26/91/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fedora-atomic’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘rpms/vim/591b0d2fc67a45e4ad13bdc3e312d5554852426a/f26/package/test/functional/running’])
fedmsg.meta.msg2icon() 1744924a-d6a6-4c59-839a-b4feeac84705-icon
fedmsg.meta.msg2secondary_icon() 1744924a-d6a6-4c59-839a-b4feeac84705-secondary_icon

compose

compose.23.atomic-lorax.done

The release engineering “compose” scripts used to produce these messages when they had finished the Atomic lorax phase of the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.atomic-lorax.done topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'done'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.atomic-lorax.done'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.atomic-lorax.done
fedmsg.meta.msg2subtitle() Completed Atomic lorax run for Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.23.cloudimg-build.done

The release engineering “compose” scripts used to produce these messages when they had finished the cloud image build phase of the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.cloudimg-build.done topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'done'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.cloudimg-build.done'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.cloudimg-build.done
fedmsg.meta.msg2subtitle() Completed building images for Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.23.cloudimg-checksum.start

The release engineering “compose” scripts used to produce these messages when they had started the Cloud image checksum phase of the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.cloudimg-checksum.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'start'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.cloudimg-checksum.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.cloudimg-checksum.start
fedmsg.meta.msg2subtitle() Started image checksum generation for Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.23.cloudimg-staging.done

The release engineering “compose” scripts used to produce these messages when they had finished the Cloud image staging phase of the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.cloudimg-staging.done topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'start'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.cloudimg-staging.done'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.cloudimg-staging.done
fedmsg.meta.msg2subtitle() Completed master mirror publication for Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.23.make-updates.start

The release engineering “compose” scripts used to produce these messages when they had started the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.make-updates.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'start'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.make-updates.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.make-updates.start
fedmsg.meta.msg2subtitle() Started Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.23.mash-atomic.stop

The release engineering “compose” scripts used to produce these messages when they had started the Atomic mash phase of the make-updates process (which was how we did periodic re-spins of our cloud, atomic, and docker images during the Fedora 21, 22 and 23 cycles). From Fedora 24 onwards, these re-spins are produced with Pungi 4 like all other forms of compose, and emit the standard compose messages with the release number in the topic (e.g. compose.24.start or compose.28.start). Here’s an example of a message from Fedora 23:

You can view the history of messages with the compose.23.mash-atomic.stop topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'branch': '23', 'log': 'start'},
  'timestamp': 1454303707.0,
  'topic': 'org.fedoraproject.prod.compose.23.mash-atomic.stop'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.23.mash-atomic.stop
fedmsg.meta.msg2subtitle() Completed Atomic updates mash for Fedora 23 post-release Cloud/Atomic/Docker respin compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘23/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.28.complete

The release engineering “compose” scripts produce these messages when they have finished a compose for a numbered release. This could be a Branched compose, or a post-release two-week Atomic, Docker, or Cloud compose: the ‘short’ and ‘compose_id’ values can be used to differentiate. The message topic obviously differs based on the release, this one is only an example.

You can view the history of messages with the compose.28.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': '28',
           'compose_id': 'Fedora-Docker-28-20180126.n.0',
           'location': 'https://kojipkgs.fedoraproject.org/compose/Fedora-Docker-28-20180126.n.0',
           'log': 'done',
           'short': 'Fedora-Docker'},
  'timestamp': 1512398352.0,
  'topic': 'org.fedoraproject.prod.compose.28.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.28.complete
fedmsg.meta.msg2subtitle() Completed Fedora-Docker 28 compose Fedora-Docker-28-20180126.n.0
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/Fedora-Docker-28-20180126.n.0
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘28/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.28.rsync.complete

The release engineering “compose” scripts produce these messages when they have finished syncing out a compose for a numbered release. This could be a Branched compose, or a post-release two-week Atomic, Docker, or Cloud compose: the ‘short’ and ‘compose_id’ values can be used to differentiate. The message topic obviously differs based on the release, this one is only an example.

You can view the history of messages with the compose.28.rsync.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': '28',
           'compose_id': 'Fedora-Cloud-28-20180126.n.0',
           'location': 'https://kojipkgs.fedoraproject.org/compose/Fedora-Cloud-28-20180126.n.0',
           'log': 'done',
           'short': 'Fedora-Cloud'},
  'timestamp': 1512313750.0,
  'topic': 'org.fedoraproject.prod.compose.28.rsync.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.28.rsync.complete
fedmsg.meta.msg2subtitle() Completed master mirror publication for Fedora-Cloud 28 compose Fedora-Cloud-28-20180126.n.0
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/Fedora-Cloud-28-20180126.n.0
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘28/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.28.rsync.start

The release engineering “compose” scripts produce these messages when they have started syncing out a compose for a numbered release. This could be a Branched compose, or a post-release two-week Atomic, Docker, or Cloud compose: the ‘short’ and ‘compose_id’ values can be used to differentiate. The message topic obviously differs based on the release, this one is only an example.

You can view the history of messages with the compose.28.rsync.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': '28',
           'compose_id': 'Fedora-Atomic-28-20171215.n.0',
           'log': 'start',
           'short': 'Fedora-Atomic'},
  'timestamp': 1512395453.0,
  'topic': 'org.fedoraproject.prod.compose.28.rsync.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.28.rsync.start
fedmsg.meta.msg2subtitle() Started master mirror publication for Fedora-Atomic 28 compose Fedora-Atomic-28-20171215.n.0
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘28/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.28.start

The release engineering “compose” scripts produce these messages when they have started a compose for a numbered release. This could be a Branched compose, or a post-release two-week Atomic, Docker, or Cloud compose: the ‘short’ and ‘compose_id’ values can be used to differentiate. The message topic obviously differs based on the release, this one is only an example.

You can view the history of messages with the compose.28.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '28', 'log': 'start', 'short': 'Fedora'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.28.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.28.start
fedmsg.meta.msg2subtitle() Started Fedora 28 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘28/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.bikeshed.complete

The release engineering “compose” scripts produce these messages when they have finished a ‘bikeshed’ compose (basically like a Rawhide compose, but for modular).

You can view the history of messages with the compose.bikeshed.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': 'bikeshed',
           'compose_id': 'Fedora-Modular-Bikeshed-20171208.n.0',
           'log': 'done',
           'short': 'Fedora-Modular'},
  'timestamp': 1512756914.0,
  'topic': 'org.fedoraproject.prod.compose.bikeshed.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.bikeshed.complete
fedmsg.meta.msg2subtitle() Completed Fedora-Modular Bikeshed compose Fedora-Modular-Bikeshed-20171208.n.0
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘bikeshed/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.bikeshed.start

The release engineering “compose” scripts produce these messages when they have started a ‘bikeshed’ compose (basically like a Rawhide compose, but for modular).

You can view the history of messages with the compose.bikeshed.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': 'bikeshed',
           'log': 'start',
           'short': 'Fedora-Modular'},
  'msg_id': '2017-7e497c3e-14b6-497f-a016-79cf9b591585',
  'timestamp': 1512756914.0,
  'topic': 'org.fedoraproject.prod.compose.bikeshed.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.bikeshed.start
fedmsg.meta.msg2subtitle() Started Fedora-Modular Bikeshed compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘bikeshed/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.complete

The release engineering “compose” scripts used to produce these messages when they finished composing whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, instead the topic for messages related to Branched composes will include the release number (e.g. ‘compose.27.complete’).

You can view the history of messages with the compose.branched.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.complete
fedmsg.meta.msg2subtitle() Completed Fedora 18 compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.image.complete

The release engineering “compose” scripts used to produce these messages when they finished building live, cloud and disk images for whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no image build messages published by the current compose process.

You can view the history of messages with the compose.branched.image.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.image.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.image.complete
fedmsg.meta.msg2subtitle() Completed building other images for Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.image.start

The release engineering “compose” scripts used to produce these messages when they started building live, cloud and disk images for whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no image build messages published by the current compose process.

You can view the history of messages with the compose.branched.image.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.image.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.image.start
fedmsg.meta.msg2subtitle() Started building other images for Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.mash.complete

The release engineering “compose” scripts used to produce these messages when they finished mashing whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no mash-related messages published by the current compose process.

You can view the history of messages with the compose.branched.mash.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.mash.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.mash.complete
fedmsg.meta.msg2subtitle() Completed mashing Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.mash.start

The release engineering “compose” scripts used to produce these messages when they began mashing whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no mash-related messages published by the current compose process.

You can view the history of messages with the compose.branched.mash.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.mash.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.mash.start
fedmsg.meta.msg2subtitle() Started mashing Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.pungify.complete

The release engineering “compose” scripts used to produce these messages when they finished creating a boot.iso for whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no pungify messages published by the current compose process.

You can view the history of messages with the compose.branched.pungify.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.pungify.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.pungify.complete
fedmsg.meta.msg2subtitle() Completed building boot.iso for Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.pungify.start

The release engineering “compose” scripts used to produce these messages when they started creating a boot.iso for whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no pungify messages published by the current compose process.

You can view the history of messages with the compose.branched.pungify.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.pungify.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.pungify.start
fedmsg.meta.msg2subtitle() Started building boot.iso for Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.rsync.complete

The release engineering “compose” scripts used to produce these messages when they finished syncing out (publishing, effectively) whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, instead the topic for messages related to Branched composes will include the release number (e.g. ‘compose.27.rsync.complete’).

You can view the history of messages with the compose.branched.rsync.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.rsync.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.rsync.complete
fedmsg.meta.msg2subtitle() Completed master mirror publication for Fedora 18 compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.rsync.start

The release engineering “compose” scripts used to produce these messages when they began syncing out (publishing, effectively) whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, instead the topic for messages related to Branched composes will include the release number (e.g. ‘compose.27.rsync.start’).

You can view the history of messages with the compose.branched.rsync.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.rsync.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.rsync.start
fedmsg.meta.msg2subtitle() Started master mirror publication for Fedora 18 compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.branched.start

The release engineering “compose” scripts used to produce these messages when they began composing whatever the current branched distribution version was. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, instead the topic for messages related to Branched composes will include the release number (e.g. ‘compose.27.start’).

You can view the history of messages with the compose.branched.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': '18', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.branched.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.branched.start
fedmsg.meta.msg2subtitle() Started Fedora 18 compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘branched/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.epelbeta.complete

The release engineering “compose” scripts used to produce these messages when they had finished an EPEL 7 Beta compose (while RHEL 7 was in Beta state).

You can view the history of messages with the compose.epelbeta.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.epelbeta.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.epelbeta.complete
fedmsg.meta.msg2subtitle() Completed Fedora EPEL Beta compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘epelbeta/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.epelbeta.start

The release engineering “compose” scripts used to produce these messages when they had started an EPEL 7 Beta compose (while RHEL 7 was in Beta state).

You can view the history of messages with the compose.epelbeta.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.epelbeta.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.epelbeta.start
fedmsg.meta.msg2subtitle() Started Fedora EPEL Beta compose
fedmsg.meta.msg2link() https://kojipkgs.fedoraproject.org/compose/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘epelbeta/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.complete

The release engineering “compose” scripts produce these messages when they have finished a rawhide compose.

You can view the history of messages with the compose.rawhide.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': 'rawhide',
           'compose_id': 'Fedora-Rawhide-20180126.n.0',
           'location': 'https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide',
           'log': 'done',
           'short': 'Fedora'},
  'timestamp': 1512398352.0,
  'topic': 'org.fedoraproject.prod.compose.rawhide.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.complete
fedmsg.meta.msg2subtitle() Completed Fedora Rawhide compose Fedora-Rawhide-20180126.n.0
fedmsg.meta.msg2link() https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.image.complete

The release engineering “compose” scripts used to produce these messages when they finished building live, cloud and disk images for for the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no image build messages published by the current compose process.

You can view the history of messages with the compose.rawhide.image.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.image.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.image.complete
fedmsg.meta.msg2subtitle() Completed building other images for Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.image.start

The release engineering “compose” scripts used to produce these messages when they started building live, cloud and disk images for for the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no image build messages published by the current compose process.

You can view the history of messages with the compose.rawhide.image.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.image.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.image.start
fedmsg.meta.msg2subtitle() Started building other images for Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.mash.complete

The release engineering “compose” scripts used to produce these messages when they finished mashing the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no mash-related messages published by the current compose process.

You can view the history of messages with the compose.rawhide.mash.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.mash.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.mash.complete
fedmsg.meta.msg2subtitle() Completed mashing Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.mash.start

The release engineering “compose” scripts used to produce these messages when they started mashing the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no mash-related messages published by the current compose process.

You can view the history of messages with the compose.rawhide.mash.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.mash.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.mash.start
fedmsg.meta.msg2subtitle() Started mashing Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.pungify.complete

The release engineering “compose” scripts used to produce these messages when they finished creating a boot.iso for the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no pungify messages published by the current compose process.

You can view the history of messages with the compose.rawhide.pungify.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'done'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.pungify.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.pungify.complete
fedmsg.meta.msg2subtitle() Completed building boot.iso for Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.pungify.start

The release engineering “compose” scripts used to produce these messages when they started creating a boot.iso for the rawhide compose. They were published for both primary and secondary architectures. The example here is of a primary arch message (the empty string signifies primary). Messages with this topic are not currently published, and there are no pungify messages published by the current compose process.

You can view the history of messages with the compose.rawhide.pungify.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'start'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.pungify.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.pungify.start
fedmsg.meta.msg2subtitle() Started building boot.iso for Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.rsync.complete

The release engineering “compose” scripts produce these messages when they have finished syncing out a completed rawhide compose.

You can view the history of messages with the compose.rawhide.rsync.complete topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': 'rawhide',
           'compose_id': 'Fedora-Rawhide-20180126.n.0',
           'location': 'https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide',
           'log': 'done',
           'short': 'Fedora'},
  'timestamp': 1512313750.0,
  'topic': 'org.fedoraproject.prod.compose.rawhide.rsync.complete'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.rsync.complete
fedmsg.meta.msg2subtitle() Completed master mirror publication for Fedora Rawhide compose Fedora-Rawhide-20180126.n.0
fedmsg.meta.msg2link() https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.rsync.start

The release engineering “compose” scripts produce these messages when they have started syncing out a completed rawhide compose.

You can view the history of messages with the compose.rawhide.rsync.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '',
           'branch': 'rawhide',
           'compose_id': 'Fedora-Rawhide-20180126.n.0',
           'log': 'start',
           'short': 'Fedora'},
  'timestamp': 1512395453.0,
  'topic': 'org.fedoraproject.prod.compose.rawhide.rsync.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.rsync.start
fedmsg.meta.msg2subtitle() Started master mirror publication for Fedora Rawhide compose Fedora-Rawhide-20180126.n.0
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

compose.rawhide.start

The release engineering “compose” scripts produce these messages when they have started the rawhide compose.

You can view the history of messages with the compose.rawhide.start topic or all compose messages in datagrepper.

{ 'i': 1,
  'msg': { 'arch': '', 'branch': 'rawhide', 'log': 'start', 'short': 'Fedora'},
  'timestamp': 1344447839.891876,
  'topic': 'org.fedoraproject.prod.compose.rawhide.start'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() compose.rawhide.start
fedmsg.meta.msg2subtitle() Started Fedora Rawhide compose
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘rawhide/primary’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

copr

copr.build.end

Copr publishes these messages when a build has completed. This is an example of a build that completed successfully.

You can view the history of messages with the copr.build.end topic or all copr messages in datagrepper.

{ u'i': 4,
  u'msg': { u'build': 100,
            u'chroot': u'fedora-20-x86_64',
            u'copr': u'mutt-kz',
            u'ip': u'172.16.3.3',
            u'pid': 12010,
            u'pkg': 'mutt-kz-1.5.23.1-1.20150203.git.c8504a8a.fc21',
            u'status': 1,
            u'user': u'fatka',
            u'version': '1.5.23.1-1.20150203.git.c8504a8a.fc21',
            u'what': u'build end: user:fatka copr:mutt-kz build:100 ip:172.16.3.3  pid:12010 status:1',
            u'who': u'worker-2'},
  u'msg_id': u'2013-b05a323d-37ee-4396-9635-7b5dfaf5441b',
  u'timestamp': 1383956707.634,
  u'topic': u'org.fedoraproject.prod.copr.build.end',
  u'username': u'copr'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.build.end
fedmsg.meta.msg2subtitle() fatka’s mutt-kz copr build of mutt-kz-1.5.23.1-1.20150203.git.c8504a8a.fc21 for fedora-20-x86_64 finished with ‘success’
fedmsg.meta.msg2link() https://copr.fedoraproject.org/coprs/fatka/mutt-kz/build/100/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fatka’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/mutt-kz/build.end’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 303e77d9-5905-4021-b02b-734f2a4b6f85-secondary_icon

copr.build.end

Copr publishes these messages when a build has completed. This is an example of a build that completed successfully.

You can view the history of messages with the copr.build.end topic or all copr messages in datagrepper.

{ u'i': 4,
  u'msg': { u'build': 100,
            u'chroot': u'fedora-20-x86_64',
            u'copr': u'mutt-kz',
            u'ip': u'172.16.3.3',
            u'pid': 12010,
            u'pkg': 'mutt-kz',
            u'status': 1,
            u'user': u'fatka',
            u'version': '1.5.23.1',
            u'what': u'build end: user:fatka copr:mutt-kz build:100 ip:172.16.3.3  pid:12010 status:1',
            u'who': u'worker-2'},
  u'msg_id': u'2013-b05a323d-37ee-4396-9635-7b5dfaf5441b',
  u'timestamp': 1383956707.634,
  u'topic': u'org.fedoraproject.prod.copr.build.end',
  u'username': u'copr'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.build.end
fedmsg.meta.msg2subtitle() fatka’s mutt-kz copr build of mutt-kz-1.5.23.1 for fedora-20-x86_64 finished with ‘success’
fedmsg.meta.msg2link() https://copr.fedoraproject.org/coprs/fatka/mutt-kz/build/100/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fatka’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/mutt-kz/build.end’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 811dc347-e635-4a23-81be-7def925891f8-secondary_icon

copr.build.end

Copr publishes these messages when a build has completed. This is an example of a build that failed.

You can view the history of messages with the copr.build.end topic or all copr messages in datagrepper.

{ 'msg': { 'build': 80794,
           'chroot': 'fedora-21-x86_64',
           'copr': 'glib2',
           'ip': '172.16.3.5',
           'owner': 'brianjmurrell',
           'pid': 9363,
           'pkg': 'glib2',
           'status': 0,
           'user': 'brianjmurrell',
           'version': '2.42.2-1.01.fc21',
           'what': 'build end: user:brianjmurrell copr:glib2 build:80794    pkg: glib2-2.42.2-1.01.fc21    version: 2.42.2-1.01.fc21 ip:172.16.3.5    pid:9363 status:0',
           'who': 'worker-4'},
  'msg_id': '2015-f3152f3c-5075-422e-af94-96c692454c81',
  'timestamp': 1425653769.0,
  'topic': 'org.fedoraproject.prod.copr.build.end'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.build.end
fedmsg.meta.msg2subtitle() brianjmurrell’s glib2 copr build of glib2-2.42.2-1.01.fc21 for fedora-21-x86_64 finished with ‘failed’
fedmsg.meta.msg2link() https://copr.fedoraproject.org/coprs/brianjmurrell/glib2/build/80794/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘brianjmurrell’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/glib2/build.end’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 5380102c-1ca2-44e9-8ffb-2a2056fd3e95-secondary_icon

copr.build.end

Copr publishes these messages when a build has completed. This is an example of a group repo.

You can view the history of messages with the copr.build.end topic or all copr messages in datagrepper.

{ u'i': 3,
  u'msg': { u'build': 450811,
            u'chroot': u'fedora-23-i386',
            u'copr': u'python26',
            u'ip': u'172.25.83.110',
            u'owner': u'@python',
            u'pid': 7513,
            u'pkg': u'python26',
            u'status': 0,
            u'user': u'churchyard',
            u'version': u'2.6.9-1.fc26',
            u'what': u'build end: user:churchyard copr:python26 build:450811  pkg: python26  version: 2.6.9-1.fc26 ip:172.25.83.110  pid:7513 status:0',
            u'who': u'backend.worker-6023-PC'},
  u'msg_id': u'2016-31e1e282-c176-4a9e-94bc-e4ae34536d47',
  u'source_name': u'datanommer',
  u'source_version': u'0.6.5',
  u'timestamp': 1473355790.0,
  u'topic': u'org.fedoraproject.prod.copr.build.end'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.build.end
fedmsg.meta.msg2subtitle() churchyard’s python26 copr build of python26-2.6.9-1.fc26 for fedora-23-i386 finished with ‘failed’
fedmsg.meta.msg2link() https://copr.fedoraproject.org/coprs/g/python/python26/build/450811/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() Unspecified
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() Unspecified
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

copr.build.start

Copr publishes these messages when a new build starts.

You can view the history of messages with the copr.build.start topic or all copr messages in datagrepper.

{ u'i': 1,
  u'msg': { u'build': 100,
            u'copr': u'mutt-kz',
            u'ip': u'172.16.3.3',
            u'pid': 12010,
            u'user': u'fatka',
            u'what': u'build start: user:fatka copr:mutt-kz build:100 ip:172.16.3.3  pid:12010',
            u'who': u'worker-2'},
  u'msg_id': u'2013-675e7b1e-9b7f-4d11-be2f-2b3845817d60',
  u'timestamp': 1383956077.232,
  u'topic': u'org.fedoraproject.prod.copr.build.start',
  u'username': u'copr'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.build.start
fedmsg.meta.msg2subtitle() fatka started a new build of the mutt-kz copr
fedmsg.meta.msg2link() https://copr.fedoraproject.org/coprs/fatka/mutt-kz/build/100/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fatka’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/mutt-kz/build.start’])
fedmsg.meta.msg2icon() da79a21a-c86b-4db8-a1c1-7c711f8f9469-icon
fedmsg.meta.msg2secondary_icon() da79a21a-c86b-4db8-a1c1-7c711f8f9469-secondary_icon

copr.chroot.start

Copr publishes these messages when a copr start a new chroot.

You can view the history of messages with the copr.chroot.start topic or all copr messages in datagrepper.

{ u'i': 3,
  u'msg': { u'build': 100,
            u'chroot': u'fedora-20-x86_64',
            u'copr': u'mutt-kz',
            u'ip': u'172.16.3.3',
            u'pid': 12010,
            u'user': u'fatka',
            u'what': u'chroot start: chroot:fedora-20-x86_64 user:fatka copr:mutt-kz build:100 ip:172.16.3.3  pid:12010',
            u'who': u'worker-2'},
  u'msg_id': u'2013-833cca09-2dba-42ad-9863-4f6c3c29a30d',
  u'timestamp': 1383956378.468,
  u'topic': u'org.fedoraproject.prod.copr.chroot.start',
  u'username': u'copr'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.chroot.start
fedmsg.meta.msg2subtitle() fatka’s mutt-kz copr started a new fedora-20-x86_64 chroot
fedmsg.meta.msg2link() https://copr-be.cloud.fedoraproject.org/results/fatka/mutt-kz/fedora-20-x86_64/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘fatka’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/mutt-kz/chroot.start/fedora-20-x86_64’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 1efac4a2-2897-4138-a6e2-98c558412b03-secondary_icon

copr.worker.create

Copr publishes these messages when a new worker is spun up.

You can view the history of messages with the copr.worker.create topic or all copr messages in datagrepper.

{ u'i': 1,
  u'msg': { u'ip': u'172.16.3.3', u'what': u'creating worker: 172.16.3.3'},
  u'msg_id': u'2013-675e7b1e-9b7f-4d11-be2f-2b3845817d60',
  u'timestamp': 1383956077.232,
  u'topic': u'org.fedoraproject.prod.copr.worker.create',
  u'username': u'copr'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() copr.worker.create
fedmsg.meta.msg2subtitle() a new worker was created
fedmsg.meta.msg2link() https://copr.fedoraproject.org
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘coprs/worker.create’])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() Unspecified

datanommer

datanommer.wat

Generally speaking, the datanommer consumer does not publish its own fedmsg messages. There is one exception to this rule.

As of fedmsg-0.7.0, every fedmsg carries its own uuid, prefixed with the year it was published. There is a very low risk of creating a duplicate uuid. To quote wikipedia:

"The annual risk of someone being hit by a meteorite is estimated to be
one chance in 17 billion, which means the probability is about
``0.00000000006 (6 * 10**-11)``, equivalent to the odds of creating a
few tens of trillions of UUIDs in a year and having one duplicate"

It is highly unlikely that datanommer will ever try to store a fedmsg message that carries a uuid that already exists in its database. In the event that it does, it will publish the following message; a momentous occasion.

You can view the history of messages with the datanommer.wat topic or all datanommer messages in datagrepper.

{ 'i': 1,
  'msg': { 'uuid': '2013-3bf0ec8f-03d3-40be-9ad5-5effdc6e4c06'},
  'timestamp': 1375753735.32427,
  'topic': 'org.fedoraproject.prod.datanommer.wat',
  'username': 'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() datanommer.wat
fedmsg.meta.msg2subtitle() datanommer encountered a duplicate uuid
fedmsg.meta.msg2link() https://www.destroyallsoftware.com/talks/wat
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘wat’])
fedmsg.meta.msg2icon() f6731423-aef1-4973-8b61-5012ae15cd00-icon
fedmsg.meta.msg2secondary_icon() f6731423-aef1-4973-8b61-5012ae15cd00-secondary_icon

faf

faf.problem.threshold10

ABRT server notifies about a problem

You can view the history of messages with the faf.problem.threshold10 topic or all faf messages in datagrepper.

{ u'i': 1,
  u'msg': { u'components': [u'evolution', u'thunderbird'],
            u'count': 77,
            u'first_occurrence': u'2015-04-10',
            u'function': u'main',
            u'level': 1,
            u'problem_id': 4321,
            u'type': u'core',
            u'url': u'http://example.org/faf/problems/4321/'},
  u'msg_id': u'2015-0284a675-995a-4942-bc59-2a5384e892b7',
  u'timestamp': 1429777247,
  u'topic': u'org.fedoraproject.prod.faf.problem.threshold10',
  u'username': u'faf'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() faf.problem.threshold10
fedmsg.meta.msg2subtitle() ABRT problem for package evolution, thunderbird has reached 77 occurrences
fedmsg.meta.msg2link() http://example.org/faf/problems/4321/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘evolution’, ‘thunderbird’])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() 6ebb8c02-25e4-4dd2-8f0c-66b31c841b54-secondary_icon

faf.report.threshold1

ABRT server notifies about a crash report

You can view the history of messages with the faf.report.threshold1 topic or all faf messages in datagrepper.

{ u'i': 1,
  u'msg': { u'components': [u'evolution'],
            u'count': 7,
            u'first_occurrence': u'2015-04-10',
            u'function': u'main',
            u'level': 1,
            u'problem_id': 4321,
            u'report_id': 1234,
            u'type': u'core',
            u'url': u'http://example.org/faf/reports/1234/'},
  u'msg_id': u'2015-0284a675-995a-4942-bc59-2a5384e892b7',
  u'timestamp': 1429777247,
  u'topic': u'org.fedoraproject.prod.faf.report.threshold1',
  u'username': u'faf'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() faf.report.threshold1
fedmsg.meta.msg2subtitle() ABRT report for package evolution has reached 7 occurrences
fedmsg.meta.msg2link() http://example.org/faf/reports/1234/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([‘evolution’])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() Unspecified
fedmsg.meta.msg2secondary_icon() c5e0c0c7-59b1-4017-8e79-66cbfb267f4c-secondary_icon

fas

fas.group.create

The Fedora Account System publishes messages on this topic whenever a new group is created.

You can view the history of messages with the fas.group.create topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'ralph', u'group': u'ambassadors'},
  u'topic': u'org.fedoraproject.prod.fas.group.create'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.group.create
fedmsg.meta.msg2subtitle() ralph created new FAS group ambassadors
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’])
fedmsg.meta.msg2icon() 108b73d8-1201-47e1-9d81-e3eac692a75c-icon
fedmsg.meta.msg2secondary_icon() 108b73d8-1201-47e1-9d81-e3eac692a75c-secondary_icon

fas.group.member.apply

The Fedora Account System publishes messages on this topic whenever a user requests to join a particular group.

You can view the history of messages with the fas.group.member.apply topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'ralph', u'group': u'ambassadors', u'user': u'ralph'},
  u'topic': u'org.fedoraproject.prod.fas.group.member.apply'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.group.member.apply
fedmsg.meta.msg2subtitle() ralph applied for ralph’s membership in the ambassadors group
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’, ‘users/ralph’])
fedmsg.meta.msg2icon() 48f08398-946e-4183-92cf-860c88dc14c5-icon
fedmsg.meta.msg2secondary_icon() 48f08398-946e-4183-92cf-860c88dc14c5-secondary_icon

fas.group.member.remove

The Fedora Account System publishes messages on this topic whenever a user is removed from a particular group.

You can view the history of messages with the fas.group.member.remove topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'toshio', u'group': u'ambassadors', u'user': u'ralph'},
  u'topic': u'org.fedoraproject.prod.fas.group.member.remove'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.group.member.remove
fedmsg.meta.msg2subtitle() toshio removed ralph from the ambassadors group
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘toshio’, ‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’, ‘users/ralph’])
fedmsg.meta.msg2icon() 9e57dce4-1a77-4273-8eb3-cd2dea7d77b2-icon
fedmsg.meta.msg2secondary_icon() 9e57dce4-1a77-4273-8eb3-cd2dea7d77b2-secondary_icon

fas.group.member.sponsor

The Fedora Account System publishes messages on this topic whenever a user’s request to join a restricted group is sponsored by an authorized user.

You can view the history of messages with the fas.group.member.sponsor topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'toshio', u'group': u'ambassadors', u'user': u'ralph'},
  u'topic': u'org.fedoraproject.prod.fas.group.member.sponsor'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.group.member.sponsor
fedmsg.meta.msg2subtitle() toshio sponsored ralph’s membership in the ambassadors group
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘toshio’, ‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’, ‘users/ralph’])
fedmsg.meta.msg2icon() a31c2e1d-8ed5-4d71-b77a-1279e117d8d0-icon
fedmsg.meta.msg2secondary_icon() a31c2e1d-8ed5-4d71-b77a-1279e117d8d0-secondary_icon

fas.group.update

The Fedora Account System publishes messages on this topic whenever a group’s properties are modified. For example:

You can view the history of messages with the fas.group.update topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'ralph',
            u'fields': [u'display_name'],
            u'group': u'ambassadors'},
  u'topic': u'org.fedoraproject.prod.fas.group.update'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.group.update
fedmsg.meta.msg2subtitle() ralph edited the following fields of the ambassadors FAS group: display_name
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’])
fedmsg.meta.msg2icon() 9f903021-58f6-4d7d-afdb-d9bd143027ed-icon
fedmsg.meta.msg2secondary_icon() 9f903021-58f6-4d7d-afdb-d9bd143027ed-secondary_icon

fas.role.update

The Fedora Account System publishes messages on this topic whenever a user’s role in a particular group changes.

You can view the history of messages with the fas.role.update topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'toshio',
            u'group': u'ambassadors',
            u'status': u'sponsor',
            u'user': u'ralph'},
  u'topic': u'org.fedoraproject.prod.fas.role.update'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.role.update
fedmsg.meta.msg2subtitle() toshio changed ralph’s role in the ambassadors group to sponsor
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘toshio’, ‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘groups/ambassadors’, ‘users/ralph’])
fedmsg.meta.msg2icon() 0d18ddb4-e678-449f-8418-9544b9d63101-icon
fedmsg.meta.msg2secondary_icon() 0d18ddb4-e678-449f-8418-9544b9d63101-secondary_icon

fas.user.create

The Fedora Account System publishes messages on this topic whenever a new user account is created.

You can view the history of messages with the fas.user.create topic or all fas messages in datagrepper.

{ u'i': 1,
  u'msg': { u'agent': u'ralph', u'user': u'ralph'},
  u'timestamp': 1344432054.809861,
  u'topic': u'org.fedoraproject.prod.fas.user.create'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.user.create
fedmsg.meta.msg2subtitle() New FAS account: ‘ralph’ (created by ‘ralph’)
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘users/ralph’])
fedmsg.meta.msg2icon() 474eca0b-18bf-4084-884c-09b94ab71434-icon
fedmsg.meta.msg2secondary_icon() 474eca0b-18bf-4084-884c-09b94ab71434-secondary_icon

fas.user.update

The Fedora Account System publishes messages on this topic whenever a user’s account is modified. Information about which account, what fields changed, and who did the changing are included in the message body. For example:

You can view the history of messages with the fas.user.update topic or all fas messages in datagrepper.

{ u'msg': { u'agent': u'ralph', u'fields': [u'comments'], u'user': u'ralph'},
  u'topic': u'org.fedoraproject.prod.fas.user.update'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fas.user.update
fedmsg.meta.msg2subtitle() ralph edited the following fields of ralph’s FAS profile: comments
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() Unspecified
fedmsg.meta.msg2objects() set([‘users/ralph’])
fedmsg.meta.msg2icon() f993b864-3739-4c59-a951-615cc9e63788-icon
fedmsg.meta.msg2secondary_icon() f993b864-3739-4c59-a951-615cc9e63788-secondary_icon

fedbadges

fedbadges.badge.award

These messages are published when Open Badges are awarded to Fedora Contributors by the fedbadges backend.

You can view the history of messages with the fedbadges.badge.award topic or all fedbadges messages in datagrepper.

{ u'i': 1,
  u'msg': { u'badge': { u'creator': u'ralph',
                        u'criteria': { u'datanommer': { u'condition': { u'greater than or equal to': 2},
                                                        u'filter': { u'topics': [ u'{topic}']},
                                                        u'operation': u'count'}},
                        u'description': u'You have commented on 2 or more bodhi updates.',
                        u'discussion': u'http://github.com/fedora-infra/badges/pull/SOME_NUMBER',
                        u'image_url': u'http://example.com/image.png',
                        u'issuer_id': u'fedora-project',
                        u'name': u'Something on your mind',
                        u'trigger': { u'topic': u'org.fedoraproject.stg.bodhi.update.comment'}},
            u'user': { u'badges_user_id': 1, u'username': u'ralph'}},
  u'timestamp': 1371498303.125771,
  u'topic': u'org.fedoraproject.prod.fedbadges.badge.award',
  u'username': u'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedbadges.badge.award
fedmsg.meta.msg2subtitle() ralph has been awarded the “Something on your mind” badge
fedmsg.meta.msg2link() https://badges.fedoraproject.org/user/ralph
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘something-on-your-mind’])
fedmsg.meta.msg2icon() 262761ef-32a8-4d6c-b1a3-b454ff19743d-icon
fedmsg.meta.msg2secondary_icon() 262761ef-32a8-4d6c-b1a3-b454ff19743d-secondary_icon

fedbadges.person.login.first

When a user logs in to the Fedora Badges site for the very first time, we publish a message like this one.

You can view the history of messages with the fedbadges.person.login.first topic or all fedbadges messages in datagrepper.

{ 'i': 2,
  'msg': { 'user': { 'badges_user_id': 2, 'username': 'ralph'}},
  'msg_id': '2013-be88d409-cdd7-47f0-9edd-87088f8505d2',
  'source_name': 'datanommer',
  'source_version': '0.6.0',
  'timestamp': 1382804277.0,
  'topic': 'org.fedoraproject.prod.fedbadges.person.login.first'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedbadges.person.login.first
fedmsg.meta.msg2subtitle() ralph logged in to badges.fedoraproject.org for the first time
fedmsg.meta.msg2link() https://badges.fedoraproject.org/user/ralph
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() 704ab6b8-eff3-47d3-bc74-d36ecf64ac95-icon
fedmsg.meta.msg2secondary_icon() 704ab6b8-eff3-47d3-bc74-d36ecf64ac95-secondary_icon

fedbadges.person.rank.advance

When a user’s rank on the leaderboard of the Fedora Badges system increases, this message gets published.

You can view the history of messages with the fedbadges.person.rank.advance topic or all fedbadges messages in datagrepper.

{ 'i': 4,
  'msg': { 'old_rank': None,
           'person': { 'bio': None,
                       'email': 'ralph@fedoraproject.org',
                       'id': 1600,
                       'nickname': 'ralph',
                       'rank': 1500,
                       'website': None}},
  'timestamp': 1377701575.214381,
  'topic': 'org.fedoraproject.prod.fedbadges.person.rank.advance',
  'username': 'fedmsg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedbadges.person.rank.advance
fedmsg.meta.msg2subtitle() ralph moved to position 1500 on the badges leaderboard
fedmsg.meta.msg2link() https://badges.fedoraproject.org/user/ralph
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() 1eadd1e9-a29e-457b-bf1c-b5fe854abe00-icon
fedmsg.meta.msg2secondary_icon() 1eadd1e9-a29e-457b-bf1c-b5fe854abe00-secondary_icon

fedimg

fedimg.image.copy

These messages are published when an image has been copied to other
region from the base region.

You can view the history of messages with the fedimg.image.copy topic or all fedimg messages in datagrepper.

{ u'i': 1,
  u'msg': { 'compose_id': 'Fedora-Atomic-27-20180507.0',
            'destination': 'us-west-2',
            'extra': { 'id': 'ami-2e80f656',
                       'source_image_id': 'ami-991999e6',
                       'virt_type': 'hvm',
                       'vol_type': 'gp2'},
            'image_name': 'Fedora-Atomic-27-20180507.0.x86_64',
            'service': 'EC2'},
  u'timestamp': 1371498303.125771,
  u'topic': u'org.fedoraproject.prod.fedimg.image.copy',
  u'username': u'fedimg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedimg.image.copy
fedmsg.meta.msg2subtitle() Fedora-Atomic-27-20180507.0.x86_64 copied to us-west-2 using source image, ami-991999e6 (ami-2e80f656, hvm, gp2)
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() 74fcb1c5-4813-4c12-829f-b5e66b29e1d9-icon
fedmsg.meta.msg2secondary_icon() 74fcb1c5-4813-4c12-829f-b5e66b29e1d9-secondary_icon

fedimg.image.publish

These messages are published when an image and snapshot is made public.

You can view the history of messages with the fedimg.image.publish topic or all fedimg messages in datagrepper.

{ u'i': 1,
  u'msg': { 'compose': 'Fedora-Atomic-27-20180507.0',
            'destination': 'eu-west-2',
            'extra': { 'id': 'ami-d813f1bf',
                       'virt_type': 'hvm',
                       'vol_type': 'gp2'},
            'image_name': 'Fedora-Atomic-27-20180507.0.x86_64',
            'image_url': None,
            'service': 'EC2'},
  u'timestamp': 1371498303.125771,
  u'topic': u'org.fedoraproject.prod.fedimg.image.publish',
  u'username': u'fedimg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedimg.image.publish
fedmsg.meta.msg2subtitle() Fedora-Atomic-27-20180507.0.x86_64 published in region, eu-west-2 (ami-d813f1bf, hvm, gp2)
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([])
fedmsg.meta.msg2icon() 1bd910cc-4b62-4880-ab0a-82071e02fa60-icon
fedmsg.meta.msg2secondary_icon() 1bd910cc-4b62-4880-ab0a-82071e02fa60-secondary_icon

fedimg.image.upload

These messages are published when an image upload finishes.
At this point, Fedimg has completed registering a .raw.xz image with a cloud provider.

You can view the history of messages with the fedimg.image.upload topic or all fedimg messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose': { u'compose_id': 'Fedora-Atomic-24-20160710.0'},
            u'destination': 'eu-west-1',
            u'extra': { u'id': 'ami-1234fda',
                        u'virt_type': 'HVM',
                        u'vol_type': 'gp2'},
            u'image_name': 'Fedora-Cloud-Base-24-20160710.0.x86_64',
            u'image_url': 'http://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-20160710.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-24-20160710.0.x86_64.raw.xz',
            u'status': 'completed'},
  u'timestamp': 1371498303.125771,
  u'topic': u'org.fedoraproject.prod.fedimg.image.upload',
  u'username': u'fedimg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedimg.image.upload
fedmsg.meta.msg2subtitle() Fedora-Cloud-Base-24-20160710.0.x86_64 finished uploading to eu-west-1 (ami-1234fda, HVM, gp2)
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘image/upload/completed’])
fedmsg.meta.msg2icon() 50b83b76-e19d-4f6c-8978-81548780c8bd-icon
fedmsg.meta.msg2secondary_icon() 50b83b76-e19d-4f6c-8978-81548780c8bd-secondary_icon

fedimg.image.upload

These messages are published when an image upload has started. Fedimg picks up this message when a compose finishes and will begin the process of registering the .raw.xz file as as an image with a cloud provider.

You can view the history of messages with the fedimg.image.upload topic or all fedimg messages in datagrepper.

{ u'i': 1,
  u'msg': { u'compose': { u'compose_id': 'Fedora-Atomic-24-20160710.0'},
            u'destination': 'eu-west-1',
            u'image_name': 'Fedora-Cloud-Base-24-20160710.0.x86_64',
            u'image_url': 'http://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-20160710.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-24-20160710.0.x86_64.raw.xz',
            u'status': 'started'},
  u'timestamp': 1371498303.125771,
  u'topic': u'org.fedoraproject.prod.fedimg.image.upload',
  u'username': u'fedimg'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedimg.image.upload
fedmsg.meta.msg2subtitle() Fedora-Cloud-Base-24-20160710.0.x86_64 started uploading to eu-west-1
fedmsg.meta.msg2link() Unspecified
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘image/upload/started’])
fedmsg.meta.msg2icon() c6467677-649a-448b-b445-98d4536f5da0-icon
fedmsg.meta.msg2secondary_icon() c6467677-649a-448b-b445-98d4536f5da0-secondary_icon

fedocal

fedocal.calendar.clear

These messages are published when someone clears a calendar of all its meeting in fedocal.

You can view the history of messages with the fedocal.calendar.clear topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'}},
  'msg_id': '2013-96f9ca0e-c7c6-43f0-9de7-7a268c7f1cef',
  'timestamp': 1379638157.759283,
  'topic': 'org.fedoraproject.prod.fedocal.calendar.clear',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.calendar.clear
fedmsg.meta.msg2subtitle() ralph cleared the “awesome” calendar of all its meetings
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/awesome/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/clear’])
fedmsg.meta.msg2icon() bda70120-e4b7-40f3-9955-a65e740afed6-icon
fedmsg.meta.msg2secondary_icon() bda70120-e4b7-40f3-9955-a65e740afed6-secondary_icon

fedocal.calendar.delete

These messages are published when someone deletes a whole calendar from fedocal.

You can view the history of messages with the fedocal.calendar.delete topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'}},
  'msg_id': '2013-96f9ca0e-c7c6-43f0-9de7-7a268c7f1cef',
  'timestamp': 1379638157.759283,
  'topic': 'org.fedoraproject.prod.fedocal.calendar.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.calendar.delete
fedmsg.meta.msg2subtitle() ralph deleted the “awesome” calendar
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/awesome/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/delete’])
fedmsg.meta.msg2icon() e23cedc4-b71a-4cf8-bf39-6fda8482a5f7-icon
fedmsg.meta.msg2secondary_icon() e23cedc4-b71a-4cf8-bf39-6fda8482a5f7-secondary_icon

fedocal.calendar.new

These messages are published when someone creates a whole calendar from fedocal.

You can view the history of messages with the fedocal.calendar.new topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'}},
  'msg_id': '2013-96f9ca0e-c7c6-43f0-9de7-7a268c7f1cef',
  'timestamp': 1379638157.759283,
  'topic': 'org.fedoraproject.prod.fedocal.calendar.new',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.calendar.new
fedmsg.meta.msg2subtitle() ralph created a whole new “awesome” calendar
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/awesome/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/new’])
fedmsg.meta.msg2icon() 88b3ddf0-acbd-43a6-a437-69aeb262133b-icon
fedmsg.meta.msg2secondary_icon() 88b3ddf0-acbd-43a6-a437-69aeb262133b-secondary_icon

fedocal.calendar.update

These messages are published when someone updates a whole calendar from fedocal.

You can view the history of messages with the fedocal.calendar.update topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'}},
  'msg_id': '2013-96f9ca0e-c7c6-43f0-9de7-7a268c7f1cef',
  'timestamp': 1379638157.759283,
  'topic': 'org.fedoraproject.prod.fedocal.calendar.update',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.calendar.update
fedmsg.meta.msg2subtitle() ralph updated the “awesome” calendar
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/awesome/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/update’])
fedmsg.meta.msg2icon() a471c14c-2790-4758-b46a-d21c9489bca2-icon
fedmsg.meta.msg2secondary_icon() a471c14c-2790-4758-b46a-d21c9489bca2-secondary_icon

fedocal.calendar.upload

These messages are published when someone uploads an iCalendar file into a calendar of fedocal.

You can view the history of messages with the fedocal.calendar.upload topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'}},
  'msg_id': '2013-96f9ca0e-c7c6-43f0-9de7-7a268c7f1cef',
  'timestamp': 1379638157.759283,
  'topic': 'org.fedoraproject.prod.fedocal.calendar.upload',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.calendar.upload
fedmsg.meta.msg2subtitle() ralph uploaded an iCalendar file into the calendar “awesome”
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/awesome/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/upload’])
fedmsg.meta.msg2icon() 7c5df56d-a9f0-421a-a5ab-9a08932942ff-icon
fedmsg.meta.msg2secondary_icon() 7c5df56d-a9f0-421a-a5ab-9a08932942ff-secondary_icon

fedocal.meeting.delete

These messages are published when someone deletes a meeting from fedocal.

You can view the history of messages with the fedocal.meeting.delete topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'},
           'meeting': { 'calendar_name': 'awesome',
                        'meeting_date': '2013-09-20',
                        'meeting_date_end': '2013-09-21',
                        'meeting_id': 42,
                        'meeting_information': 'awesome',
                        'meeting_manager': 'ralph,',
                        'meeting_name': 'wat',
                        'meeting_region': None,
                        'meeting_time_start': '12:00:00',
                        'meeting_time_stop': '12:00:00',
                        'meeting_timezone': 'UTC'}},
  'msg_id': '2013-8d60e263-5c5f-40bb-86e0-241dc3965ba4',
  'timestamp': 1379638613.767245,
  'topic': 'org.fedoraproject.prod.fedocal.meeting.delete',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.meeting.delete
fedmsg.meta.msg2subtitle() ralph deleted the “wat” meeting from the “awesome” calendar
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/meeting/42/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/meetings/wat/delete’])
fedmsg.meta.msg2icon() 8364fb4f-0c8d-41a6-b478-af6758fd0a6d-icon
fedmsg.meta.msg2secondary_icon() 8364fb4f-0c8d-41a6-b478-af6758fd0a6d-secondary_icon

fedocal.meeting.new

These messages are published when someone creates a meeting from fedocal.

You can view the history of messages with the fedocal.meeting.new topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'},
           'meeting': { 'calendar_name': 'awesome',
                        'meeting_date': '2013-09-20',
                        'meeting_date_end': '2013-09-21',
                        'meeting_id': 42,
                        'meeting_information': 'awesome',
                        'meeting_manager': 'ralph,',
                        'meeting_name': 'wat',
                        'meeting_region': None,
                        'meeting_time_start': '12:00:00',
                        'meeting_time_stop': '12:00:00',
                        'meeting_timezone': 'UTC'}},
  'msg_id': '2013-8d60e263-5c5f-40bb-86e0-241dc3965ba4',
  'timestamp': 1379638613.767245,
  'topic': 'org.fedoraproject.prod.fedocal.meeting.new',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.meeting.new
fedmsg.meta.msg2subtitle() ralph created a “wat” meeting in the “awesome” calendar
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/meeting/42/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([‘ralph’])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/meetings/wat/new’])
fedmsg.meta.msg2icon() db37b5b1-1820-4b44-91b6-8a21249365cf-icon
fedmsg.meta.msg2secondary_icon() db37b5b1-1820-4b44-91b6-8a21249365cf-secondary_icon

fedocal.meeting.reminder

These messages are published by a cronjob when time gets close to certain meetings scheduled in the fedocal calendaring system.

You can view the history of messages with the fedocal.meeting.reminder topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status': 'Enabled'},
           'meeting': { 'calendar_name': 'awesome',
                        'meeting_date': '2018-06-11',
                        'meeting_date_end': '2013-09-21',
                        'meeting_id': 42,
                        'meeting_information': 'awesome',
                        'meeting_manager': 'ralph,',
                        'meeting_name': 'wat',
                        'meeting_region': None,
                        'meeting_time_start': '09:24:28',
                        'meeting_time_stop': '12:00:00',
                        'meeting_timezone': 'UTC'}},
  'msg_id': '2013-8d60e263-5c5f-40bb-86e0-241dc3965ba4',
  'timestamp': 1379638613.767245,
  'topic': 'org.fedoraproject.prod.fedocal.meeting.reminder',
  'username': 'threebean'}

The example message above, when passed to various routines in the fedmsg.meta module, will produce the following outputs:

fedmsg.meta.msg2title() fedocal.meeting.reminder
fedmsg.meta.msg2subtitle() Unspecified
fedmsg.meta.msg2link() https://apps.fedoraproject.org/calendar/meeting/42/
fedmsg.meta.msg2agent() Unspecified
fedmsg.meta.msg2usernames() set([])
fedmsg.meta.msg2packages() set([])
fedmsg.meta.msg2objects() set([‘awesome/meetings/wat/reminder’])
fedmsg.meta.msg2icon() 609b5725-eed8-4b7f-909c-66a582b02f9e-icon
fedmsg.meta.msg2secondary_icon() Unspecified

fedocal.meeting.update

These messages are published when someone updates a meeting from fedocal.

You can view the history of messages with the fedocal.meeting.update topic or all fedocal messages in datagrepper.

{ 'i': 1,
  'msg': { 'agent': 'ralph',
           'calendar': { 'calendar_admin_group': 'sysadmin-badges',
                         'calendar_contact': 'ralph@fedoraproject.org',
                         'calendar_description': 'cool deal',
                         'calendar_editor_group': 'sysadmin-main',
                         'calendar_name': 'awesome',
                         'calendar_status':