Versions Compared

Old Version 59

changes.mady.by.user Jessica Wagantall

Saved on

compared with

New Version Current

changes.mady.by.user Jessica Wagantall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Only the maven-docker-stage is failing. It looks like a dependency issue. Kanagaraj is looking into it
Tableenhancer
numberOfFixedRows3
decimalMark. (point)


TaskMove maven-stage plugin in a new profile in all pom.xml filesReview all pom file changesMerge global-jjb changes & trigger jobsAnalyze binaries delivered to NexusCherry pick needed changed into release branchesRemove old staging jobsRemove unused profiles in pom.xml filesComment on progress
ResponsibleRelEngPTLRelEngPTLPTLRelEngPTL
Estimated Duration10 min
per file		5 min 
per file		20 Min30 Min5 min10 Min10 min per file
AAF







AAI

We are moving few components at a time. The team has tested at least 1 project and we had no issues.

Update:  23 of 24 repos are converted.  The remaining issue:

1) Champ is not a critical mS and is failing, this ticket is open assigned to Steven Blimkie   

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-2506
 









APPC







CCSDK







CLAMP







CLI
Failures in cli-maven-docker-stage-master







DCAE







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
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyEXTAPI-261
  • Also Just need to run a full release process to be sure
Holmes







Integration







Logging

Failures on all new maven-stage jobs

Haven't heard from anyone




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
needs to be done
  • done
  • The team is developing 1.5.0-SNAPSHOT which fixed several jobs
Modeling







MSB
Maven-docker-stage jobs need to be added to replace docker-java-version-shell-daily
  • Cleanup of old jobs underprogress








    • 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

    Ofir mentioned they are going to work on the migration this week and contact me for any issues. In comunication with him

    Waiting on Ofir to confirm which modules does he wants to work on first, or if he wants me to submit a change for all

    Phase 1 started









    SDNC







    SO






    		Only thing to be done is remove the old deprecated jobs
    UUI







    VFC







    VID







    VNFSDK
    Failures







    • Only remaining ves-agent stage-relase job need to be addressed: The job is still calling "
      nexus-staging-maven-plugin:" need to remove the plugin
      The team needs to merge https://gerrit.onap.org/r/#/c/vnfsdk/ves-agent/+/92054/
    • Done.failues need to be addressed. Looks like development needs to be done on a SNAPSHOT version and the artifacts being built from the pom.xml have a release artifact version. The team needs to add the "SNAPSHOT" in the version
    Cleanup
    • DoneCleanup of old jobs needs to be done



    Nexus2 releases migration notes

    ...

    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