Hi guys,
During our test of the SonarQube Jenkins plugin we have noticed the following bad behavior:
- start from scratch (drop ~/.jenkins)
- start a clean Jenkins with java -jar jenkins.war
- go in administration page and see that all tools auto-install drop down list are populated (and indeed there are appropriate files in ~/.jenkins/updates)
- install SonarQube Jenkins plugin manually (upload sonar.hpi)
- restart Jenkins
- go in administration page and see SonarQube Runner tool auto-install feature is broken (a text box is rendered instead of the drop down)
- in ~/.jenkins/updates/ there is indeed no hudson.plugins.sonar.SonarRunnerInstaller file
To fix that I only found 2 options:
- either wait for a very long time (1 day?) as it seems this is the default interval for downloading json files from update center
- delete entire folder ~/.jenkins/updates and restart Jenkins => then all files (including hudson.plugins.sonar.SonarRunnerInstaller) are downloaded
So my question is: is it a known issue on core side or did I do something wrong in my implementation:
Thanks
Julien