-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: NXP-7.x, NXP-8.x, NXP-9.x
-
Component/s: Continuous Integration
-
Epic Link:
-
Tags:
-
Sprint:nxsupport 11.1.6
-
Story Points:3
After a HF build is successful
- the next HF version should be added to the list of versions (see here)
- the current HF version should be filled in with the release date (the day the job is run)
- the next HF version should be filled in with the start and release dates
- the start date is the day the job is run
- the release date is in this case theoretical and calculated based on version-specific cycle (2 weeks, 3 weeks, 1 month)
- the current HF version will be released
- the unresolved issues fixversion should be set to the next version
- the newly created version should be grouped with other HF releases of the same branch (have to check how the position is persisted on a page)
2 approaches:
- Jenkins plugin:
https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin - scripting by adding functions to the JIRA lib and adding a separate script
Some thoughts
- Unfortunately, it seems the former is limited and does not allow to set release date for the current version as well as the start and release dates for the next one
- In both cases this could be triggered from the actual Jenkins job