...
- Roll to next snapshot version of parent poms, and update properties containing current version to use next snapshot version.
- Roll ccsdk/sli repos (sli/core, sli/adaptors, sli/northbound, sli/plugins, distribution) to next snapshot and update to use new snapshot version of parent pomCrpom.
Note: be sure to do the repos in the order listed. core must be done first; then adaptors,northbound and plugins ; and lastly distribution. - Create new CCSDK docker containers
- Rerun CSIT to make sure it still passes
- Update parent poms to update properties containing version to the next version
Note: at this point, builds of sli/adaptors, sli/northbound, sli/plugins and distribution will break, because we have not yet released sli/core. - Create staging version of ccsdk/parent by posting comment "please release" to commit for previous step.
- Mail helpdesk@onap.org to create a ticket requesting to release new CCSDK parent poms. In ticket, be sure to include link to the Jenkins release build triggered by previous step.
NOTE: do NOT continue to next step until Linux Foundation has released parent poms. - Update ccsdk/sli repos to use released version of parent pom.
- Create new staging versions of ccsdk sli repos (core, adaptors, northbound, plugins)
- Create new CCSDK docker containers
- Rerun CSIT to make sure it still passes
- Mail helpdesk@onap.org to create a ticket requesting to release CCSDK sli repos (core, adaptors, northbound, plugins). In ticket, be sure to reference Jenkins release builds trigger by step 10