-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Setup a job for java-maps artifacts release #9045
Copy link
Copy link
Closed
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Description
Activity
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Let's setup a job for java-maps-* artifacts release. Currently we have java-maps-addressvalidation and java-maps-routing and around 6 artifacts under them. As of now, the modules are excluded by stage.sh so that artifacts with "com.google.maps" groupID do not go to the publishing host google.oss.sonatype.org.
google-cloud-java/.kokoro/release/stage.sh
Line 32 in 59d6637
Scope
Here are the Maven modules in the scope:
Publishing Host and Group ID
The challenge (troubleshooting in OSSRH-87007) was that we have 2 publishing hosts and a groupID can only belong to one of them. The current setup:
159f41f was the commit I used on Dec 14th release (http://sponge2/907014e9-7270-4bdb-8122-f1d95c67a278). (One of the artifacts was https://search.maven.org/artifact/com.google.maps.api.grpc/grpc-google-maps-addressvalidation-v1/0.1.0/jar; notice the groupID is
com.google.maps.apiin 2a76495).This script change and groupID change have not been merged to the main branch. Therefore I created this GitHub issue.
Todo
Consideration
We may add other libraries outside Google Cloud organization but not in Google Maps. Let's design the flow and name the script and job to meet future needs.