I have a windows machine where I have installed jenkins(master). Then I installed jenkins slave in cent os which is a SSH server. There is a github repository which I have checked out in that cent os machine. Now I wanted to configure a job from the master jenkins which is in window to perform git pull operation in the cent os. How can I do this? Please help me in this.
You can use "Restrict where this project can be run" from Configure job option in jenkins
you need to provide label name.
Related
I was using Jenkins 1.7.4 version in RHEL Linux server. I can able to configure the slave using "launch agent via execution of command on the master" option during slave setup.
Now we have upgraded jenkins to 2.121.1 version. Now we unable to find that option in the upgraded version.
How to fix this issue.
Manually I Installed command-launcher, jdk-tools plugin. Then it works.
I wanted to create ipa files with a Jenkins slave on mac. My Jenkins master is on Linux.
So when creating a job in master, I need to configure the Xcode plugin. So should I give the path and keychain in the slave?
Or is there a way to create the job in slave and the master triggering it?
Jenkins slaves are just "runners", they don't provide configuration page. All the job configurations are made on the master, even if it's a Linux machine.
Start by setting up a Jenkins slave on the Mac:
http://www.parsed.io/setup-a-mac-slave-for-jenkins/
https://blog.samsaodev.com/how-to-setup-a-jenkins-slave-running-mac-osx-for-ios-projects-part-1/
I have setup lots of Windows Masters with Windows Slaves.
I have instructions for setting up a Linux Master.
However, what I would really like to do is to setup a Linux (ubuntu) Slave on a Windows master.
The issue is that my Windows master doesn't have a SSH option for slaves, so none of the Linux Slave instructions seem to apply.
Any ideas if this is possible and if so, how to go about it?
Frank
There shouldn't be any major differences between running a master on different operating systems.
I thought the SSH Slaves plugin came installed by default, but if not, you can try installing it from the plugin centre.
In therory Master is : Job and Slave is : Node (however that what im understand).
I installed JENKINS in 2 machines MAC OS X (maybe windows whatever), I set up my job with a correct repository and configure xCode in this job etc ... like same tutorial, i set up my slave etc ... all fine and 10/10 BUTTT this test is local test, in one machine.
My problem is : I want have SLave(Node) for building my xCode Project in MAC OS, and My Matser (job) in others server (why not my seconde machine MAC OS X), How i can establish connection between slave (Node) and Master(job) for building my project xCode in my Remote SLave.
Set your job to use "Restrict where this project can be run" by checking the box and put the name of the slave in the box (use quotes if there are spaces
I had a little trouble deciphering your questions so if this does not answer please rework what you are asking.
Easy set the IP address of the slave host machine in the Jenkins setup. Choose ssh as the communications method and set up accounting information on the slave machines jenkins setup. Make sure the slave machine can ssh to the account and machine you set up in jenkins. Your ready to roll
How to link jobs in Jenkins
Master job: "Trigger/call builds on other projects"
Slave job: Add a Condition Step build: "Run? Build Cause --> UpstreamCause (with The master project name)" and then copy the artifacts (.) from the "Master" job.
Don't forget to copy from the workspace and not from the latest successful build, since the master didn't finished yet and din't publish the artifacts.
I can only build my system on a FreeBSD 5 machine.
I am looking and introducing gerrit and Jenkins into my team.
I have setup the server running gerrit and Jenkins both on a Debian machine for now.
What is the standard way of dealing with Jenkins building on a remote server?
The standard way would be to install a Jenkins Slave on the remote server. See https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds
You then setup the job that must be built on a FreeBSD 5 machine, to only only run on that slave/node. This is can be achieved within the job configuration by specifying the FreeBSD machine by name.
If you don't want other Jenkin jobs to run on that FreeBSD machine, you can configure the slave to only run jobs that are tied to it. See step 4 in the JENKINS Step by step guide to setup master and slave machines for the config page that you need to do this.