Set the “Restrict where this job can be run” check box in your job configuration and specify the name of your slave. If you add more slaves later, you can set labels for each slave and specify those in your job configs. See this reference documentation: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds
Don’t know if you resolved this problem, but I have just resolved the same issue from the other side. It appears Selenium and Firefox have difficulty talking to each other – I suspect Firefox ‘evolve’ changes over a number of releases, so backward and forward compatibility are not always guaranteed, and incompatibility always seems to … Read more
It does seem like you are confused about several aspects of Jenkins.. I think your question basically boils down to the following. What is a difference between a workspace and a build? So, here are some thoughts on this topic: Builds are historical data. They (usually) don’t change like a workspace does during building/checkout. Builds … Read more
To restart Jenkins manually, you can use either of the following commands (by entering their URL in a browser): (jenkins_url)/safeRestart – Allows all running jobs to complete. New jobs will remain in the queue to run after the restart is complete. (jenkins_url)/restart – Forces a restart without waiting for builds to complete.
This wasted so much time on my Jenkins Windows slave. I knew git was in the path because I executed “where git” in the build job’s batch command. Apparently the Jenkins Git Plugin executes ** before ** the environment is inherited. SET YOUR SLAVE’s PATH to Git ( Just DO IT !! ) 1) Go to your Windows slave … Read more
Finally, this post helped me to do away with the crumb problem but still securing Jenkins from CSRF attack. Solution for no-valid crumb included in the request issue Basically, we need to first request for crumb with authentication and then issue POST api calls with crumb as a header along with authentication again. This is … Read more
This problem might occur if you are behind corporate proxy and corporation uses its own certificate. Just add “–no-check-certificate” in the command. e.g. wget –no-check-certificate -qO – http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add – It works. If you want to see what is going on, you can use verbose command instead of quiet before adding “–no-check-certificate” option. … Read more
You can output the variables to same file in stage, then read back and assign to env at the beginning of each stage as following:
This problem might occur if you are behind corporate proxy and corporation uses its own certificate. Just add “–no-check-certificate” in the command. e.g. wget –no-check-certificate -qO – http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add – It works. If you want to see what is going on, you can use verbose command instead of quiet before adding “–no-check-certificate” option. … Read more
This bizarre message means that the trustStore you specified was: empty, not found, or couldn’t be opened (due to wrong/missing trustStorePassword, or file access permissions, for example). See also @AdamPlumb’s answer below.