[gate] CI does not tell how to retrigger it
Bug #1539220 reported by
Kirill Zaitsev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Fix Released
|
Wishlist
|
Nikolay Starodubtsev | ||
Bug Description
It's currently tribal knowledge — how you can retrigger a failed CI. We should enhance it to add comment to jenkins on failure:
smth like: "If you believe, that the error is not related to your change: retrigger the CI with 'retrigger murano-ci'"
We should also comply with http://
| description: | updated |
| description: | updated |
| Changed in murano: | |
| milestone: | mitaka-3 → mitaka-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to murano-deployment (master) | #1 |
| Changed in murano: | |
| assignee: | nobody → Nikolay Starodubtsev (starodubcevna) |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to murano-deployment (master) | #2 |
| Changed in murano: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/