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

Provide the option to use the client spec from the server verbatim


    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
    • Environment:
      Hudson 1.347
      Perforce Plugin 1.0.21
      Hosted on Linux FC11
      Perforce Server version: P4D/SOLARIS10X86_64/2008.1/176084 (2008/11/20)
    • Similar Issues:


      I am a first time user of Hudson. I have to say the tool was very easy to install and configure compare to other tools. The hardest part was understanding the way the build uses the Perforce plugin in terms of the workspace. When I created my first job I wanted Hudson to use a preexisting perforce workspace. I wanted to run builds in this preexisting workspace so I did not expect Hudson to try to change the root directory or viewspec or anything. In order to define this type of job you need to go into 'advanced' features and you need to configure a root directory and deselect 'let hudson manage my viewspec'. Well I did not see that option and when I ran the build very bad things happened to my workspace. I did recover but it was frustrating.

      So... The feature request is to provide the option to use a preexisting perforce workspace as it is defined on the server. User would specify the workspace name only. The job should not make any attempt to modify any portion of the client spec.

      I realize this may seem like a limited type of build but it has been very useful in terms of getting started with Hudson and gaining confidence in the tool.




            • Assignee:
              rpetti Rob Petti
              mchartier mchartier
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: