I installed a vanilla Jenkins on my Windows 7 64-bits workstation. Caching does not work either on latest Jenkins 1.476.

Started by user anonymous
Building in workspace C:\Users\ronald\.jenkins\workspace\test
$ hg clone --rev default --noupdate http://ronaldradial:8000/ C:\Users\ronald\.jenkins\workspace\test

I found out that I have the option to choose the Mercurial installation. The options are '(default)' and my own created 'Mercurial'. The '(default)' get 'hg' from the path and does not have options. My own installation 'Mercurial' does have options.
Is this the expected behaviour? Is this difference documented somewhere (or should I have known this)?

(Sorry for delayed response, my JIRA mail queue was choked.)

Right, (default) is the fallback in case you have not explicitly configured any installations. To enable caching you need to create a Mercurial installation and click the checkbox for caching, then use this installation on your jobs. I am not sure how else you thought you had enabled caching.

A hack option that I use is to name one of my mercurial installations: "(Default)", and enable caching on that installation. I'm sure this is not the recommended approach, but for us it beats updating every single job

@jglick Yes, somehow I expected the plugin to use the configuration of the first mercurial installation that was listed. I did not expect it to have a hidden '(Default)' installation that I could not see nor change.

For other tools the installation section allows to say where a tool is installed or add an installer. They don't have settings that changes its behavior. Maven for example, has three sections: maven configuration, maven and maven project configuration. And then there are more settings for each job where maven is used.

There is some inconsistency in how various plugins pick a default for a kind of tool, and how that selection is displayed and made.