10 Glossary used in Jenkins
Glossary used in Jenkins
Here are some words that you must be aware of. These are very popular in Jenkins world. It is Jenkins's vocabulary that will help you when you start using the Jenkins tool.
Artifact:
It is an immutable file that is generated during the build in the pipeline process. This file is saved on the Jenkins controller and can be accessed by the user.
Project:
It is a description of the task that will be performed on the Jenkins tool, like building a part of the software.
Pipeline:
It is a user-defined model that is used to execute the jobs. All the instructions related to the software building, software testing and software deployment are given in it. It is mainly used for continuous delivery.
Plug-in:
It is an extension that is provided by the Jenkins core team to perform the task easily.
Controller:
It is the center of the Jenkins tool. It controls all the processes like store configuration, loading of a plug-in, creating the user interface, etc.
Core:
It is the main Jenkins application, i.e., Jenkins.war file. It provides basic UI and other configurations for the process.
Executor:
It is the place where execution is done in the pipeline on a node.
Folder:
It is similar to that of the other folders in the file system. In the Jenkins, it is like a container for the pipeline and project.
URL:
A Jenkins URL is created when the execution of a process is being started. This URL is by default followed by a number, i.e., 8080.
Job:
It is like a part of the main project. When we have a heavy project, then it is divided into subparts. These subparts are known as jobs.
Master:
Your main Jenkins server is Jenkins master. It is a controller, which controls many Jenkins slaves. It is also used in the pipeline process, having master-slave architecture.
Slave:
A Jenkins slave is a program (contains a set of statements) written in a specific language. It performs all of the operations under the control of the Jenkins Master.
Agent:
It is like a container, which is connected with a Jenkins controller or master. It is operated according to the instructions given by Jenkins master.
Label:
It is the parameter of the Jenkins agent. It is a user-defined text used for grouping the Jenkins agent. This parameter tells that pipeline will run on the given label.
Trigger:
When the developer pushes the job for execution, then it is known as the triggering of the job.
Upstream:
Upstream job is part of the main execution process of the pipeline. A pipeline creates a new sub-pipeline related to it to perform task-parallel with it. It is triggered before the actual job is triggered. We can't trigger the actual job if the upstream job is failed.
Downstream:
The downstream job is the same as that of the upstream job, but the difference is: It is triggered after the actual job is triggered. We can't trigger the downstream job if the actual job is failed.
Node:
A node is a machine that executes the entire code written under it. It is used in the scripted pipeline process.
Stages:
It is a block in which all steps are available related to software creation. It is the part of the pipeline and performs many steps under itself. It is like the main body of the program.
Step:
The procedure performs under the stages are known as steps. A step is a single operation that is applied to jobs in the pipeline. There are many steps available in Jenkins, but "Build," "Test," and "Deploy" are the main steps that are used in almost all projects.
Build:
It is a step, which is performed inside the block stages. When a single project is executed in the pipeline, then its result is known as a build.
Test:
It is also a step; its work is to test the builds in the pipeline.
Deploy:
It is also a step used to deploy the software in the process.
Publisher:
It provides the reports (result status) and sends notifications in the process.
Workspace:
It is a directory of the node, where all the works of the pipeline process are performed.
Build Status (result):
Success:
The build has no bugs and compiled normally. Everything is up to the mark and satisfies all the regions.
Failed:
The build has got some dangerous errors in the compilation.
Aborted:
The build is broken down before achieving its goal. Example: Time out an error. The build gets aborted when the user stops the process manually.
Stable:
The build is achieved when there is no compilation error.
Unstable:
The build has some common errors, can be resolved easily. A build comes in an unstable stage when it is created successfully by the developer, but it's one or more publishing result is not up to the mark. It will give the result after resolving the issue easily.