What Are Jobs and Builds?

A job is a configuration that defines your application's builds. A build is the result of a job’s run.

A job defines where to find the source code files, how and when to run builds, and the software and environment required to run builds. When a build runs, it packages application archives that can be deployed to a web server. A job can have hundreds of builds, each generating its own artifacts, logs, and reports.

Here are some terms that this documentation uses to describe the build features and components:

Term	Description
Build system	Software that automates the process of compiling, linking and packaging the source code into an executable form.
Build executor template	A build executor template defines the operating system and software packages installed on a VM build executor. A build executor template must be created before VM build executors can be added to it. See What Are VM Build Executors and Build Executor Templates?.
VM build executor	A VM build executor is an OCI or OCI Classic VM compute instance dedicated to running builds of jobs that organization members define in VB Studio projects. A VM build executor is always associated with a build executor template. Each build uses one VM build executor. See What Are VM Build Executors and Build Executor Templates?.
Build artifact	A file generated by a build. It could be a packaged archive file, such as a .zip or .ear file, that you can deploy to a build server.
Trigger	A condition to run a build.