Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

TAG All builds when Deployment CI passes

Description

 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

 

Activity

Show:

Former user December 30, 2018 at 10:27 AM

Good morning. The current fixVersion is set to "Beijing Release". Can you please review the status of this ticket and update it accordingly? thank you

Former user June 12, 2018 at 2:45 PM

Ran, please check and update its status.

Former user April 29, 2018 at 11:46 AM
Edited

Just to add that we Need to create a Tag with a jenkins job and update the charts with this Tag after all the above action is applied(BVT & E2E Tests Pass).

note that this will update the one chart with all the subchart included.

Former user October 30, 2017 at 3:24 PM

We are working on a solution on how to stabilize the code base, right now, it is under discussion and will come out with a solution asap with help of LF.

Former user October 30, 2017 at 11:24 AM

just as a reminder on how important proper tagging is:

updating the OOM git repo does not yield any change.

BUT pulling in all the images shows that actually a lot has changed, with no knowledge on what exactly changed as everything is '1.1-STAGING-latest'

 

Done

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Priority

Created September 9, 2017 at 3:34 AM
Updated February 2, 2019 at 4:38 AM
Resolved February 2, 2019 at 4:38 AM