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

Perforce / Source Code Plugin Doesn't Perform Variable Expansion on Environment Variable When Evaluating if Workspace Exists

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • p4-plugin
    • Jenkins Version: 1.744
      Tomcat Version: 6.0.35
      OS: Amazon Linux Version 2012.03
      Perforce Plugin: 1.3.17

      Steps to Reproduce
      1. Create a Job
      2. In Source Code Management, Select "Perforce" Source Code Management Tool
      3. In the Project Details: Workspace (client) field enter myworkspace-${JOB_NAME}
      4. Check the "Let Jenkins Create Workspace" box
      5. Build Job - the workspace will be created.
      6. Return to the Job page
      7. Look under Project Details: Workspace (client) - despite the Workspace being created (it was created in step 5) the warning "Workspace does not exist. If "Let Hudson/Jenkins Manage Workspace View" is check the workspace will be automatically created." is still shown despite the workspace existing.

          [JENKINS-14969] Perforce / Source Code Plugin Doesn't Perform Variable Expansion on Environment Variable When Evaluating if Workspace Exists

          Colin Johnson created issue -
          Rob Petti made changes -
          Assignee New: Rob Petti [ rpetti ]
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 145670 ] New: JNJira + In-Review [ 176419 ]
          Jenkins IRC Bot made changes -
          Component/s New: p4-plugin [ 19224 ]
          Component/s Original: perforce-plugin [ 15506 ]

            Unassigned Unassigned
            colinbjohnson Colin Johnson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: