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

${hostname} is not being correctly resolved in slave workspace name

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Jenkins server running on Win2k8 server 64bit, 64bit JRE (0 executors)
      6 Jenkins slaves running on Win7 64bit, 64bit JRE (1 executor)
    • Similar Issues:

      Description

      Previously working builds have suddenly stopped being able to resolve $

      {hostname} for workspace name

      with the following settings in the job cfg
      >> Workspace (client) ms_${hostname}

      _evo11main
      >> Client name format for slaves ms_$

      {hostname}

      _evo11main

      previously this resolved to ms_build5pcw7_evo11main
      now it is resolving to ms_43_evo11main
      where 43 is the first part of the machine ip address (43.xx.xx.xx)

      nslookup works find in both directions for jenkins server and slave.

        Attachments

          Activity

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              richardtaylor Richard Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: