autorelease-validate-central job?

Robert Varga


we are currently releasing to Central, but there is no guarantee those
artifacts do not require to actually work.

There are important differences, as our nexus is a mirror, which
contains additionally seeded artifacts -- see for details. Also
compare to
content of nexus.

In order to validate that this really is the case, we really should be
running autorelease *without*, i.e. making sure
we depend *only* on the content of Central.

This might be a drastic step, so can we first have a weekly job which
performs autorelease-release, but does nothing else?


P.S.: this is something we definitely would want for MRI's maven-stage
jobs -- that way we have assurance that our upstream artifacts have been
successfully replicated on Central.

Join { to automatically receive all group messages.