Revisions and Commits
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dereckson | T580 Create a notification center, with a message broker | |||
| Resolved | dereckson | T581 Print on #tasacora and #nasqueron-ops relevant messages about Jenkins tasks | |||
| Resolved | dereckson | T616 Allow Dæghrefn to consume messages from the broker | |||
| Resolved | dereckson | T617 Installed Fossil 1.34 on Ysul | |||
| Resolved | dereckson | T621 TCL extension to implement AMQP without blocking the thread |
Event Timeline
This task has been identified as suitable for the December product backlog for infrastructure. It's included in our product backlog and will be discussed for inclusion to sprint backlog this E3 meeting.
As said in T579, we have two approach:
(1) We create a Jenkins gate and relevant events pipeline in the notifications center, and use a Jenkins to HTTP plugin
(2) We create a plugin to publish directly to the broker JSON messages in the relevant notifications format.
Format for JSON notification messages
{
"service": "Jenkins",
"project": "Nasqueron",
"group": "docker",
"rawContent": "",
"type": "job-done",
"text": "The job ... has been done.",
"link": "http://ci.nasqueron.org/<url of the log>"
}Let's take a shorcut.
Jenkins notifies GitHub about jobs. GitHub then fires 'status' event.
Status support added to notification center: https://github.com/nasqueron/notifications/commit/f54e93a06189dfe5ab7863a78319f9971ba570d5
This gives:
20:59:25 < Wearg> Build #21 in progress... — deploy-website-nasqueron-www1-docker — http://ci.nasqueron.org/job/deploy-website-nasqueron-www1-docker/21/
20:59:25 < Wearg> Build #21 succeeded in 2 sec — deploy-website-nasqueron-www1-docker — http://ci.nasqueron.org/job/deploy-website-nasqueron-www1-docker/21/