• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • sbt-plugin
    • None
    • Ubuntu 14

      I have a simple Jenkins server running Ubuntu. Just building off master. The auto install from scala-sbt.org does not work. In the logs I just see;
      Invalid tool ID 0.13.7
      [chot-bi-build] $ java -Xms512m -Xmx512m -XX:ReservedCodeCacheSize=128m -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -jar /var/lib/jenkins/tools/org.jvnet.hudson.plugins.SbtPluginBuilder_SbtInstallation/0.13.7 clean scalastyle coverage test coverageAggregate

          [JENKINS-27264] Latest 1.5 SBT Plugin does not work

          After the above command, things looked better. That seems a problem though.

          Paolo Giarrusso added a comment - After the above command, things looked better. That seems a problem though.

          Ronald Chen added a comment -

          I still had to run that update downloadables in the script console for the sbt plugin to download 0.13.8

          Ronald Chen added a comment - I still had to run that update downloadables in the script console for the sbt plugin to download 0.13.8

          Same here, I still need to run this workaround and for better or worse have to include it in the instructions for using the plugin in a book that I am writing around the topic of Reactive Web Applications. To be honest though it looks somewhat odd in there, so I was wondering, is there something that could be done to fix this situation? I have absolutely no experience with Jenkins plugin development, but I imagine it should not be too difficult to run this snippet as part of installing the plugin? I'd be willing to help to get this fixed just to be able to remove the workaround from the chapter.

          Manuel Bernhardt added a comment - Same here, I still need to run this workaround and for better or worse have to include it in the instructions for using the plugin in a book that I am writing around the topic of Reactive Web Applications. To be honest though it looks somewhat odd in there, so I was wondering, is there something that could be done to fix this situation? I have absolutely no experience with Jenkins plugin development, but I imagine it should not be too difficult to run this snippet as part of installing the plugin? I'd be willing to help to get this fixed just to be able to remove the workaround from the chapter.

          Daniel Beck added a comment -

          Is this also still necessary in Jenkins 1.619 and newer? I added functionality to update tool installers (basically the script above) whenever you install a plugin that defines one. (JENKINS-27694)

          With JENKINS-27612 resolved, this issue should be obsolete now.

          Daniel Beck added a comment - Is this also still necessary in Jenkins 1.619 and newer? I added functionality to update tool installers (basically the script above) whenever you install a plugin that defines one. ( JENKINS-27694 ) With JENKINS-27612 resolved, this issue should be obsolete now.

          Charles Rice added a comment - - edited

          Jenkins 1.637 using sbt plugin 1.5 - unable to automatically download sbt versions using the scala-sbt.org installer. We're using the 1.5 plugin and 1.4 configuration as a workaround for now...

          Charles Rice added a comment - - edited Jenkins 1.637 using sbt plugin 1.5 - unable to automatically download sbt versions using the scala-sbt.org installer. We're using the 1.5 plugin and 1.4 configuration as a workaround for now...

          chuckwired Can you elaborate on what you mean by 1.4 configuration?

          Brandon Bradley added a comment - chuckwired Can you elaborate on what you mean by 1.4 configuration?

          Charles Rice added a comment -

          blbradley By that we mean we download the sbt installer/binary using userdata (in AWS) into /home/centos/workspace/tools during provisioning of a Jenkins slave, and then specify to Jenkins that there is an sbt installation already in that directory

          Charles Rice added a comment - blbradley By that we mean we download the sbt installer/binary using userdata (in AWS) into /home/centos/workspace/tools during provisioning of a Jenkins slave, and then specify to Jenkins that there is an sbt installation already in that directory

          Brandon Bradley added a comment - - edited

          chuckwired I see. Thanks for your quick response.

          Then, the auto-installer function must be completely broken in newer versions. I've tried

          • the script mentioned above to fix 'Install from scala-sbt.org'
          • 'Install from '*.zip/*.tar.gz' and the path given to '-jar' is empty.

          Good to know most of the functionality besides the auto-installer works.

          Brandon Bradley added a comment - - edited chuckwired I see. Thanks for your quick response. Then, the auto-installer function must be completely broken in newer versions. I've tried the script mentioned above to fix 'Install from scala-sbt.org' 'Install from '*.zip/*.tar.gz' and the path given to '-jar' is empty. Good to know most of the functionality besides the auto-installer works.

          Daniel Beck added a comment -

          One issue I noticed is that the SBT Artifactory was shut down in favor of Bintray – could this be related? Tool downloads failing?

          I created a PR for the crawler at https://github.com/jenkinsci/backend-crawler/pull/48 (which will also make the newest releases available again).

          Daniel Beck added a comment - One issue I noticed is that the SBT Artifactory was shut down in favor of Bintray – could this be related? Tool downloads failing? I created a PR for the crawler at https://github.com/jenkinsci/backend-crawler/pull/48 (which will also make the newest releases available again).

          Charles Rice added a comment -

          Tried this recently on Jenkins 2.10 with the automatic installer and some versions now work correctly, I think you might be right danielbeck with the Artifactory --> Bintray move!

          Can confirm 0.13.9 installs successfully now, and 0.13.9.2 returns a "resource not found".

          Seems it's looking for:
          https://dl.bintray.com/sbt/native-packages/sbt/0.13.9.2/0.13.9.2.zip
          but it's actually located in:
          https://dl.bintray.com/sbt/native-packages/sbt/0.13.9/0.13.9.2.zip

          Charles Rice added a comment - Tried this recently on Jenkins 2.10 with the automatic installer and some versions now work correctly, I think you might be right danielbeck with the Artifactory --> Bintray move! Can confirm 0.13.9 installs successfully now, and 0.13.9.2 returns a "resource not found". Seems it's looking for: https://dl.bintray.com/sbt/native-packages/sbt/0.13.9.2/0.13.9.2.zip but it's actually located in: https://dl.bintray.com/sbt/native-packages/sbt/0.13.9/0.13.9.2.zip

            nightwolfzor Night Wolf
            nightwolfzor Night Wolf
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: