All,
Self-release is something the community has been asking the LF for since 2017. That is now possible however the process is unfairly getting a bad reputation. Some growing pains are to be expected with any transition, but there has been a rush to judgement that the process is somehow fundamentally flawed. Indeed there was an issue identified as a bug on the LF side, which the RelEng team quickly rectified. The remainder of the tickets unfortunately have primarily come from project teams that have not made the updates necessary to enable self-release, or are not following the documented process. An example of this was a ticket opened today because a successful build did not but produce all of the required artifacts. The root cause of this problem was the continued use of the deprecated nexus-staging-maven-plugin which pre-packaged and deployed some artifacts before lftools compiled the official auto-release package. Eliminating the plugin in the example above was discussed during numerous TSC and PTL calls related to the global-jjb migration. No one should still be using that plugin, however it is the process and tools that have been blamed for the failure. Please help us help you; read and follow the instructions found here: <https://wiki.onap.org/pages/viewpage.action?pageId=68540543> Self Releases Workflow (Nexus2) Thanks! -kenny -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5336): https://lists.onap.org/g/onap-tsc/message/5336 Mute This Topic: https://lists.onap.org/mt/32803235/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
