Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: release main #6005

Merged
merged 2 commits into from
May 31, 2023
Merged

chore: release main #6005

merged 2 commits into from
May 31, 2023

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented May 30, 2023 •
edited

🤖 I have created a release beep boop

26.16.0

26.16.0 (2023-05-31)

Dependencies

  • update dependency com.google.cloud:first-party-dependencies to v3.10.0 (#6000) (9880029)
  • update dependency com.google.cloud:first-party-dependencies to v3.10.1 (#6018) (291545a)
  • update dependency com.google.cloud:gapic-libraries-bom to v1.12.0 (#6002) (27ecac9)
  • update dependency com.google.cloud:google-cloud-bigquery to v2.27.0 (#5993) (a9867e8)
  • update dependency com.google.cloud:google-cloud-bigquerystorage-bom to v2.37.2 (#6001) (9f2e1f7)
  • update dependency com.google.cloud:google-cloud-bigtable-bom to v2.23.2 (#6010) (4aa461c)
  • update dependency com.google.cloud:google-cloud-datastore-bom to v2.14.7 (#6003) (3f38cb1)
  • update dependency com.google.cloud:google-cloud-firestore-bom to v3.12.0 (#6014) (352c3ee)
  • update dependency com.google.cloud:google-cloud-logging-bom to v3.15.2 (#6006) (da161ad)
  • update dependency com.google.cloud:google-cloud-logging-logback to v0.130.13-alpha (#6011) (c9e6e0f)
  • update dependency com.google.cloud:google-cloud-nio to v0.126.16 (#6008) (19f3cb0)
  • update dependency com.google.cloud:google-cloud-pubsub-bom to v1.123.13 (#6009) (5b8348d)
  • update dependency com.google.cloud:google-cloud-pubsublite-bom to v1.12.6 (#6012) (88e259c)
  • update dependency com.google.cloud:google-cloud-spanner-bom to v6.42.2 (#5997) (a233987)
  • update dependency com.google.cloud:google-cloud-spanner-bom to v6.42.3 (#6016) (e063e7c)
  • update dependency com.google.cloud:google-cloud-spanner-jdbc to v2.10.0 (#6017) (9f6ec63)
  • update dependency com.google.cloud:google-cloud-storage-bom to v2.22.3 (#6007) (0de3cda)

This PR was generated with Release Please. See documentation.

@release-please release-please bot requested a review from a team as a code owner May 30, 2023 17:50
@product-auto-label product-auto-label bot added the size: s Pull request size is small. label May 30, 2023
@release-please release-please bot force-pushed the release-please--branches--main branch 5 times, most recently from d5a240a to 94add52 Compare May 31, 2023 04:53
@suztomo
Copy link
Member

suztomo commented May 31, 2023

@mpeddada1 Use this failing shared dependency convergence check to find missing dependencies

image

@release-please release-please bot force-pushed the release-please--branches--main branch 8 times, most recently from d232156 to 07bee5a Compare May 31, 2023 14:32
@mpeddada1
Copy link
Contributor 

Found 1 artifacts with shared dependencies version: 3.9.0
Warning: cloud-spanner-jdbc:2.9.16[WARNING]

@release-please release-please bot force-pushed the release-please--branches--main branch 2 times, most recently from eb456fb to 369079f Compare May 31, 2023 15:33
@mpeddada1
Copy link
Contributor

mpeddada1 commented May 31, 2023 •
edited

The shared-dependencies version is currently set to 3.10.0 but the desired version is3.10.1. Put up follow-up in #6018

@mpeddada1
Copy link
Contributor

mpeddada1 commented May 31, 2023 •
edited

The ci/ bom-content-test job is failing with:

Error:  Errors: 
Error:    BomContentTest.testLibrariesBom:60->checkBom:76->assertReachable:197 IO Received 404 response from invalid artifact https://repo1.maven.org/maven2/com/google/cloud/google-cloud-bigtable/2.23.2/
[INFO] 
Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0

@suztomo due to a maven caching issue, we are receiving a 404 Not Found error even though com.google.cloud:google-cloud-bigtable:2.23.2is available on Maven Central (See https://repo1.maven.org/maven2/com/google/cloud/google-cloud-bigtable/2.23.2/google-cloud-bigtable-2.23.2.pom and https://repo1.maven.org/maven2/com/google/cloud/google-cloud-bigtable/maven-metadata.xml). I've added workaround for theBomContentTest` to cater to this. Please let me know if this looks okay or if you have any alternatives?

@product-auto-label product-auto-label bot added size: m Pull request size is medium. and removed size: s Pull request size is small. labels May 31, 2023
@mpeddada1
Copy link
Contributor

mpeddada1 commented May 31, 2023 •
edited

Now running into:

com.google.api.grpc:proto-google-cloud-storage-v2:jar:2.22.3-alpha has a transitive dependency com.google.api.grpc:proto-google-iam-v1:jar:1.14.1. This is higher version than com.google.api.grpc:proto-google-iam-v1:jar:1.14.0 in the BOM. Example dependency path: com.google.api.grpc:proto-google-cloud-storage-v2:jar:2.22.3-alpha / com.google.api.grpc:proto-google-iam-v1:1.14.1 (compile)
com.google.api.grpc:proto-google-cloud-storage-v2:jar:2.22.3-alpha has a transitive dependency com.google.api:api-common:jar:2.11.1. This is higher version than com.google.api:api-common:jar:2.11.0 in the BOM. Example dependency path: com.google.api.grpc:proto-google-cloud-storage-v2:jar:2.22.3-alpha / com.google.api:api-common:2.11.1 (compile)

It may be because we are still using shared dependencies 3.10.0 instead of 3.10.1.

@mpeddada1 mpeddada1 added do not merge Indicates a pull request not ready for merge, due to either quality or timing. owlbot:run Add this label to trigger the Owlbot post processor. labels May 31, 2023
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label May 31, 2023
@mpeddada1 mpeddada1 removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label May 31, 2023
@mpeddada1 mpeddada1 added the owlbot:run Add this label to trigger the Owlbot post processor. label May 31, 2023
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label May 31, 2023
@mpeddada1 mpeddada1 merged commit 7dbac53 into main May 31, 2023
20 checks passed
@mpeddada1 mpeddada1 deleted the release-please--branches--main branch May 31, 2023 20:49
@mpeddada1 mpeddada1 mentioned this pull request May 31, 2023
Merged
@release-please
Copy link
Contributor Author

🤖 Release is at https://github.com/googleapis/java-cloud-bom/releases/tag/v26.16.0 🌻

@release-trigger
Copy link

Triggered job: cloud-devrel/client-libraries/java/java-cloud-bom/release/stage (2023-05-31T21:36:45.025Z)

To trigger again, remove the autorelease: triggered label (in a few minutes).

@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

The release build failed! Please investigate!

@mpeddada1
Copy link
Contributor

mpeddada1 commented May 31, 2023 •
edited

Release failed with:

No plugin found for prefix 'nexus-staging' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/root/.m2/repository), central ([https://repo.maven.apache.org/maven2](https://www.google.com/url?q=https://repo.maven.apache.org/maven2&sa=D))] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

Investigation:
The native-staging-maven-plugin is defined under the release-staging-repository profile.. This profile is called when mvn nexus-staging:release -B --activate-profiles release-staging-repository is activated in stage.sh

@suztomo
Copy link
Member

suztomo commented Jun 1, 2023 •
edited

@mpeddada1 Any network error? "maven is unable to access the remote repository (so basically a problem with your internet connection)."

https://stackoverflow.com/a/26378059

(Either case, retry the job.)

@mpeddada1
Copy link
Contributor

@suztomo That could be possible! Started a rebuild.

@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

The release build failed! Please investigate!

@mpeddada1
Copy link
Contributor

mpeddada1 commented Jun 1, 2023 •
edited

Maybe the profile is not getting activated correctly? The profile in google-cloud-java looks slightly different: https://github.com/googleapis/google-cloud-java/blob/57ff8a24d17bc2bb32bef1e3e32187fa143cb2e1/pom.xml#L188-L224

Or a Maven issue. From the stackoverflow post:

Background Information

When you execute mvn help:effecitve-pom, help is a prefix which represents a specific plugin while effective-pom is the goal from that plugin that should be executed.

The first thing Maven does is try to lookup the full plugin based on the given prefix (so in your case the prefix help). Normally it does this by checking the /org/apache/maven/plugins/maven-metadata.xml file in your local repository (by default your local repository is stored under %HOME%/.m2/repository).

If this file doesn't exist then it tries to check it remotely (again default configuration would use maven central)

We recently experienced a 404 Not Found error in #6005 (comment)

[Update] https://repo.maven.apache.org/maven2/org/sonatype/plugins/nexus-staging-maven-plugin/1.6.13/ is accessible via the browser.

@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

The release build failed! Please investigate!

@mpeddada1 mpeddada1 mentioned this pull request Jun 1, 2023
Closed
@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

The release build failed! Please investigate!

@release-tool-publish-reporter
Copy link

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link

🥚 You hatched a release! The release build finished successfully! 💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@suztomo suztomo suztomo approved these changes

@mpeddada1 mpeddada1 mpeddada1 approved these changes

Assignees
No one assigned
Labels
autorelease: failed autorelease: published size: s Pull request size is small.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@suztomo @mpeddada1