-
Story
-
Resolution: Done
-
Highest
-
None
-
None
-
Integration R2 M3
After a minimum sanity (robot + extended rest calls) determines that an automated ONAP deployment is good - tag all the repos with the current date-time
We don't need to actually test the build prior to tagging - as we can remove tags that don't pass sanity later
20171026 Proposal: Blind nightly TAG of repos/images. This will allow us to begin CI work to mark builds as stable. Currently there is no way to reference a master TAG across ONAP for builds later found to be passing most Health/REST checks, define builds where particular JIRAs occur - for reproduction/fix testing. In the near future when we have automated E2E via vFW we would be able to reference the last nightly TAG of master that passed sanity in a CI build (process: bring up a spot EC2 instance - deploy ONAP (tagged version jars/wars/images) - run robot health + vFW - mark TAG as Good/Bad, shutdown ONAP - repeat every 24 hours) - developers then decide to upgrade based on results
every day for 2 weeks
every week after
every month for last year
- is blocked by
-
POLICY-674 Docker images names inconsistent between nexus3 and dockerhub (policy-db vs policy-policy-db)
- Closed
-
CIMAN-132 Docker Standard Tag Format
- Done