An agent is typically a machine, or container, which connects to a Jenkins master and executes tasks when directed by the master.
Result of a single execution of a Project
The primary Jenkins application (
jenkins.war) which provides
the basic web UI, configuration, and foundation upon which Plugins
can be built.
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.
The main url for the jenkins application, as visited by a user. e.g. https://ci.jenkins.io/
A deprecated term, synonymous with Project.
User-defined text for grouping Agents, typically by similar
functionality or capability. For example
linux for Linux-based agents or
docker for Docker-capable agents.
The central, coordinating process which stores configuration, loads plugins, and renders the various user interfaces for Jenkins.
A user-configured description of work which Jenkins should perform, such as building a piece of software, etc.
A user-defined model of a continuous delivery pipeline, for more read the Pipeline chapter in this handbook.
An extension to Jenkins functionality provided separately from Jenkins Core.
Part of a Build after the completion of all configured Steps which publishes reports, sends notifications, etc. A publisher may report Stable or Unstable result depending on the result of its processing and its configuration. For example, if a JUnit test fails, then the whole JUnit publisher may report the build result as Unstable.
A secondary url used to serve potentially untrusted content (especially build artifacts). This url is distinct from the Jenkins URL.
stage is part of Pipeline, and used for defining a conceptually distinct
subset of the entire Pipeline, for example: "Build", "Test", and "Deploy",
which is used by many plugins to visualize or present Jenkins Pipeline
A disposable directory on the file system of a Node where work can be done by a Pipeline or Project. Workspaces are typically left in place after a Build or Pipeline run completes unless specific Workspace cleanup policies have been put in place on the Jenkins Master.
The Build was interrupted before it reaches its expected end. For example, the user has stopped it manually or there was a time-out.
The Build had a fatal error.
The Build has no compilation errors.
The Build had some errors but they were not fatal. A Build is unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the Build will be marked unstable.