> On Mon, Mar 5, 2012 at 10:19 AM, Vojtech Juranek <[email protected]> wrote: > >> I was just missing something obvious. Along with checking the > >> 'Install automatically' box in the global config (which might have > >> been set by default) you have to give it a name and then you have to > >> pick that name in the job config. Before getting this right, the job > >> config only offered the 'default' verision, and until I went back to > >> the job and changed it, it didn't trigger the install. And until I > >> clicked the drop-down on in the job config I don't realize there was a > >> new option there. > > > > thanks for feedback, IIRC this is standard behavior of any > > auto-installer, but I'll check if I missed something somewhere > > It makes sense now, but since I didn't understand it at first I set up > a job with the 'default' groovy version which was the only choice, and > it continued to fail after giving the install a name. It would have > helped to mention that the version names had to match in the ? help > link in the main and job configs where you enter them. Or maybe even > to make the 'default' choice work with the auto-installed copy if you > don't find one earlier in PATH. Shouldn't that become the default if > there is no other?
Yes, make sense, thank. Logged as JENKINS-12988 [1]. As for "default" - it's defined as calling "groovy" command - i.e. it calls the installation which you have as the first on the path. In some cases such setup can be useful, second problem is backward compatibility. So the only possible solution which has come to my mind so far is to keep this behavior and switch to some installation defined in global Jenkins config only if calling "groovy" fails - i.e. there's no groovy in the path. Does it make sense? Another possibility could be to add some checkbox which would allow users to define "default" installation in global jenkins config (as the user intentionally select the "default", he wants to change "default" behavior, so there shouldn't be a problem with backward compatibility). Logged as JENKINS-12989 [2], feel free to add comments. Thanks [1] https://issues.jenkins-ci.org/browse/JENKINS-12988 [2] https://issues.jenkins-ci.org/browse/JENKINS-12989
