Core Release: Staging not working anymore (original) (raw)

release.ci.jenkins.io

The Jenkins Core release process is able to stage part of the release as per https://github.com/jenkins-infra/release#stage.

For instance: https://github.com/jenkins-infra/release/blob/security-2.356/profile.d/security#L32 where the name of the "private maven repository" to be used for staging is specified in the build profile.

With the security release 2.370, the deployment of the Jenkins artifacts was done to the public repository instead of the staging repository specified in https://github.com/jenkins-infra/release/blob/security-2.370/profile.d/security#L32

Previous security release involving staging (security-256) behaved as expected, so something change between both.

@daniel-beck and I tracked the issue to (at first sight) a major bump of the maven-deploy-plugin (description to be updated).

We have to confirm, diagnose and fix this behavior as soon as possible to avoid any security to be exposed before its end.

No response