Thanks, Sebb. To confirm, our Jenkins jobs only create release candidates (produce artifacts to local disk). They have no Nexus credentials and no GPG key. The RM downloads the unsigned artifacts, verifies binary reproducibility locally, signs with their own GPG key, uploads signed artifacts to the ASF Nexus staging repo, and later performs any staging→release promotion manually via the Nexus web UI after a successful vote on dev@. The recent 401s you may have seen from the CI account were an accidental Nexus deploy attempt from a misconfigured POM in a utility project; that has now been corrected so the CI never contacts repository.apache.org. ________________________________ From: sebb <[email protected]> Sent: Friday, July 24, 2026 9:05 AM To: [email protected] <[email protected]> Subject: Re: Royale_Compiler_JBurg_Types_Release_Step_002 - Build # 4 - Still Failing!
The Jenkins job appears to be trying to perform a formal release. This must not and cannot be automated. Scripts are allowed to create release candidates, but promotion to a release must be done manually after a successful release vote. Sebb On Fri, 24 Jul 2026 at 08:39, Apache Royale Release <[email protected]> wrote: > > Royale_Compiler_JBurg_Types_Release_Step_002 - Build # 4 - Still Failing: > > Check console output at > http://apacheroyale.francecentral.cloudapp.azure.com:8080/job/Royale_Compiler_JBurg_Types_Release_Step_002/4/ > to view the results.
