[JENKINS-31160] Update Jenkins UI not to call everything a "Build"

[timja]

Jenkins (core, plugins, etc.) has a tendency to call everything a "build". These days, "build" tends to conjure thoughts of Continuous Integration use cases only. In fact, our very own uday wrote a plugin so users could change the "build now" button to "deploy now" (or whatever his customer's heart desired).

There are many other areas in Jenkins where the notion of "build" is the default. This RFE requests updating them to a more fashionable term.

It seems there are two options:

• Jenkins either needs to be "smarter" to know there are different types of things (eg: Build Job, Test Job, Deploy Job, Pipeline)
• Or we need a more acceptable generic word than "build" (since it seems less fashionably to point at CI use cases specifically) - eg: everything is a "job" (job history, job queue, and so on)

Quick List of Build References:

• Global: Build History
• Global: Build Queue
• Global: Build Executor Status
• Job: Discard Old Builds
• Job: Build Now
• Job: Build with Parameters
• Job: Skip Builds
• Job: Build History
• Job: Last build
• Job: Last failed build
• Job: Last unsuccessful build
• Job: Show Consolidated Build View
• Job: This build is parameterized
• Job: Promote builds when...
• Job: Disable Build
• Job: Execute concurrent builds
• Job: Build Triggers: *
• Job: Build Environment: *
• Job: Build Steps: *
• Job: Post-build Actions: *
• Jenkins Analytics: BUILDS PER MASTER
• Jenkins Analytics: BUILDS

relates to JENKINS-7628 but that ticket was closed with "Not a Bug" resolution.

---

Originally reported by hrmpw, imported from: Update Jenkins UI not to call everything a "Build"

• status: Open
• priority: Minor
• resolution: Unresolved
• imported: 2022/01/10

[timja]

magjac:

"Run" or "Execution" perhaps?

[timja]

danielbeck:

Execution would nicely mirror the Executor term already used.

OTOH Run would be less confusing from a developer POV as that's the common supertype for all classes implementing this.

[timja]

abayer:

+1 to Run - it fits into the general feel better than "Execution".

[timja]

orrc:

I don't suppose we're going to get consensus on this before Jenkins 2.0 — or what do you think?

I'm working on JENKINS-33364, and I'm ending up constructing something of an English styleguide for at least the Jenkins in-app documentation (e.g. "hostname" not "host name"; "agent" not "slave") — to this end, knowing what to call agents / machines / jobs / projects / items / pipelines / builds / runs / whatever would be useful.

[timja]

magjac:

+2 for Run
+1 for Execution
-1 for keeping Build

[timja]

danielbeck:

Job: Promote builds when...

Promoted Builds Plugin

---

Job: Skip Builds
Job: Show Consolidated Build View
Jenkins Analytics: BUILDS PER MASTER
Jenkins Analytics: BUILDS

hrmpw Something for our issue tracker, these are all CJP.

---

The rest appear to be in core.

[timja]

martinjost:

Inside our CI team, we usually call a "run" (of a job), what Jenkins terms "Build",

We have seperate jobs for actual "build" (compile/link) and "test".
So we got several times questions from our developers, why "test" is called "Build" in CI and I had to tell, that Jenkins happens to have decided so ...

[timja]

[Originally related to: JENKINS-31095]

[timja]

[Epic: JENKINS-31156]