I don't have a $JENKINS_HOME/script directory accessible from the login user (jenkins) which runs the Jenkins process on Debian or on Oracle Linux. I'm also not sure how to execute Functions.IsWindows(). Is that invoking a groovy script from the web browser rather than from an operating system shell outside Jenkins ? If so, do I need to install a groovy plugin, or is there a tutorial which could suggest how to invoke that script?
The VNC plugin is checked to not run VNC on Windows, and VNC definitely runs on the master node, so I'm reasonably confident that some part of the Jenkins infrastructure knows that the machine is not Windows. The "system information" screen (http://localhost:8080/systemInfo) shows os.name as "Linux" and os.arch as "amd64", so I think the Java runtime knows it is on Linux. Mark Waite >________________________________ > From: Vojtech Juranek <vjura...@redhat.com> >To: jenkinsci-users@googlegroups.com >Sent: Saturday, July 21, 2012 3:00 PM >Subject: Re: Re: LTS 1.466.1 RC1 testing > >Hi Mark, >thanks for spotting it! > >I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine for me. >You probably suffer from JENKINS-13007 [1], the last comment under this issue >also states that this issue start to appear on linux since 1.1.21. It >obviously appear only on some machines, but I have currently no idea what >triggers this problem. > >In 1.1.21 was one commit related to this issue [2], but it should affect only >windows machines... Just for sure, could you please go to $JENKINS_HOME/script >and run following command: >Functions.isWindows() >if Jenkins for some strange reason thinks that it runs on windows? > >Thanks >Vojta > >[1] https://issues.jenkins-ci.org/browse/JENKINS-13007 >[2] https://github.com/jenkinsci/git- >plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc > >On Friday 20 July 2012 20:21:58 Mark Waite wrote: >> I installed the release candidate and cannot seem to checkout with the >> latest release of the Git plugin. Has anyone else successfully used Git >> plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? >> >> I had seen the same problem with an existing installation and rolled back to >> 1.1.20 on that existing installation. Unfortunately, it is not that >> simple with a new installation. >> >> Mark Waite >> >> >________________________________ >> > >> > From: Vojtech Juranek <vjura...@redhat.com> >> > >> >To: jenkinsci-...@googlegroups.com; jenkinsci-users@googlegroups.com >> >Sent: Friday, July 20, 2012 5:04 PM >> >Subject: LTS 1.466.1 RC1 testing >> > >> >Hi, >> >LTS 1.466.1 RC1 is now available for download [1], thus we can start >> >testing. As usual, I would like to ask for your help. If you stage RC in >> >you stage environment or just download RC and try to run it, please drop a >> >note on wiki page [2], shortly describe what you tested, where it was done >> >(OS, JDK version) and the result. >> > >> >Feel free to add new tests or repeating test which was already done by >> >someone else in different env. - it is also very useful as some bug can >> >appear only on e.g. one OS but not on other etc. >> > >> >Any test is very helpful, especially in case of new major LTS RC. >> > >> >Thanks in advance >> >Vojta >> > >> >[1] http://mirrors.jenkins-ci.org/ >> >[2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing > > >
