I don't believe the symlinks exist to make builds more easily accessible. I don't believe the builds are meant to be accessed directly from the file system under $JENKINS_HOME. If you access the builds using the Web UI, you will always have the same interface, regardless where you run Jenkins.
The only functional differences that come to mind are: * Jenkins running on Linux or Mac cannot execute a Batch file build step and * Jenkins running on Windows cannot execute a Shell script build step Jenkins will try, but it will usually fail either because cmd.exe or /bin/sh cannot be found. -- Sami Daniel Beck kirjoitti 20.6.2012 kello 23.55: > Hi all, > > I recently learned that when run on Linux, Jenkins uses symlinks to make > builds a bit more easily accessible on the file system. > > lrwxrwxrwx 1 danielbeck danielbeck 19 Jun 10 19:24 1 -> > 2012-06-10_19-24-57 > lrwxrwxrwx 1 danielbeck danielbeck 19 Jun 10 19:25 2 -> > 2012-06-10_19-25-52 > drwxr-xr-x 2 danielbeck danielbeck 4096 Jun 10 19:24 2012-06-10_19-24-57 > drwxr-xr-x 2 danielbeck danielbeck 4096 Jun 10 19:25 2012-06-10_19-25-52 > > This came as quite a surprise, and now I'm wondering what else is different > with Jenkins Master on different OSes and could affect my choice of OS for > the Master node. > > Is this documented anywhere? While the wiki contains instructions on how to > set up Jenkins, it doesn't mention functional differences in Jenkins between > operating systems. > > Regards, > Daniel >
