Signed Minion container bleeding image shows revision as meridian-foundation-2021.1.4-1-487
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Benjamin Reed September 28, 2021 at 9:00 PM
merged to foundation-2019
Benjamin Reed September 28, 2021 at 6:34 PM
It turns out this isn't wrong, it's just not coming up with a terribly useful "unique identifier". Git searches back in the history for a recent common-ancestry tag, and then appends the short hash to it.
I've made a change to make it instead be, eg: develop-29.0.0-SNAPSHOT-91896a47af5 (the branch + the POM version + the short hash)
But you can rest assured the bleeding snapshots aren't coming from an ancient version, it is actually develop code.
Fixed
Details
Details
Assignee
Benjamin ReedReporter
Chantal MoffattLabels
HB Grooming Date
Sep 28, 2021
HB Backlog Status
HB
Sprint
None
Priority
MinorPagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Created September 23, 2021 at 3:04 PM
Updated February 11, 2022 at 10:22 PM
Resolved September 28, 2021 at 9:00 PM
The signed opennms/minion bleeding image report its revision as meridian-foundation-2021.1.4-1-487-g91896a47af5
Pull the signed minion bleeding image (September 23rd, 2021 at 10:00 EST)
Running history on the image
is aware and asked for a Jira to track the above.