-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
Not Selected
-
-
-
None
As an engineer, I want to understand the work needed on the QE side to allow the team to create an ACM 5.0 branch and related issues including upgrade.
This includes understanding what needs to be updated in automation scripts.
Status:
- Installer automation has been updated to factor in both X and Y versions when deciding when to run something. This was done a simple and future proof way as follows. For example, only execute this task if ACM version is 2.14 or greater (including 2.17 and 5.0).
when: - (acm_release_version.split('.') | first | int) * 100 + (acm_release_version.split('.') | last | int) >= 214 - MCE EUS upgrade will need to be tested. Prior to this, EUS upgrade was only for odd Y releases. ACM will remain the same even/odd-ness but MCE will switch.
- clones
-
ACM-29267 ACM 5.0 Version Numbering Investigation - Dev (Installer)
-
- New
-
- is cloned by
-
ACM-29272 [PICS] ACM 5.0 Version Numbering Investigation - QE (PICS)
-
- New
-
-
ACM-29735 ACM 5.0 Version Numbering Investigation - QE (Infrastructure operator)
-
- New
-
-
ACM-29754 ACM 5.0 Version Numbering Investigation - QE (Global Hub)
-
- New
-
-
ACM-29845 ACM 5.0 Version Numbering Investigation - QE (Console)
-
- New
-