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

Env vars not always handled in project name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • synergy-plugin
    • None
    • Platform: All, OS: All

      Setting up a distributed build with Hudson/synergy, I do a synergy 'copy
      project' for each (windows) node, using the computer name to identify project
      versions.
      Then, in the "project name" field, I enter something like "project~${COMPUTERNAME}".

      This is done as a workaround when two nodes would attempt to set different work
      area paths to the same project (This is not perfect, it does not guarantee that
      checkouts will be identical).

      In the console output, I notice that, when the plugin sets the work area path,
      it does not always use the dynamic value (replacing "COMPUTERNAME" with the
      actual name), but the uncomputed 'raw' string "${COMPUTERNAME}".

      Hint: This is probably due to SynergySCM.setAbsoluteWorkarea using this.project,
      instead of a computed dynamic value...

            jribette jribette
            ldore ldore
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: