I’m running into similar delays for DCAE artifacts release also. We had partial success with selfrelease (for 2 components), but for other dint go as expected. The docker containers releases are also pending with LF – hopefully we can get these closed soon.
Integration team can continue using OOM/staging which includes all latest updates for DCAE (oom/master updates will be done once artifacts are released). Thanks, Vijay From: [email protected] <[email protected]> On Behalf Of FREEMAN, BRIAN D Sent: Tuesday, August 06, 2019 9:21 AM To: [email protected]; onap-release <[email protected]>; [email protected] Subject: Re: [onap-tsc] Self releases latest fix ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Dan, Thanks – that seems reasonable. Brian From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of TIMONEY, DAN Sent: Tuesday, August 06, 2019 9:17 AM To: [email protected]<mailto:[email protected]>; onap-release <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] Self releases latest fix ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Jess, Thanks. I see now that not all the jars in the various CCSDK were released either – so I’ll have to : * Roll the version properties in my parent pom, rebuild and re-release * Roll the version in the following repositories, rebuild and re-release: * ccsdk/sli/core * ccsdk/sli/adaptors * ccsdk/sli/northbound * ccsdk/sli/plugins * ccsdk/features * ccsdk/cds * ccsdk/apps * ccsdk/distribution * Rebuild and re-release dockers in the following repositories: * ccsdk/distribution * ccsdk/apps * ccsdk/cds * Roll the version in the following sdnc repositories and re-release: * sdnc/apps * sdnc/northbound * Build the sdnc dockers and release against the rebuilt versions in these repositories: * Sdnc/apps * Sdnc/oam TSC, integration team : these activities will most likely take most of today, and possibly tomorrow. So, best case, SDNC will have release versions of El Alto early drop available by COB tomorrow, assuming no other issues occur. In the meantime, I’ll update the staging branch of OOM to use staging versions of our early drop – which are built on snapshot builds (so not impacted by this issue) so that testing can move forward. FYI – I started release build activities last Wednesday in order to make the 8/2 date, and was already delayed due to issues with the self-release process. I agree, by the way, that this is short term pain in exchange for significant improvements. I believe a few days delay in getting the release builds done is a good investment in the long run. I just wanted to make sure to set clear expectations on when our release artifacts will be ready and why. Dan Dan Timoney Principal Technical Staff Member AT&T Email : [email protected]<mailto:[email protected]> Office : +1 (732) 420-3226 Mobile : +1 (201) 960-1211 200 S Laurel Ave, Rm E2-2A03 Middletown, NJ 08873 From: <[email protected]<mailto:[email protected]>> on behalf of Jessica Wagantall <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, August 5, 2019 at 9:05 PM To: onap-release <[email protected]<mailto:[email protected]>>, onap-discuss <[email protected]<mailto:[email protected]>>, onap-tsc <[email protected]<mailto:[email protected]>> Subject: [onap-tsc] Self releases latest fix Dear ONAP team. Few PTLs contacted me to report issues in self releases. Aric, Eric, Anil and myself were investigating these. It turns out there was a Nexus CLI limitation that was causing issues while releasing some repos and while attempting to close previous ones at the same time. This might have caused releases to not being posted (or partially posted) whenever there were release jobs running in parallel. We have added the fix right now and released a new version of global-jjb which onap is currently using. I am scanning some releases, but if you encounter any issues please bump your versions and release a new version for your artifacts. Unfortunately we cannot re-release the same versions that might have failed since those autoreleases were closed after attempt a release. Please let me know for any questions and we really appreciate your patience on taking us to this level. I know is been bumpy but this will be so enjoyable after. We also need a perfected process so that we can finish developing the Docker Images self releases safely. Thanks again team! Jess -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18447): https://lists.onap.org/g/onap-discuss/message/18447 Mute This Topic: https://lists.onap.org/mt/32742705/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
