| Table of Contents |
|---|
...
- Produce build artifacts, compile them into docker images and test them with CSIT locally.
- Push the changes to gerrit to produce build artifacts and docker images from submitted patch and have them tested by CSIT in Jenkins review verification.
- Merge verified changes to produce build artifacts and docker images from master and have them tested by CSIT againin Jenkins merge verification. Successfully verified docker images are tagged with STAGING
- Release the artifacts that pass merge verification.
- Produce STAGING docker images from the released artifacts. These are applicable for higher level E2E test flows.
- Produce RELEASE docker image images by picking one of the candidate STAGING docker images that have passed E2E tests.
Docker image release process:
- Set up gerrit-maven-docker-stage (docker staging job from global-jjb) to produce the STAGING docker images.
- Ensure that the docker staging jobs have completed and generated candidate artifacts
- Perform any necessary testing against the candidate artifacts
- Create a service request to LF Releng (support.linuxfoundation.org) to request a release of the staging candidate
- Specify the specific Jenkins build job that generated the selected candidate build, e.g. https://jenkins.onap.org/view/clamp/job/clamp-maven-docker-stage-master/52/
- LF to re-tag the selected STAGING docker image with a RELEASE version tag
- Update the declared version number for your docker image in the docker version manifest: https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv
- Update the CHANGELOG to describe the changes that were part of this release
- TBD: CHANGELOG structure and update process is being developed by the Documentation project
- Bump your own version numbers for ongoing development
- Staging/Release version in version.properties
...
- Docker Release: ONAP released Images
- Docker Staging: Docker images for staging?currently empty
- Docker Snapshot: the big pile (all the snapshot candidate images from various phases)
What do we need standardized Docker format for?
As Docker Snapshot is a cumulative repository, given a version, a keyword and the name of an image, there is need for a systematic method to sort images chronologically based on Nexus version field.
This will help community to provide 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:
...
proposal: use semantic version v1.1.1 - is released (no latest tag) - unchanged
1.1.2-snapshot is the next under test
1.1.2-timestamp (here we need LF to pick up the format)
proposal: Timestamp-yyyy-mm-dd-Thh-mm-ssZ
or version-yyyymmddThhmmssZ (no :)
1.1.2-20181231T234559Z
fill out and merge Gildas slides
to
https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Independent+Versioning+and+Release+Process#IndependentVersioningandReleaseProcess-StandardizedDockerTagging
send mail to discuss and meeting 2nd monday
...