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

Resolve naming inconsistencies in hudson interface - terminology

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • core
    • None

      First, do not take these request as fixed, we should find a clear naming and stick to it in all places in order to improve the user experiece and facilitate hudson adoption.

      Here are some of the inconsistencies I found:

      • job versus project
      • build (action), may not be the best because not every thing you run or execute on hudson is a build.
      • node versus slave

      We already have a page at http://wiki.jenkins-ci.org/display/JENKINS/Terminology but this is incomplete and reading it doesn't help too much.

      A good terminology should also include a list of `old terms`, terms that are outdated and to be replaced by newer variants.

          [JENKINS-7628] Resolve naming inconsistencies in hudson interface - terminology

          Sorin Sbarnea created issue -
          Daniel Beck made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-1968 [ JENKINS-1968 ]
          Kohsuke Kawaguchi made changes -
          Link New: This issue is related to JENKINS-31095 [ JENKINS-31095 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 137727 ] New: JNJira + In-Review [ 187645 ]

            Unassigned Unassigned
            ssbarnea Sorin Sbarnea
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: