[JENKINS-18548] Release build runs different than manual build

I just tried to release teamconcert 1.0.6, and the release ran fine on my client machine, but the build failed,

https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/31

Then I manually requested a build with no changes and it succeeded,

https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/32

I did a diff of the logs and found some additional logged entries in the successful build that seem related to the error reported in the failed build. They are at the bottom.

This all seems related to the special requirements of our plugin that lead us to using a file repo, https://github.com/jenkinsci/teamconcert-plugin/tree/master/com.ibm.team.build.hjplugin/repo

See history of our plugin requirements for reference here, https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/cowan/jenkinsci-dev/aFN3wcTt2Sw/hB8nDczGU14J

CONSOLE LOG:

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repo.cloudbees.com/content/repositories/central

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo

Downloading: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repo.jenkins-ci.org/public/

Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml

Downloading: file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo/org/kohsuke/stapler/stapler/maven-metadata.xml

[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

457/457 B

457/457 B 4/6 KB

457/457 B 6/6 KB

Downloaded: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml (457 B at 4.7 KB/sec)

[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml (6 KB at 38.4 KB/sec)

[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

[DEBUG] Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in hjplugin-rtc-repo (file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo)

[DEBUG] Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in local (/home/jenkins/.m2/repository)

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Failure to find org.kohsuke.stapler:stapler/maven-metadata.xml in file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo was cached in the local repository, resolution will not be reattempted until the update interval of hjplugin-rtc-repo has elapsed or updates are forced

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://download.java.net/maven/2/

Downloading: http://download.java.net/maven/2/org/kohsuke/stapler/stapler/maven-metadata.xml

4/5 KB

5/5 KB

5/5 KB

---
Originally reported by scowan, imported from: Release build runs different than manual build

• status: Open
  
• priority: Major
  
• component(s): release-plugin
  
• label(s): release-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251223-222157
  

Raw content of original issue

I just tried to release teamconcert 1.0.6, and the release ran fine on my client machine, but the build failed,

https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/31


Then I manually requested a build with no changes and it succeeded,

https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/32


I did a diff of the logs and found some additional logged entries in the successful build that seem related to the error reported in the failed build.  They are at the bottom.


This all seems related to the special requirements of our plugin that lead us to using a file repo, https://github.com/jenkinsci/teamconcert-plugin/tree/master/com.ibm.team.build.hjplugin/repo


See history of our plugin requirements for reference here, https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/cowan/jenkinsci-dev/aFN3wcTt2Sw/hB8nDczGU14J


CONSOLE LOG:


[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repo.cloudbees.com/content/repositories/central

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo

Downloading: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repo.jenkins-ci.org/public/

Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml

Downloading: file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo/org/kohsuke/stapler/stapler/maven-metadata.xml


[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

457/457 B              

457/457 B   4/6 KB  

457/457 B   6/6 KB  


Downloaded: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml (457 B at 4.7 KB/sec)

[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties


Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml (6 KB at 38.4 KB/sec)

[DEBUG] Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

[DEBUG] Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in hjplugin-rtc-repo (file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo)

[DEBUG] Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in local (/home/jenkins/.m2/repository)

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Failure to find org.kohsuke.stapler:stapler/maven-metadata.xml in file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo was cached in the local repository, resolution will not be reattempted until the update interval of hjplugin-rtc-repo has elapsed or updates are forced

[DEBUG] Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://download.java.net/maven/2/

Downloading: http://download.java.net/maven/2/org/kohsuke/stapler/stapler/maven-metadata.xml

4/5 KB              

5/5 KB  

5/5 KB