I don't know now how that version of Jenkins used to distribute the load and the default node setup. AFAIK, if that jenkins infrastructure is based on one master then those jobs will be always triggered by those 'master slave', otherwise those jobs will require where to run.
Jenkins tries to allocate those jobs to the last node is was executed on, by default, unless that node is busy then will choose another one: - http://documentation.cloudbees.com/docs/cje-user-guide/_default_jenkins_behavior.html You can find useful the below confluence page: - https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds Cheers On Thursday, 25 February 2016 12:42:29 UTC, Alex Domoradov wrote: > > So, every time when I'll create a new job I must specify a node? Have I > correctly understood? > > It's a little bit strange, because we have another instance with Jenkins > (ver. 1.565.2) and there all jobs by default executes on MASTER node. If I > need a job will execute on some specific node then I just specify it on job > settings page as you mentioned before. > > On Thursday, February 25, 2016 at 2:19:53 PM UTC+2, Victor Martinez wrote: >> >> Hi, >> >> You might need to configure your jobs in order to use the 'master' >> label, it's part of the 'Restrict where this project can be run' >> configuration. Although using your master for building and so on it's ideal. >> >> Cheers >> >> On Thursday, 25 February 2016 09:30:07 UTC, Alex Domoradov wrote: >>> >>> Hello, >>> >>> >>> Some time ago Jenkins has started run jobs on slave node (win 7). >>> >>> >>> [EnvInject] - Loading node environment variables. >>> >>> Installing JDK jdk-8u74-oth-JPR >>> Downloading JDK from >>> http://download.oracle.com/otn-pub/java/jdk/8u74-b02/jdk-8u74-windows-x64.exe >>> Downloading 196405336 bytes >>> >>> Installing D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74\jdk.exe >>> >>> [jdk-sun-1.8.74] $ D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74\jdk.exe >>> /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress >>> INSTALLDIR=D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74 /L >>> D:\jenkins\tools\hudson.model.JDK\install1182473847874408631log >>> >>> Building remotely on win7 (WINDOWS) in workspace >>> D:\jenkins\workspace\resin-deploy >>> >>> Cloning the remote Git repository >>> ... >>> [EnvInject] - Injecting environment variables from a build step. >>> [EnvInject] - Injecting as environment variables the properties content >>> JAVA_HOME=/var/lib/jenkins/tools/hudson.model.JDK/jdk-sun-1.8.74 >>> >>> [EnvInject] - Variables injected successfully. >>> FATAL: Cannot find executable from the chosen Ant installation "ant-1.9.6" >>> Build step 'Invoke Ant' marked build as failure >>> SSH: Current build result is [FAILURE], not going to run. >>> Finished: FAILURE >>> >>> >>> The slave node was connected via >>> >>> >>> >>> > java -jar d:\jenkins-slave.jar -jnlpUrl >>> > http://jenkins.example.net:8080/computer/win7/slave-agent.jnlp -secret >>> > {SECRET} >>> >>> >>> >>> >>> For example build 10 was built on Master node (linux) and build 11 was >>> built on Slave (windows 7). How can I revert the old behavior and tell >>> Jenkins build all jobs on master node by default ? >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0129d9df-aad6-4c74-a3de-1812b4d0a9ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
