[RPU] builds stuck in trusted.ci.jenkins.io

[dduportal]

Service(s)

trusted.ci.jenkins.io

Summary

Since jenkins-infra/repository-permissions-updater#3953, builds of RPU are stuck on trusted.ci.jenkins.io (past 14 hours).

As a consequence, the CD tokens are expired, preventing plugins to be released.

Reproduction steps

No response

[dduportal]

Initial analysis on trusted.ci.jenkins.io: builds are stuck waiting for a maven-21 node but this is not configured on trusted.ci.jenkins.io.

Applied the label to the ubuntu-22 Azure VM template as a hotfix : VM was scheduled and build is running using JDK11 as it was before the jenkins-infra/repository-permissions-updater#3953 change => it is only a label and we know RPU works fine with JDK11.

[MarkEWaite]

Thanks! Sorry that I broke the RPU with that pull request. Is there a way the pull request that introduced the damage could have been safely executed on trusted.ci.jenkins.io without actually performing any operations?

I assume probably not, so the next best thing would have been for me to ask someone with access to trusted.ci.jenkins.io to confirm that the jobs are still running successfully. I'll do that in the future.

[dduportal]

Thanks! Sorry that I broke the RPU with that pull request. Is there a way the pull request that introduced the damage could have been safely executed on trusted.ci.jenkins.io without actually performing any operations?

I assume probably not, so the next best thing would have been for me to ask someone with access to trusted.ci.jenkins.io to confirm that the jobs are still running successfully. I'll do that in the future.

Good point: we can check the status of the trusted.ci build after such a change in the future. But as the jenkins-infra team does not have a monitoring of private builds, it's not easy for you as a "consumer" though.

Another point: the jenkins-infra team should provide the same "feature set" for agent and their labels between ci.jio, trusted.ci.jio and infra.ci.jio. WiP on this!

[MarkEWaite]

We can also revert the change to repository permissions updater in order to remove any pressure for this change. My change broke RPU and reverting the change is perfectly reasonable.

[dduportal]

We can also revert the change to repository permissions updater in order to remove any pressure for this change. My change broke RPU and reverting the change is perfectly reasonable.

I would propose an intermediate:

• Set the label to 'maven-21' || 'java' (so it always spawn an agent)
• Add a withEnv(JAVA_HOME=/opt/jdk-21) and/or using JDK tool

=> we have promising results and should be able to implement the maven-XX labels on trusted.ci soon!

[dduportal]

• chore(pipeline) fix CD execution on trusted.ci.jenkins.io by using alternative node label and force JDK21 repository-permissions-updater#3958 (comment) => RPU now builds properly
• Adding maven-21 label on trusted.ci.jenkins.io is tracked in Add JDK21 agents (build) #4124
• status closed - jenkins-infra/status@729b58b