...
| Tableenhancer |
|---|
| numberOfFixedRows | 3 |
|---|
| decimalMark | . (point) |
|---|
|
| Task | Move maven-stage plugin in a new profile in all pom.xml files | Review all pom file changes | Merge global-jjb changes & trigger jobs | Analyze binaries delivered to Nexus | Cherry pick needed changed into release branches | Remove old staging jobs | Remove unused profiles in pom.xml files | Comment on progress |
|---|
| Responsible | RelEng | PTL | RelEng | PTL | PTL | RelEng | PTL |
|
|---|
| Estimated Duration | 10 min
per file | 5 min
per file | 20 Min | 30 Min | 5 min | 10 Min | 10 min per file |
|
|---|
| AAF |
|
|
|
|
|
|
|
| | AAI |
|
|
|
|
|
|
| | | APPC |
|
|
|
|
|
|
|
| | CCSDK |
|
|
|
|
|
|
|
| | CLAMP |
|
|
|
|
|
|
|
| | CLI |
|
|
|
|
|
|
| | | DCAE |
Demo | DMaaP | |
|
|
|
|
|
|
|
7/17 Update: All impacted dcae repo (15/15) migrated to new jobs. Validation and resolution (of some job failures for Ubuntu dependency) are in-progress. | | Demo |
|
|
|
|
|
|
|
| | DMAAP |
|
|
|
|
|
|
|
| | ExtAPI |
|
|
|
|
|
|
| ExtAPI seems to be ok, all jobs ok, pom cleaned. https://jenkins.onap.org/view/externalapi/ - To do: use the java binary from repo, and not the one locally build see
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | EXTAPI-261 |
|---|
|
- Also Just need to run a full release process to be sure
|
ExtAPI | | Holmes |
|
|
|
|
|
|
|
| | Integration |
|
|
|
|
|
|
|
| | Logging |
|
|
| Resolving 2 more failures |
|
|
| - Prudence to help me remove the extra snapshot artifacts being packaged in the autorelease file which is breaking the job
- Cleanup of old jobs done
- The team is developing 1.5.0-SNAPSHOT which fixed several jobs
| | Modeling |
|
|
|
|
|
|
|
| | MSB |
|
|
|
|
|
|
|
| | MultiCloud |
|
|
|
|
|
|
| - Maven-docker-stage jobs need to be added to replace docker-java-version-shell-daily
- Cleanup of old jobs underprogress
| | Music |
|
|
|
|
|
|
|
| | OOF |
|
|
|
|
|
|
| All jobs work, only cmso is skipping artifact signing since they need to run in Ubuntu and SIGUL is just supported in Centos. Signing images for their releases will need to continue to be done manually, but at least we are migrated and not using the plugin in question. | | OOM |
|
|
|
|
|
|
| Confirmed with Mike that they don't need to make any releases. | | O-parent |
|
|
|
|
|
|
|
| | Policy |
|
|
|
|
|
|
| Actively working with Pam, we are getting few components at a time | | Portal |
|
|
| Failures due to banned dependencies (Exception approved by TSC on Aug 1) |
|
|
| - Requesting exception: Portal team requested exception in email to use the portal/sdk snapshot dependency in portal repo (mail sent to Jessica and Catherine). As these two repos (portal and portal/sdk) are developed very closely in dev sprints, they require snapshot usage in those dev sprints (so portal cannot always be on released sdk libraries). Team requests, TSC to consider this as an exception and allow Portal component to use snapshots of protal/sdk libraries while in development phase.
- Component having dependency issues. Information sent to the PTL for helping me analyzing them.
- Need to add maven-docker-stage jobs to replace docker old jobs
- Cleanup needs to be done
| | SDC |
|
|
|
|
|
|
|
| | SDNC |
|
|
|
|
|
|
|
| | SO |
|
|
|
|
|
|
| Only thing to be done is remove the old deprecated jobs | | UUI |
|
|
|
|
|
|
|
| | VFC |
|
|
|
|
|
|
|
| | VID |
Migration almost completed. We hit an issue with a NPM version not supported but the team decided to backtrack all changes  | VNFSDK
|
Nexus2 releases migration notes
...
TECHTEAM: If the project's pom.xml has a dependency on Oparent, they need to migrate to version 2.0.0. For example: https://gerrit.onap.org/r/#/c/modeling/toscaparsers/+/88216/
TECHTEAM: Make sure there is no usage of nexus-staging-maven-plugin in pom.xml. For example: https://gerrit.onap.org/r/#/c/clamp/+/87812/
LFRELENG: Add the team's needed jobs from global-jjb. For example: https://gerrit.onap.org/r/#/c/ci-management/+/77825/
...
- The migration cannot be tested in the Sandbox unfortunatelly.
- The Sandbox is specifically designed to block Nexus2 pushes and we will not be able to confirm if the artifacts were pushed correctly.
- The migration changes depend on pom.xml file changes in the source code which cannot be tested unless these changes are merged.
- Please notice that we can't keep both version-java-daily (and similar local templates) and gerrit-maven-stage (from global-jjb) running successfully at the same time.
- The plugin in question "nexus-staging-maven-plugin" only works for the old templates and, once we remove it's usage to be able to migrate, it will cause the old jobs to fail.
Triggering the stage release jobs
Please use the comment "stage-release" to trigger.
Release process
The release process is still the same:
- The PTL works towards their component development (I believe teams work on JAR artifact changes first and then Docker images)
- Once the PTL has a JAR artifact ready for releasing, they will trigger the gerrit-maven-stage job using the "stage-release" comment in Gerrit.
- The PTL will create a LF support jira ticket with the link of the gerrit-maven-stage job that produced their "autorelease" package (The same way they were already doing for release-java-daily jobs)
- LF will make a release in Nexus2
- PTL works towards their Docker images (which will use the previously released JARs for building)
- Once the PTL has a Docker images ready for releasing, they will trigger the gerrit-maven-docker-stage job using the "stage-release" comment in Gerrit.
- The PTL will create a LF support jira ticket with the link of the gerrit-maven-docker-stage job that produced their images (The same way they were already doing for docker-java-daily jobs)
- LF will make the release in Nexus3
