@pnemade afaik this has nothing to do with this specification. Seems the timestamp the Fedora CI pipeline is exporting is wrong. @bgoncalv maybe you would some time too look @ this pls?

The timestamp in the CI message that is sent seems correct (AFAIK) it is set by fedmsg:

https://apps.fedoraproject.org/datagrepper/id?id=2019-67135b90-b160-4e09-8553-014622bb5a81&is_raw=true&size=extra-large

I don't know from where the timestamp used by the IRC notification comes from...

The only place I see timestamp == 0 (that would explain the 49 years) is on message returned by the CI plugin...

{"msg":{"branch":"master","build_id":"8439","build_url":"https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-task-pipeline-trigger/detail/fedora-task-pipeline-trigger/8439/pipeline/","ci_topic":"org.centos.prod.ci.pipeline.allpackages-build.package.ignored","comment_id":null,"namespace":null,"nvr":"","original_spec_nvr":"","ref":"x86_64","repo":"fonttools","rev":"kojitask-34829084","scratch":true,"status":"SUCCESS","test_guidance":"''","username":"pnemade"},"msg_id":"2019-67135b90-b160-4e09-8553-014622bb5a81","timestamp":0,"topic":"org.centos.prod.ci.pipeline.allpackages-build.package.ignored"}

Yeah - that needs to be fixed in the pipeline, not in the spec here.

I'm not sure where the source code for that is. @jbieren can you link to it here?

@bgoncalv can you tell me where you found that message you pasted that had the timestamp: 0?

@jbieren it appears on Jenkins job:

example: https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-build-pipeline-trigger/287360/console

14:13:54  {"msg":{"branch":"module","build_id":"287360","build_url":"https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-build-pipeline-trigger/detail/fedora-build-pipeline-trigger/287360/pipeline/","ci_topic":"org.centos.prod.ci.pipeline.allpackages-build.package.ignored","comment_id":null,"namespace":null,"nvr":"","original_spec_nvr":"","ref":"x86_64","repo":null,"rev":"kojitask-35125818","scratch":false,"status":"SUCCESS","test_guidance":"''","username":"mbs/mbs.fedoraproject.org"},"msg_id":"2019-c38e68bd-fb53-4d15-8907-ba9402f9f304","timestamp":0,"topic":"org.centos.prod.ci.pipeline.allpackages-build.package.ignored"}

@bgoncalv you pasted a message above that shows timestamp: 0. I am wondering where that one came from

https://github.com/jenkinsci/jms-messaging-plugin/issues/125

Thanks Johnny. Closing this one in favor of the jms-messaging-plugin issue.

Fix released in v1.1.8 of jms-messaging Jenkins plugin.