-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Sonatype and Javadoc snapshots both failing since recently #1832
Comments
I updated the Auto Sonatype secret to use my user token after doing the same for Truth. It was kind of a pain, but I think it's done. That leaves only Javadoc. I may report progress on a similar problem with Truth for that, too. |
I have a fix out for the Truth Javadoc problem, and it looks like the same fix will work here. |
(In the case of the similar problem for _Truth_, the problem was `maven-javadoc-plugin-3.10.0`. But the _Auto_ problem doesn't appear to have started with such an upgrade, so _shrug_.) This should fix Javadoc snapshots. Fixes ttps://github.com//issues/1832 RELNOTES=n/a PiperOrigin-RevId: 681054579
(In the case of the similar problem for _Truth_, the problem was `maven-javadoc-plugin-3.10.0`. But the _Auto_ problem doesn't appear to have started with such an upgrade, so _shrug_.) This should fix Javadoc snapshots. Fixes ttps://github.com//issues/1832 RELNOTES=n/a PiperOrigin-RevId: 681477620
Javadoc is fixed. Sonatype snapshots are not fixed. I assume that I don't personally have the necessary permissions to publish for auto. We'll need someone who does have permissions to follow the instructions above. |
In short, we need a username and password in https://github.com/google/auto/settings/secrets/actions that come from a Sonatype owner's User Token (rather than a "plain" username and password). There's a chance that those are already in your .m2/settings.xml, or you can get them by following https://central.sonatype.org/publish/generate-token/. (And then put them in your .m2/settings.xml while you have them handy, since you'll likely need them for publishing "real" releases in the future.) |
Thanks for the detailed instructions! I've done that, and it looks like the Publish Snapshot action is working now. |
Oh, nice, I'd forgotten that you can manually trigger reruns! |
Sonatype
That appears to have started with 98c8ec7, but I assume it's a result of some credentials expiring or being regenerated or having access cut off. I reported a similar problem recently with Guava as internal bug 360518509, and it turned out to be simple to fix
Javadoc
(Or at least I'm guessing that that's the problem.)
That appears to have started with either 8a9bd4f or a161323. It's hard to be sure which because the submission of the one cancelled the CI for the other.
The text was updated successfully, but these errors were encountered: