-
Story
-
Resolution: Done
-
Highest
-
None
We need to have a mechanism for setting the stable ONAP deployment with it's Repo's versions in some info file.
This should give us the information of the 3 weeks stable configuration that we use and the last stable configuration of ONAP deployment until it's been broken.
And be able to understand which component caused the issue and what Repo version number in order to get it fixed ASAP.
Possibly: blindly daily tag jar/war/dockers - then after CD runs - mark the tag set as good later
- clones
-
INT-106
Stabilizing the ONAP master branch
-
- Closed
-
- is blocked by
-
INT-369
Team level notification+E2E testing of in/out dependency changes - procedure
-
- Closed
-
-
AAI-614
AAI: Refactor CHEF out or enable $TAG passed into chef branch git pull in traversal/resources to enable CI/CD
-
- Closed
-
-
INT-300
CI-CD For ONAP master branch
-
- Closed
-
-
LOG-319 61 Amsterdam branches missing/ambiguous/release-1.1.0 only/Capitalized
-
- Closed
-
- relates to
-
LOG-300
CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
-
- Closed
-
-
LOG-265
Migrate OOM CD job to Azure public - run by jenkins.onap.org
-
- Closed
-
- mentioned in
-
Page Loading...