Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31160

Update Jenkins UI not to call everything a "Build"

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Similar Issues:

      Description

      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 Udaypal Aarkoti 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.

        Attachments

          Issue Links

            Activity

            Hide
            magjac Magnus Jacobsson added a comment -

            "Run" or "Execution" perhaps?

            Show
            magjac Magnus Jacobsson added a comment - "Run" or "Execution" perhaps?
            Hide
            danielbeck Daniel Beck added a comment -

            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.

            Show
            danielbeck Daniel Beck added a comment - 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.
            Hide
            abayer Andrew Bayer added a comment -

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

            Show
            abayer Andrew Bayer added a comment - +1 to Run - it fits into the general feel better than "Execution".
            Hide
            orrc Christopher Orr added a comment -

            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.

            Show
            orrc Christopher Orr added a comment - 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.
            Hide
            magjac Magnus Jacobsson added a comment -

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

            Show
            magjac Magnus Jacobsson added a comment - +2 for Run +1 for Execution -1 for keeping Build
            Hide
            danielbeck Daniel Beck added a comment -

            Job: Promote builds when...

            Promoted Builds Plugin


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

            Patrick Wolf Something for our issue tracker, these are all CJP.


            The rest appear to be in core.

            Show
            danielbeck Daniel Beck added a comment - Job: Promote builds when... Promoted Builds Plugin Job: Skip Builds Job: Show Consolidated Build View Jenkins Analytics: BUILDS PER MASTER Jenkins Analytics: BUILDS Patrick Wolf Something for our issue tracker, these are all CJP. The rest appear to be in core.

              People

              • Assignee:
                Unassigned
                Reporter:
                hrmpw Patrick Wolf
              • Votes:
                4 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: