Docker Standard Tag Format
Description
blocks
duplicates
is blocked by
relates to
Activity
Show:

Former user July 10, 2018 at 4:02 PM

Jessica Gonzalez April 12, 2018 at 12:26 AM
All needed pom file changes have been merged

Former user April 4, 2018 at 9:00 PM
yes, thanks

Jessica Gonzalez April 4, 2018 at 8:59 PM
Sorry I meant x.y.z-STAGING-yyyymmddThhmmssZ . The releases need to come from a x.y.z-STAGING-yyyymmddThhmmssZ tag

Former user April 4, 2018 at 8:51 PM
Releases will be done with x.y.z-STAGING images right? Since the jobs that create the staging images should be using already released/signed java artifacts, while the snapshot docker images will probably contain unreleased snapshot java code.
Done
Details
Assignee
Jessica GonzalezJessica GonzalezReporter
Former userFormer user(Deactivated)Labels
Priority
Medium
Details
Details
Assignee

Reporter

Labels
Priority
Created February 20, 2018 at 7:37 PM
Updated August 12, 2023 at 4:14 AM
Resolved April 12, 2018 at 12:26 AM
As a community we need a consistent way to tag the Docker images so that we can sort them chronologically.
The need is also documented in the wiki.
Current status within Docker
ONAP Nexus 3 which contains ONAP Docker images is structured as below:
Docker Release: ONAP released Images
Docker Staging: currently empty
Docker Snapshot: the big pile
What do we Need standardized Docker format
As Docker Snapshot is a cumulative repository, given a version, a keyword and the name of an image, the need is a systematic method to sort chronologically images based on Nexus version field.
This will help to community in providing an automated deployment using tag sets on a standard format.
Proposal
The proposed docker tag format to align across all the teams is the following:
x.y.z-KEYWORD-yyyymmddThhmmssZ
X.Y.Z follows the Semantic Versionning
KEYWORD: SNAPSHOT or STAGING
Example
1.1.2-SNAPSHOT-20181231T234559Z