Sonatype and Javadoc snapshots both failing since recently

[cpovirk]

Sonatype

Failed to deploy artifacts: Could not transfer artifact com.google.auto:auto-common:jar:HEAD-20240816.234909-593 from/to sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots/): authentication failed for https://oss.sonatype.org/content/repositories/snapshots/com/google/auto/auto-common/HEAD-SNAPSHOT/auto-common-HEAD-20240816.234909-593.jar, status: 401 Content access is protected by token

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

I'm going to try looking up my Sonatype User Token and plugging it into our repository secrets. I don't know if the old one (last updated Aug 31, 2021) expired or what.

---

Javadoc

mv: cannot stat '/home/runner/work/auto/auto/target/site/apidocs': No such file or directory

(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.

[cpovirk]

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.

[cpovirk]

I have a fix out for the Truth Javadoc problem, and it looks like the same fix will work here.

[cpovirk]

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.

[cpovirk]

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.)

[eamonnmcmanus]

Thanks for the detailed instructions! I've done that, and it looks like the Publish Snapshot action is working now.

[cpovirk]

Oh, nice, I'd forgotten that you can manually trigger reruns!