• HOME
  • TECH BLOG
  • MIGRATING TO AMAZON WEB SERVICES
  • IT PROJECT MANAGEMENT BLOG
  • Q&A
  • INTERACTIVE LEARNING

JENKINS TERMINOLOGY



JENKINS MASTER



Your main Jenkins server is the Master.

This is where the Jenkins server software is installed.

By default your jobs will be triggered in the Master.


The Master’s job is to handle:

* Scheduling build jobs.

* Dispatching builds to the slaves for the actual execution.

* Monitor the slaves (possibly taking them online and offline as required).

* Recording and presenting the build results

* A Master instance of Jenkins can also execute build jobs directly.



JENKINS SLAVE



A Slave is a Java executable that runs on a remote machine.


The following are the characteristics of Jenkins Slaves:

* It hears requests from the Jenkins Master instance.

* Slaves can run on a variety of operating systems.

* The job of a Slave is to do as they are told to, which involves executing build jobs dispatched by the Master.

* You can configure a project to always run on a particular Slave machine, or a particular type of Slave machine, or let Jenkins pick the next available Slave.



workspace directory



The workspace directory is where Jenkins builds your project.


It contains the source code.


Jenkins checks it out in addition to any files generated by the build itself.


The workspace directory can also be called the root directory.


Wherever your job is triggered (whether it's on the slave or master) then that's where the workspace directory will be located.


So for example if you trigger a job in a development server the workspace or root directory will be located on that development server.


While adding the slave you will add the workspace directory in the configuration on the Jenkins web console.


Location of the workspace directory for the Master server: /var/lib/jenkins/workspace


Location of the workspace directory for slave servers:

/root/workspace


If your user was not a root user as above then the location would have been:

/home/"user"/workspace

where "user" is the name of your user.

The root user get its own directory whereas any other user is located under the /home directory.



build directory



Where the job configuration is available.


The job configuration is only available in the Master server and not any of the slave servers.


The jobs will show which jobs have been run on all servers.

So if you have run multiple jobs located on different servers they will all show under the build directory of the Master/Jenkins server.


Location of the build directory - var/lib/jenkins/jobs



artifacts



Artifacts can be used to represent data created as a side-effect of running a Jenkins build.


Artifacts are files which are associated with a single build.


A build can have any number of artifacts associated with it.




executor



A slot for execution of work defined by a Pipeline or Project on a Node.


A Node may have zero or more Executors configured which corresponds to how many concurrent Projects or Pipelines are able to execute on that Node



CERTIFIED CLOUD EXPERTS | AWS PARTNER NETWORK
CLOUD CONSULTING FIRM | (516) 387-2085 | CONTACT US