What is a Job in Jenkins? - Jenkins Tour #02

Basically, a job in Jenkins is any runnable task that is controlled by Jenkins. In recent Jenkins Documentation, the term job is replaced by the term project.

So job = project.

So let's see some of the jobs or projects available in Jenkins.

Type of Projects

FreeStyle Project

The most common type of project and normal build step for this type of project executes a hell(Linux) or batch(Windows) command. there are times you need to execute something on the batch or on the command line and this project provides that capability in an automated way. Also if you are not using Maven or Ant or you are using some other build system freestyle project is the way to go so you can call the invocation command at the end of the project. Also, these project normally ends in shell command but that doesn't mean they always need to end in shell command.

Pipeline

This type is used to be called workflow. Normally written in Jenkins Domain Specific Language (DSL). This type is used for more things that are complicated or span across multiple nods. The DSL written is put into a Jenkinsfile which tells Jenkins what to do and then that Jenkinsfile can be popped into source control so that the configuration can be iterated along with the source code. So that the pipeline workflow can actually change as needed to support the source that's being put in there. these are for things that don't fit in a freestyle project. You are got a multi-configuration pipeline going on where you are building for different OSes. When you get a Jenkins project where it is really large got a large scope that when you want to run a pipeline.

Multi-configuration Project

This is for projects that will be tested on multiple environments and require different configurations, depending on those environments. Basically, if you are building for multiple operating systems say you have an Android project, iso project windows project you are going to have to build agents on notes to support that, So you are going to have multiple configurations for these different nodes because you are going to be building different code.

GitHub - Organization

Curtain version control platforms allow different repositories to be organized into organizations. What this does is let Jenkins interact with it. So Jenkins can recognize that those repositories are part of an organization.

Folder

Allows to group projects together. The folder is technically not a project. it acts as a kind of directory structure for projects. and the folder name becomes a part of the project's path.

Multi-Branch Pipeline

In this kind of project, Jenkins uses a Jenkins file to mark repositories. if a branch is created in that repository, Jenkins will make a new project in Jenkins in that branch.

Job/Project Scope

This is something really important when it comes to the security of the projects. Normally project scope includes all the items that are part of that job/project. In some cases, there are global libraries that are brought into the scope of a project simply by being included. Other items that are declared within a project only exist in that project's scope and are not available as a shared resource.

We'll mee in a new topic called XYZ soon.