[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config

9 views
Skip to first unread message

kwirth@perforce.com (JIRA)

unread,
May 17, 2018, 3:44:02 PM5/17/18
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
 
Jenkins / Improvement JENKINS-47005
Let user specify p4 workspace root in manual config
Change By: Karl Wirth
Labels: P4_VERIFY
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

kwirth@perforce.com (JIRA)

unread,
May 17, 2018, 3:46:02 PM5/17/18
to jenkinsc...@googlegroups.com

punith416@gmail.com (JIRA)

unread,
Mar 26, 2019, 5:12:02 AM3/26/19
to jenkinsc...@googlegroups.com
Punith C commented on Improvement JENKINS-47005
 
Re: Let user specify p4 workspace root in manual config

This is an interesting feature which gives me more control over where I want to keep my source code and not necessarily under Jenkins installation.

As a workaround every times I had to fetch the client and update the client root before proceeding to populate the workspace. 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kwirth@perforce.com (JIRA)

unread,
Mar 18, 2020, 6:42:04 AM3/18/20
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
Change By: Karl Wirth
Labels: P4_VERIFY
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

guyjoules@gmail.com (JIRA)

unread,
Mar 19, 2020, 2:05:03 AM3/19/20
to jenkinsc...@googlegroups.com
Guy Catz commented on Improvement JENKINS-47005
 
Re: Let user specify p4 workspace root in manual config

We would also like to see that coming. We need to sync to different drives and therefore must update the root folder. The lack of that prevents us from working smoothly with the p4 plugin.

kwirth@perforce.com (JIRA)

unread,
Apr 30, 2020, 10:11:02 AM4/30/20
to jenkinsc...@googlegroups.com
Karl Wirth edited a comment on Improvement JENKINS-47005
*Possible workarounds:*
# Replace contents of Jenkinsfile with a simple non instruction so that no real build is performed.
# Remove all access to the branch for the Jenkins user through Perforce protections.
# JENKINS-47066
# If using pipleline you can use the 'ws' directive:
{code:java}
    stage("SyncMyWorkspace") {
      steps {
         ws('/var/lib/jenkins/XXXXX/KarlTest/') {
    p4sync charset: 'none', credential: 'JenkinsMasterAdminUser', format: 'jenkins-${NODE_NAME}-${JOB_NAME}', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource('//depot/test/...')
    echo "DONE"
           }
      }
    }
{code}

 

kwirth@perforce.com (JIRA)

unread,
Apr 30, 2020, 12:21:03 PM4/30/20
to jenkinsc...@googlegroups.com

Comments from JENKINS-62123:

 
In the P4Jenkins plugin, please add the functionality to "checkout to subdirectory" when defining either "Stream" or "View Mappings"  (for Freestyle jobs).

Customer would like to have the functionality to define a stream, and also have this stream checkout into a sub directory in the Jenkins workspace without having to fill in the "View Mappings" from a client spec by hand, with the directory present. 

kwirth@perforce.com (JIRA)

unread,
Apr 30, 2020, 12:22:03 PM4/30/20
to jenkinsc...@googlegroups.com

kwirth@perforce.com (JIRA)

unread,
Apr 30, 2020, 12:22:04 PM4/30/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages