Uploaded image for project: 'Integration'
  1. Integration
  2. INT-189

TAG All builds when Deployment CI passes

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Beijing Release
    • Component/s: None
    • Labels:
    • Sprint:
      Integration R2 M3

      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

       

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              michaelobrien Michael O'Brien
              Reporter:
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: