b5d2018
@@ -4,6 +4,7 @@
testcase:
name: "${body.test.namespace}.${body.test.type}.${body.test.category}"
ref_url: "${body.run.url}"
+ msg-id: "${header.JMSMessageID}"
data:
type:
- "brew-build"
@@ -8,6 +8,7 @@
- uuid: "${headers.uuid}"
url: "${body.run.url}"
item:
- "${body.artifact.component}-${body.artifact.version}"
- "container-image"
- "fedora-module"
- "${body.artifact.name}-${body.artifact.version}-${body.artifact.release}"
- "productmd-compose"
- "redhat-module"
adding msg-id to message, @lholcek please review and merge
lgtm
:thumbsdown: This is not supported by ResultsDB. Custom fields can be only nested under "data".
And I'm not sure if this has been requested. As I understand it, the issues is that adding message ID (which was already added in https://pagure.io/fedora-ci/messages/pull-request/131#request_diff) requires also bumping message version in message publishers. To fix this, we decided to move the mappings to internal GitLab instance and stop versioning it (master/main branch would be the source).
Pull-Request has been closed by timitra
adding msg-id to message, @lholcek please review and merge