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.

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

Auto-release all clients when publishing with Maven #8378

Merged
merged 1 commit into from
Nov 17, 2024

Conversation

arielshaqed
Copy link
Contributor

Look what I found! This property is covered in the
docs
. It also allows for a manual review opportunity... but given that we don't do that, and that we test first, let's not go there.

Fixes #7974.

Tested by manually triggering a release on this branch. It finished and I see no staging repository on https://s01.oss.sonatype.org/#stagingRepositories. Naturally we will need to wait to see whether a release test-auto-release actually made it to Maven central.

But it's worth pulling even now, in the worst case we still need to do something extra.

@arielshaqed arielshaqed added pr/merge-if-approved Reviewer: please feel free to merge if no major comments infrastructure build, deploy and release processes java Pull requests that update Java code exclude-changelog PR description should not be included in next release changelog labels Nov 17, 2024
@Isan-Rivkin
Copy link
Contributor

Isan-Rivkin commented Nov 17, 2024

Nice!

@@ -388,6 +388,11 @@ type Config struct {
Enabled bool `mapstructure:"enabled"`
FlushInterval time.Duration `mapstructure:"flush_interval"`
} `mapstructure:"usage_report"`
Plugins map[string]struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What this change for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OMG!!?!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @Isan-Rivkin , PTAL...

This property is covered in [the
docs](https://central.sonatype.org/publish/publish-maven/#nexus-staging-maven-plugin-for-deployment-and-release).
It also allows for a manual review opportunity... but given that we don't do
that, and that we test first, let's not go there.
@arielshaqed arielshaqed force-pushed the chore/auto-release-all-clients-from-mvn branch from 8e00fbb to ce834ec Compare November 17, 2024 13:30
Copy link

E2E Test Results - DynamoDB Local - Local Block Adapter

13 passed

Copy link

E2E Test Results - Quickstart

11 passed

@arielshaqed
Copy link
Contributor Author

Also worth noting the beautiful XML inheritance model for pom.xml. This affects all 3 Java clients.

@arielshaqed
Copy link
Contributor Author

Thanks!

@arielshaqed arielshaqed enabled auto-merge (squash) November 17, 2024 13:36
@arielshaqed arielshaqed merged commit 6191fb1 into master Nov 17, 2024
38 checks passed
@arielshaqed arielshaqed deleted the chore/auto-release-all-clients-from-mvn branch November 17, 2024 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exclude-changelog PR description should not be included in next release changelog infrastructure build, deploy and release processes java Pull requests that update Java code pr/merge-if-approved Reviewer: please feel free to merge if no major comments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automate the Java API client release
2 participants