Create 1.5 Release

[planetf1]

• [x] Create 1.x branch
• [x] Update master to 1.(x+1)-SNAPSHOT
• [x] Update branch from 1.x-SNAPSHOT to 1.x
• [x] Remove release notes from branch
• [x] Run tests including CTS
• [x] Ensure release is current in master release notes & Add any final text
• [x] Launch release pipeline
• [x] Approve release
• [x] Verify artifacts on maven central
• [x] Publish final 1.x docker images
• [x] Create GitHub release
• [ ] Blog Post
• [ ] Update master with new Type patchfile

[planetf1]

Notebooks and CTS tests all look good with no additional failures

[planetf1]

Currently blocked by incomplete sync. See #2704 for an effort to add parallism. However that in itself caused additional issues, so reverting to N=1 to flush out the final packaging issues preventing sync.

[planetf1]

Current issues on the publishing are:

Not present in JCenter:

• [X] admin-services-samples:1.5 -> Not on Bintray??? -> Added to JCenter -> Successfully synced and closed repo.
• [X] discovery-engine-connectors:1.5 -> Submitted to JCenter -> Successfully synced and closed repo.
• [x] glossary-author-view:1.5 -> A binary file (jar, aar, wat, apk) should be part of the package. Package should include sources as part of the package.
• [X] glossary-author-view-server:1.5 ->< Submitted to JCenter -> Successfully synced and closed repo.
• [X] glossary-author-view-spring:1.5 -> Submitted to JCenter-> Successfully synced and closed repo.
• [X] readonly-repository-connector:1.5 -> Submitted to JCenter -> Successfully synced and closed repo.
• [x] stewardship-engine-services:1.5 -> A binary file (jar, aar, wat, apk) should be part of the package. Package should include sources as part of the package.
• [x] stewardship-engine-services-api:1.5 -> Package should include sources as part of the package.
• [x] stewardship-engine-services-client:1.5 -> Package should include sources as part of the package.
• [X] stewardship-engine-services-server:1.5 -> Submitted to JCenter -> Successfully synced and closed repo.
• [x] stewardship-engine-services-spring:1.5 -> Package should include sources as part of the package.
• [x] view-services:1.5 -> A binary file (jar, aar, wat, apk) should be part of the package - Package should include sources as part of the package.

Va;idation failed:

• [x] open-metadata-conformance-suite-server:1.5 - no javadoc/signature -> Missing Signature: '/org/odpi/egeria/open-metadata-conformance-suite-server/1.5/open-metadata-conformance-suite-server-1.5-javadoc.jar.asc' does not exist for 'open-metadata-conformance-suite-server-1.5-javadoc.jar'. Dropping existing partial staging repository.
• [X] subject-area-server:1.5 - no sources/signature - Successfully synced and closed repo.

Errors reported relating to repository: (could be related to a previous partial sync)

• [X] security-sync-connectors:1.5 -> Failed to close repository: orgodpi-2927. Server response: * Unhandled: Staging repository is already transitioning: orgodpi-2927 Dropping existing partial staging repository. DELETED repo -> Successfully synced and closed repo.
• [X] security-sync-services:1.5 -> Successfully synced and closed repo.
• [X] stewardship-action:1.5 -> Successfully synced and closed repo.
• [X] stewardship-action-api:1.5 -> Successfully synced and closed repo.

Bad Request from API

• [X] stewardship-action-client:1.5 -> Successfully synced and closed repo.
• [X] stewardship-action-server:1.5 -> Failed to close repository: orgodpi-2933. Server response: * Unhandled: Staging repository is already transitioning: orgodpi-2933 Dropping existing partial staging repository. -> DROPPED repos -> Successfully synced and closed repo.

Source: https://dev.azure.com/ODPi/Egeria/_releaseProgress?releaseId=116&_a=release-environment-logs&environmentId=348

[planetf1]

Reporting to bintray issues with:

a) Packages that have packaging=pom, and contain the required <scm> tag which are failing validation for no clear reason. This is a re-run of the problems last release where JFrog said we needed the scm tag, which we added.....

• glossary-author-view
• stewardship-engine-services
• view-services

email sent...

Packaging errors in egeria

Missing sources. These poms are defined as packaging=jar (default) but don't contain sources, which we know isn't permitted. It is basically invalud. We can either a) ignore b) add dummy source/javadoc/jar c) change packaging type to pom. Since these are mostly currently empty and not used, I'm inclined to leave as-is cc: @mandy-chessell

• stewardship-engine-services-api
• stewardship-engine-services-client
• stewardship-engine-services-spring

Errors in artifactory

-- missing signatures. This may be fixable by redoing the full build, perhaps signature gen failed for some reason?

• open-metadata-conformance-suite-server - no signature for the javadoc jar....

@bramwelt can you advise on this artifactory issue

Longer term need to figure out why this process is rather unreliable. Not just performance but the jfrog validation seems suspect. What do other project use? How about commercial products? Can we use a different service? Do we need to pay for jfrog support? Also - can we run 'test' deployments more often - which may pick up issues quicker than monthly ie on any newly introduced components. Perhaps consider maven central snapshots, or weekly runs.

[planetf1]

The three packages failing validation are now synced to maven central after manual addition The stewardship-engine-* packages will be left as-is, as they are currently empty, awaiting implementation in a future release

[planetf1]

Contacting LF team to see if they can re-sync https://odpi.jfrog.io/odpi/webapp/#/artifacts/browse/tree/General/egeria-release-local/org/odpi/egeria/open-metadata-conformance-suite-server/1.5 to bintray (I don't have permissions).

The sync from bintray to maven central is failing due to a missing signature:

Sync Status
Last Synced: Never
Last Sync Status: Validation Failed
Last Sync Errors: Missing Signature: '/org/odpi/egeria/open-metadata-conformance-suite-server/1.5/open-metadata-conformance-suite-server-1.5-javadoc.jar.asc' does not exist for 'open-metadata-conformance-suite-server-1.5-javadoc.jar'. Dropping existing partial staging repository.

[planetf1]

See https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-19257

[grahamwallis]

The link is only viewable to a limited audience

[planetf1]

The link is only viewable to a limited audience

Yes it is sorry - I can't control that. It's included so that I can point the LF support team here for further info.

@bramwelt is looking at trying to republish that artifact. It looks to me as something went awry in the signing process, which is basically an artifactory operation as best I know

[planetf1]

Chasing up - still blocked from completing the release.

[planetf1]

Release 1.5 artifacts are now synced to maven central.