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

Missing hash in client names if ClientNameFormat substitution fails

XMLWordPrintable

      This bug appears in the following conditions:

      • Client name contains ${EXECUTOR_NUMBER} variable

      High-priority issue appears if:

      • Concurrent builds are enabled
      • No NODE_NAME variable in client name
        => Missing hash in Client name => collisions in workspaces on different nodes

          [JENKINS-25559] Missing hash in client names if ClientNameFormat substitution fails

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-25226 [ JENKINS-25226 ]
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-23467 [ JENKINS-23467 ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "PR #60 (Web Link)" [ 11907 ]
          Oleg Nenashev made changes -
          Assignee Original: Rob Petti [ rpetti ] New: Oleg Nenashev [ oleg_nenashev ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Oleg Nenashev made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Oleg Nenashev made changes -
          Summary Original: Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions New: Missing hash in client names if ClientNameFormat substitution fails
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 159531 ] New: JNJira + In-Review [ 196115 ]

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: