[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title Karl Wirth commented on JENKINS-49141 Re: P4 plugin removed BOM from utf8 files Hi ram Shukla - Please provide a screenshot of where you are seeing this error. Is it with the file you synced when you try to use it or when running the job? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187977.1516811255000.24531.1589183100308%40Atlassian.JIRA.
[JIRA] (JENKINS-59922) Publish should use p4 reconcile -t to detect filetype changes
Title: Message Title Karl Wirth commented on JENKINS-59922 Re: Publish should use p4 reconcile -t to detect filetype changes Updating to highlight this. Please discuss at next sprint planning meeting. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202721.1571927316000.20311.1588340100165%40Atlassian.JIRA.
[JIRA] (JENKINS-59922) Publish should use p4 reconcile -t to detect filetype changes
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59922 Publish should use p4 reconcile -t to detect filetype changes Change By: Karl Wirth Labels: P4_A P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202721.1571927316000.20310.1588340040069%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.20046.1588263720623%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Labels: P4_A P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.20048.1588263720692%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth commented on JENKINS-47005 Re: Let user specify p4 workspace root in manual config 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. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.20034.1588263660229%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-62123 P4 Plugin should allow checkout to subdirectory Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206036.1588253201000.20032.1588263600259%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Karl Wirth commented on JENKINS-62123 Re: P4 Plugin should allow checkout to subdirectory Hi Dan Dawson - Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206036.1588253201000.20030.1588263600226%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title
Karl Wirth edited a comment on JENKINS-47005
Re: Let user specify p4 workspace root in manual config
*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/X/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}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.19962.1588255860326%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title
Karl Wirth commented on JENKINS-62123
Re: P4 Plugin should allow checkout to subdirectory
Hi Dan Dawson I think I'm going to link this request to JENKINS-47005 if that's acceptable. Are you using Freestyle or pipeline jobs? In pipeline you can use the 'ws' directive as workaround. For example the following sets the root directory for the command in brackets to '/var/lib/jenkins/X/KarlTest':
pipeline {
agent { label 'master' }
stages {
stage("SyncMyWorkspace") {
steps {
ws('/var/lib/jenkins/X/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/...')
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Karl Wirth commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu - Sorry I'm going to need more the information I requested above. Note that if you are an exsiting Perforce customer you may already have a NDA in place with us. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.18830.1588072920160%40Atlassian.JIRA.
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Karl Wirth commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu - I havent seen the email yet so just wanted to check if you were able to email to us the private information I have requested. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.17355.1587742860124%40Atlassian.JIRA.
[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Labels: P4_SUPPORT P4_DOC jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16269.1587629640210%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Aha. Another Jenkins feature I never knew about. Thanks. Great that it's now working and thanks for correcting the typos in the other job. Yes I agree this should be documented so passed this job to our doc team. I'm going to suggest the following wording, but they will tweak it as needed to match the documentation standards and correct grammar: Note that when using build steps such as 'Execute Shell' the standard Perforce variables P4PORT, P4USER and P4CLIENT are not set in the environment. This is to ensure the plugin does not overwrite variables on preconfigured build environments. If a build step needs access to these values the variables P4_PORT, P4_USER and P4_CLIENT can be used. For example in a shell script: export P4CLIENT=$P4_CLIENT To make the standard variables accessible by default they can be set in the 'Global properties' section on the Jenkins 'Configure System' page. For example: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-59-08-936.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16263.1587628800209%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-57-39-950.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16260.1587628680199%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-55-54-786.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16257.1587628560215%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Thanks for those kind words. The developers have confirmed that 1.3.35 was the old community plugin. That did set the variables. The new plugin developed by Perforce has never set the variables because we were worried about stamping on environment variables that had been preconfigured already on build slaves. I have therefore raised the following enhancement request: https://issues.jenkins-ci.org/browse/JENKINS-62008 The workaround would still be the same that you need to manually set P4CLIENT in the build script based on P4_CLIENT. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.15770.1587556740612%40Atlassian.JIRA.
[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-04-22 11:54 Environment: 1.10.12 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth The old community P4 plugin used to expose the variables P4PORT, P4USER and P4CLIENT as environment variables for scripts to use. The new plugin on purpose uses different variables to ensure we dont override variables that are already set in the environment. Would be good if we had the option to also automatically set P4PORT=P4_PORT, P4USER=P4_USER and P4_CLIENT=P4_CLIENT. Add Comment
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61995 P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.15577.1587542280305%40Atlassian.JIRA.
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Karl Wirth commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu - I have just tested with a Windows 10 build slave against a Linux 13.2 server and for me it works OK so there must be something else going on. The error message suggests there was anetworking problem. Can you please send an email to supp...@perforce.com containing the following information: Screenshot of your Jenkins credential P4D log file for the time of your tets Output from 'p4 -Ztag info' Output from 'p4 configure show' Please put the Jenkins job number (JENKINS-61995) in the description or heading. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.15575.1587542280279%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Not ignoring you but dont know the answer yet. Checking with the developers and will let you know when I have something. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14979.1587484260129%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4_CLIENT environment variable non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4_CLIENT environment variable non-reentrant Change By: Karl Wirth Summary: P4CLIENT P4_CLIENT environment variable non-reentrant Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.14975.1587483180229%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
Karl Wirth commented on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi David Rodriguez, Thanks. The SCM class not longer hard codes all that information. In later versions of the plugin everything is built on the fly. So instead of specifying P4PORT and P4USER you pull in the Jenkins credential that encapsulates P4PORT, P4USER and P4PASSWD:
p4-userpass
P4CLIENT is also dynamically built based on 'name':
jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
For example if your node is WIN10, your job is mybuild and it runs on executor (Jenkins build thread) 1 the P4CLIENT (variable P4_CLIENT) would be:
jenkins-WIN10-mybuild-1
If you knew the job only ever runs on one node you could hard code the client name in the job definition to be 'ci-admin-ui-4.2'. As for the error its occurring after P4Jenkins has finished and after the command "/data/jenkins_home/tools/apache-maven-3.6.3/bin/mvn -s " has executed. Also P4Jenkins doesnt use the 'p4' binary it uses P4Java that is dynamically sent to the slave as teh job executes:
ha:4Lo+a7u/lzaTkq1HGH3U8JSMfSgah36g77z15FvpSvDYYB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYA==[ERROR] Failed to execute goal com.mycom:mycom-build-info-plugin:1.0.14:create (vernum) on project admin.ui: Unable to fetch p4 head version for path/data/jenkins_home/workspace/admin-ui-4.2: P4 process `/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...` returned error code;rc;1;Error message;... - must create client 'ip-10-21-2-84' to access local files. -> [Help 1]
Note that it's running '/bin/sh -c p4'. So if this is not Maven then it is another script or job that is being executed by the Jenkins job. The problem is that the P4CLIENT being built on the fly is not being passed to the environment that the job is executing under which is why I think it needs to be passed or picked up explicitly. For example if it's bash try using 'export P4CLIENT=P4_CLIENT'. For example below is the output when I run a shell script from the job that displaye P4CLIENT and P4_CLIENT: Note that P4CLIENT is not set but P4_CLIENT is.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-20-13-40-22-145.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14036.1587386460169%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13034.1587108420416%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez This looks likes it a problem in Maven (possibly P4Maven if you are using it) not P4Jenkins. We see P4Jenkins succesfully doing it's sync against a the client 'jenkins-jenkins-slave-test1-admin-ui-4.2-0' here on a node called 'ip-10-21-2-84': P4 Task: syncing files at change: 290033 (p4):cmd:... p4 sync -q /data/jenkins_home/workspace/admin-ui-4.2/...@290033 p4 sync -q /data/jenkins_home/workspace/admin-ui-4.2/...@290033 Then later on when the Maven command runs: [admin-ui-4.2] $ /data/jenkins_home/tools/apache-maven-3.6.3/bin/mvn -s /data/jenkins_home/maven_repository/settings.xml -Pmycomci clean deploy -B -U -Dit.skip=true we see the error: +LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYA==[ERROR] Failed to execute goal com.mycom:mycom-build-info-plugin:1.0.14:create (vernum) on project admin.ui: Unable to fetch p4 head version for path/data/jenkins_home/workspace/admin-ui-4.2: P4 process `/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...` returned error code;rc;1;Error message;... - must create client 'ip-10-21-2-84' to access local files. -> [Help 1] ha:4Lo+a7u/lzaTkq1HGH3U8JSMfSgah36g77z15FvpSvDYYB When P4CLIENT is not set in the environment we default to using the hostname for the client (in this case 'ip-10-21-2-84'. Looking at the maven docs (https://www.perforce.com/manuals/p4maven/index.html) you may need to explicitly pass the client name onto Maven. Possibly: mvn -Dmaven.scm.perforce.clientspec.name=$P4_CLIENT .
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Labels: P4_SUPPORT jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.13036.1587108420439%40Atlassian.JIRA.
[JIRA] (JENKINS-59750) Quiet all Perforce output when quiet:true.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59750 Quiet all Perforce output when quiet:true. Change By: Karl Wirth Labels: P4_B P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202473.1570806978000.11538.1586951160212%40Atlassian.JIRA.
[JIRA] (JENKINS-59750) Quiet all Perforce output when quiet:true.
Title: Message Title Karl Wirth commented on JENKINS-59750 Re: Quiet all Perforce output when quiet:true. In addition the output in 'p4 changes -m1' can trip up log analyzers which fail builds when error messages are detected. Would be good if this was also hidden from the log. For example this is from a standard polled freestyle job: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/00640681_Polling_Exclude_User Executor number at runtime: 0 (p4):cmd:... p4 login -s p4 login -sUser super ticket expires in 5 hours 15 minutes.(p4):stop:3 (p4):cmd:... p4 client -o jenkins-master-00640681_Polling_Exclude_User-3 p4 client -o jenkins-master-00640681_Polling_Exclude_User-3(p4):stop:4 (p4):cmd:... p4 info p4 info(p4):stop:5 (p4):cmd:... p4 info p4 info(p4):stop:6 (p4):cmd:... p4 client -o jenkins-master-00640681_Polling_Exclude_User-3 p4 client -o jenkins-master-00640681_Polling_Exclude_User-3(p4):stop:7 (p4):cmd:... p4 counter change p4 counter change(p4):stop:8 (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-master-00640681_Polling_Exclude_User-3/... p4 changes -m1 -ssubmitted //jenkins-master-00640681_Polling_Exclude_User-3/...Change 89712 on 2020/04/15 by super@test_ws 'Fix Error Message: FATAL ERROR at line 1234' The above 'FATAL ERROR' in the changelist description would fool the paser. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-59750) Quiet all Perforce output when quiet:true.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59750 Quiet all Perforce output when quiet:true. Change By: Karl Wirth Summary: Quiet all Perforce file list output when quiet:true. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202473.1570806978000.11524.1586950860377%40Atlassian.JIRA.
[JIRA] (JENKINS-61825) P4 - Additional build occurs
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Karl Wirth Labels: P4_SUPPORT p4plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205678.1586224029000.7374.1586247360500%40Atlassian.JIRA.
[JIRA] (JENKINS-61825) P4 - Additional build occurs
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205678.1586224029000.7372.1586247360464%40Atlassian.JIRA.
[JIRA] (JENKINS-61825) P4 - Additional build occurs
Title: Message Title
Karl Wirth commented on JENKINS-61825
Re: P4 - Additional build occurs
Hi Kevin Park The Perforce trigger you are using tells all jobs to wake up and check if they need to be built. Therefore any job that has:
triggers { p4Trigger() }
will wake up and check if it needs to be built. In your case there are new changes so it will run the build. If you are after a more targeted build you need to remove the 'triggers' line above from your pipeline script and call the direct URL for the job in your Perforce trigger. For example:
http://MyJenkinsServer:8080/job/MyJobName/job/MyBranchName/build?delay=0sec
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth assigned an issue to Kevin Williamson Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Change By: Karl Wirth Assignee: Kevin Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205622.1585835118000.5258.1585835280224%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205622.1585835118000.5260.1585835280317%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-04-02-14-43-10-072.png, image-2020-04-02-14-43-53-073.png Components: p4-plugin Created: 2020-04-02 13:45 Environment: p4-plugin 1.10.12 Priority: Critical Reporter: Karl Wirth A recent security change has enforced that Swarm needs to send the paramaters of the job as a POST not GET. To acheive this in Swarm you need to move the paramaters that were in the URL after '?' to the 'Post BODY' section. For example: becomes: Add Comment
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205574.1585583601000.3004.1585583760157%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Change By: Karl Wirth Environment: p4-plugin 1. 10. 1. 9 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205574.1585583601000.3003.1585583760110%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-03-30 15:53 Environment: p4-plugin 1.10.9 Priority: Blocker Reporter: Karl Wirth When scanning for changes in multibranch pipelines we use p4 changes -m1 //Path/...@now. This is triggering a similar resource behavior to: JENKINS-57870 For example with a big dataset in the multibranch scan log we see: p4 changes -m1 //Path/branch/...@now Request too large (over 50); see 'p4 help maxresults'. ERROR: [Mon Mar 30 13:07:05 CEST 2020] Could not fetch branches from source d5fe37f7-6c40-4111-af23-d4f539fec120 com.perforce.p4java.exception.RequestException: Request too large (over 50); see 'p4 help maxresults'. When checking this at the command line we see that limiting the query or dropping '@now' works: $ p4 changes -m1 //path/branch/...@now Request too large (over 50); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/...@2020/03/30 Request too large (over 50); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/... Change 62552 on 2020/03/30 by user@PC1 'CL Description'$ p4 changes -m1 //path/branch/...@52552,62552 Change 62552 on 2020/03/30 by user@PC1 'CL
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.1185.1585308000290%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth closed an issue as Postponed More invstigation required. Will return to this at a later date. Jenkins / JENKINS-51552 Cannot replay pipelines - files are read-only Change By: Karl Wirth Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I fully understand and I hope things are OK with you. As soon as there is anything I can do to help, please let me know. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.324.158500405%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I've just been going through requalifying old jobs and still cant reproduce this problem. Are you avalable later in the week so we could have a Webex? If you are please drop an email to supp...@perforce.com for my attention so we can arrange it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.12104.1585063560291%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston Finally got a chance to test this properly and still no luck in reproducing it. Can you please send an email to 'supp...@perforce.com' for my attention and send the full console logs for the two jobs when th. I'll try and figure out what I'm missing. Thanks in advance, Karl Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.9440.1584618840223%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.8838.1584528120232%40Atlassian.JIRA.
[JIRA] (JENKINS-61450) Cant filter streams with P4Groovy
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-61450
Cant filter streams with P4Groovy
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2020-03-12 09:56
Labels:
P4_VERIFY
Priority:
Minor
Reporter:
Karl Wirth
Following groovy code returns an empty result:
def output = p4.run('streams','-F','"Name=mainX"','//streams/...')
At the command line we get a result:
$ p4 streams -F "Name=mainX" //streams/...
Stream //streams/main mainline none 'mainX'
Usage Case: To get the stream path from the BRANCH_NAME when using multi branch and helix streams. Workaround:
def output = p4.run('streams','-T','Name,Stream','//streams/...')
output.eachWithIndex{item, index -> output[index].each{
key, value -> if (value == "mainX") println output[index]['Stream'];
}
}
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks. I'll test on WIndows and Linux build slaves and get back to you. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3812.1583842560252%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Karl Wirth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi Tom Cramer Can you please send me your trigger to 'supp...@perforce.com'. I want to check how you are calling the trigger. Thanks in advance, Karl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.7172.1582729860237%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Team Cloud - Thanks. I've let the devs know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197398.1549406943000.4308.1582296480281%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55985 Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Change By: Karl Wirth Comment: Raising to P1 to highlight to dev. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197398.1549406943000.4303.1582296240494%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Raising to P1 to highlight to dev. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197398.1549406943000.4299.1582296240446%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks and happy I can help. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.4132.1582278120237%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - I just tried the following test with 1.10.10 and it seemed to work: (1) Add CL 123 to downstream job directory. (2) Add CL 124 to upstream job directory. (3) Trigger upstream job that has a 20 second sleep as a build step. (4) Add 2 more CLs to each directory. (5) Downstream job is triggered with CL124 as the paramater and jobs is pinned to that CL. P4-Plugin looks for most recent CL in downstream depot path and syncs CL 123. My setup is - Upstream job... Downstream job... and: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3755.1582221240263%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-50-12-201.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3739.1582221060594%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-50-50-682.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3747.1582221060738%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-49-11-213.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3731.1582221000361%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Karl Wirth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi Tom Cramer - Quick update. I just upgraded my test instance to 1.10.10 and for me the trigger is still working so it's possible this is to do with the paths involved or could be Jenkins version related also. If you can get me the data mentioned above and the paths involved that would be great (for example is it a stream, are there spaces, numbers or non ASCII characters). If you'd feel more comfortable in sending the data to me directly please send it to supp...@perforce.com for my attention. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.3720.1582219200191%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Yes that's the one. I'll do some basic tests here to see if I can repro this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3470.1582193820517%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Has this ever worked for you? From this thread, it looks like we didnt put in a code fix and only provided a workaround where you avoided using P4_CHANGELIST. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3299.1582192500241%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Karl Wirth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi Tom Cramer - Thanks for reporting this. What type of job are you triggering? Freestyle or pipeline? Please send me screenshots showing the 'Build Triggers' section of the job and the complete URL (with hostname replaced with a dummy hostname) you use to trigger the job. I will then try and repro this here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.3281.1582190760145%40Atlassian.JIRA.
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Karl Wirth closed an issue as Fixed Credential corruption possibly due to another plugin being upgraded. In the past I have seen that saving the credential and then saving the job can solve the problem. In this case recreating the credential seems to have solved the problem. Jenkins / JENKINS-61005 Builds failing because Run defining the context within which to find P4 credential is null Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Karl Wirth commented on JENKINS-61005 Re: Builds failing because Run defining the context within which to find P4 credential is null Hi Annie Chen - Thanks and I'm happy I could help. If the problem comes back or if there is anything else we can do to help, please let us know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204475.1581024719000.6724.1581423600365%40Atlassian.JIRA.
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title Karl Wirth commented on JENKINS-61035 Re: Polling build filters case sensitive on -C1 server William Brode - Thanks. Have linked them both so dev can see. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204514.1581360737000.6722.1581423360361%40Atlassian.JIRA.
[JIRA] (JENKINS-48584) Add case insensitive option for "Exclued changes from Depot path"
Title: Message Title Karl Wirth edited a comment on JENKINS-48584 Re: Add case insensitive option for "Exclued changes from Depot path" Hi [~wbrode] - Thanks for spotting that. My Google-fu failled failed . keywords - C1, insensitive, P4D, poll, filter, exclusion,exclude. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187224.1513365845000.6720.1581423301254%40Atlassian.JIRA.
[JIRA] (JENKINS-48584) Add case insensitive option for "Exclued changes from Depot path"
Title: Message Title Karl Wirth commented on JENKINS-48584 Re: Add case insensitive option for "Exclued changes from Depot path" Hi William Brode - Thanks for spotting that. My Google-fu failled. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187224.1513365845000.6718.1581423241019%40Atlassian.JIRA.
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61035 Polling build filters case sensitive on -C1 server Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204514.1581360737000.5622.1581360780172%40Atlassian.JIRA.
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61035 Polling build filters case sensitive on -C1 server Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-02-10 18:52 Environment: p4-plugin 1.10.10 Jenkins 2.176.1 P4D 2019.2 Priority: Minor Reporter: Karl Wirth Polling build filters are case sensitive when connected to a case insensitive server. For example if the polling build filter is '//depot/sub' submitting '//depot/sub/f1' will be ignored but submitting '//depot/SUB/f1' will trigger a build. Note this behavior on a Linux client. If I create a directory called SUB and sync when connected to a C1 server this is what I see: $ cd SUB $ p4 sync ... //depot/SUB/f10#1 - added as /wsC1/SUB/f10 //depot/sub/f6#1 - added as /wsC1/SUB/f6 //depot/sub/f7#1 - added as /wsC1/SUB/f7 //depot/sub/f9#1 - added as /wsC1/SUB/f9 Note that in depot syntax files in SUB and sub are treated the same. Reproduction Steps: (1) Start a Perforce server with the -C1 flag: p4d -r /p1/1/root -L log -C1 -p 1666 (2) Create a 'jenkins' users in this P4D. (3) Create a workspace on a Linux box and submit the file '//depot/sub/f1'. (4) Create a
[JIRA] (JENKINS-61013) plagin
Title: Message Title Karl Wirth closed an issue as Fixed Jenkins / JENKINS-61013 plagin Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204483.158108912.3856.1581091260232%40Atlassian.JIRA.
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Karl Wirth commented on JENKINS-61005 Re: Builds failing because Run defining the context within which to find P4 credential is null Hi Annie Chen - Thanks for letting us know. Are you saying that you have 3 Perforce builds and only one is failing, or are you saying that all your Perforce builds are failing? Please try the following tests: Create a new Perforce job does that work? Try creating a new credential that uses the same userid and password. Switch a failing job to using the new credential does that work? Usually after an upgrade there is a cleanup old data option under Manage Jenkins. Did you run this already? Please also give me additional information. Is this a freestyle job? Please send me screenshots showing how the job is defined and any Jenkinsfiles it may be using. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-60358) Support Root=null value in Template workspace - Currently it is overridden, failing sync
Title: Message Title Karl Wirth commented on JENKINS-60358 Re: Support Root=null value in Template workspace - Currently it is overridden, failing sync Hi Shai Shapira, This is still in the backlog but you commenting on it will mark it as an active job for the developers the next time they review the backlog. Your previous comments suggests that the reason you are not using the workaround is it is more confusing for users? Is that correct or did I misread it? Regards, Karl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203377.1575437377000.10642.1580719140161%40Atlassian.JIRA.
[JIRA] (JENKINS-41088) Show "latest" run results via fixed URL (dashboard like feature)
Title: Message Title Karl Wirth commented on JENKINS-41088 Re: Show "latest" run results via fixed URL (dashboard like feature) Hi Robin Björklin - I couldnt figure out how to translate mine. For example a working link to execution 8 (last) of the job: http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/8/pipeline I've tried different combination of your URL with only 404 errors. For example: http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/job/master/lastBuild/display/redirect http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/job/master/lastBuild/display/redirect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60832) Polling on matrix build always gives "P4: Polling error; no previous change.
Title: Message Title Karl Wirth commented on JENKINS-60832 Re: Polling on matrix build always gives "P4: Polling error; no previous change. Confirm I can reproduce this problem even if I have forced a build before. Manual builds work fine. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204183.1579654315000.3987.1579715160270%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Just hit this problem while testing JENKINS-60832 so wanted to highlight it to dev. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197398.1549406943000.3984.1579714260158%40Atlassian.JIRA.
[JIRA] (JENKINS-60675) An automated ant build called from Jenkins fails
Title: Message Title Karl Wirth commented on JENKINS-60675 Re: An automated ant build called from Jenkins fails Hi Peeush Trikha - I just wanted to check if you had seen my previous comment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203918.1578391928000.6294.1578654300238%40Atlassian.JIRA.
[JIRA] (JENKINS-60675) An automated ant build called from Jenkins fails
Title: Message Title Karl Wirth commented on JENKINS-60675 Re: An automated ant build called from Jenkins fails Hi Peeush Trikha - From the console log I cannot see what is not working. Can you add extra debugging to the script to show where it is failing. Is it possible that you are expecting variables to be present that are not? For example maybe add 'p4 set' to the script to display what P4PORT, P4USER and P4CLIENT are in use. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203918.1578391928000.3602.1578395640238%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Karl Wirth Labels: P4_B P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175181.1475750631000.1652.1577978940432%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Karl Wirth Labels: P4_SUPPORT P4_B Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175181.1475750631000.1649.1577978940367%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175181.1475750631000.1654.1577978940456%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title
Karl Wirth commented on JENKINS-38781
Re: p4 unshelve not updating changes (pipeline)
Hi Morne Joubert - Happy New Year and thanks for all the detail. I was easily able to reproduce this so will pass it back to the devs. Reproduction Steps: (1) Create the depot structure: //depot/JENKINS-38781-UnsyncChangelist/JenkinsfileHome/Jenkinsfile //depot/JENKINS-38781-UnsyncChangelist/sync/s1 //depot/JENKINS-38781-UnsyncChangelist/unshelve/u1 (2) In the Jenkinsfile put the following code:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
script {
p4sync charset: 'none', credential: 'JenkinsMaster', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false, replace: true, tidy: false), source: depotSource('//depot/JENKINS-38781-UnsyncChangelist/sync/...')
def p4env = p4unshelve credential: 'JenkinsMaster', ignoreEmpty: false, resolve: 'at', shelf: '2254', tidy: false, workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-unshelve', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/JENKINS-38781-UnsyncChangelist/unshelve/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-unshelve/unshelve/... '))
}
}
}
}
}
Note that there is a sync step followed by an unshelve to a different directory. (3) Run the job using 'Build Now'. The unshelve step should have unshelved '2254' but it is not reported: We would like to see unshelved changelist reported.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Karl Wirth Attachment: image-2020-01-02-15-25-09-490.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175181.1475750631000.1642.1577978760399%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Karl Wirth commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Hi Eric Daigneault - I was going through my old cases and saw that this one is still open. Are you able to answer the questions above? Thanks in advance. Karl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203502.1576019104000.1626.1577970240106%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth closed an issue as Done John has provided a workaround. Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Labels: P4_B P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.1623.1577970060750%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell. problem 1: I cannot get this to work. Is it possible to to load two libraries. One for each path? problem 2: I also see this so have raised the following enhancement request JENKINS-60545. problem 3: Please get me you code. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.13773.1576774920230%40Atlassian.JIRA.
[JIRA] (JENKINS-60545) Replay with ModernSCM doesn't use relevant library version.
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-60545
Replay with ModernSCM doesn't use relevant library version.
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-12-19 16:59
Environment:
p4-plugin 1.10.7
Labels:
P4_VERIFY
Priority:
Minor
Reporter:
Karl Wirth
Replaying a dynamically loaded library will load the latest version of the library and not the library available at the time of the build. Reproduction Steps: (1) Submit following file to Perforce: //depot/lib_autoload/libs/src/com/f5/v4/Device.groovy
#!groovy
package com.f5.v4class Device implements Serializable {
static void main()
{
println("This is Device in the Library I EDITED THIS.")
}
static void test()
{
println("This is test in Device in the Library")
}
static String test2()
{
return "This is test2() in Device in the Library"
}
}
(2) Create a pipeline job with code similar to:
def f5Lib
timestamps{
try {
node ('master') {
f5Lib = loadF5Lib()
def
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13761.1576770540278%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: Karl Wirth Component/s: p4-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203532.1576121478000.13758.1576770420250%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203532.1576121478000.13756.1576770420222%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi Matthew Brunton - Here's the line of code: https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepExecution.java#L42 I have worked through this with the developers and we don't think this is a problem with our code in p4-plugin. There is a slight chance that maybe we need to be inheriting a new version of one of our dependencies but as it works when in a 'Jenkinsfile' or without the 'excludes' there's more chance it's problem in a library higher up such as the general SCM module. If this does turn out to be a bug on our side please let us know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13747.1576767900201%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Karl Wirth Attachment: PerforceTestingConsoleOutput_WithExcludes.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13677.1576756020390%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Karl Wirth Attachment: PerforceTestingConsoleOutput_WithOUT_Excludes.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13680.1576756020438%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi Matthew Brunton - The problem was that I needed the latest version of the declarative pipeline plugin. I'm easily able to reproduce the behavior and have attached the complete console outputs for with and without excludes. I'll check where the message 'No branches to run' comes from and discuss with the developers to see if that cab tell us if the is a p4-plugin or something else problem. PerforceTestingConsoleOutput_WithExcludes.txt PerforceTestingConsoleOutput_WithOUT_Excludes.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13683.1576756020472%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi Matthew Brunton - Thanks. I'll try again and let you know how it goes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.13640.1576753380499%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title
Karl Wirth edited a comment on JENKINS-60479
Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Hi [~abayer],Thanks for reporting this. Before we start, from a pure Perforce streams point of view I'd recommend against having a library stream in the same stream path as code.The code expects that streams are divergent forms of the same basic code. For example a stream may contain: {code:java}//Project1Stream/Rel1/...//Project1Stream/Rel2/...//Project1Stream/Main/...//Project1Stream/Dev/...{code} which could import{code:java}//LibraryStream/main/...{code}Alternatively if you have a deeper stream depth set you could have the two stream trees in the same depot:{code:java}//StreamDepot/Project1/Rel1/...//StreamDepot/Project1/Rel2/...//StreamDepot/Project1/Main/...//StreamDepot/Project1/Dev/...//StreamDepot/Library/Main/...//StreamDepot/Library/Dev/...{code}If you don't have this structure then there will always be outstanding changes that need to be branched between the library stream and it's parents.Now back to the problem. I tried setting this up and keep getting compilation errors: {code:java} org.jenkinsci.plugins.workflow.cps.CpsCompilationErrorsException: startup failed: /var/lib/jenkins/jobs/JENKINS-60479_Exclusions_MultiBranch/branches/main/builds/2/libs/test-pipeline/vars/lib.groovy: 8: Unknown stage section "matrix". Starting with version 0.5, steps in a stage must be in a ‘steps’ block. @ line 8, column 7. stage('Build') {code} I am on 2.176.1 so this may be a version problem. Just in case can you please send me the screenshots of the job definition to make sure I'm doing this correctly.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi Andrew Bayer, Thanks for reporting this. Before we start, from a pure Perforce streams point of view I'd recommend against having a library stream in the same stream path as code. The code expects that streams are divergent forms of the same basic code. For example a stream may contain: //Project1Stream/Rel1/... //Project1Stream/Rel2/... //Project1Stream/Main/... //Project1Stream/Dev/... which could import //LibraryStream/main/... Alternatively if you have a deeper stream depth set you could have the two stream trees in the same depot: //StreamDepot/Project1/Rel1/... //StreamDepot/Project1/Rel2/... //StreamDepot/Project1/Main/... //StreamDepot/Project1/Dev/... //StreamDepot/Library/Main/... //StreamDepot/Library/Dev/... If you don't have this structure then there will always be outstanding changes that need to be branched between the library stream and it's parents. Now back to the problem. I tried setting this up and keep getting compilation errors: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.8140.1576490640545%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) Hi Morne Joubert - Sorry I'm missing the point here. I've read the job you mention but can you describe for me exactly what you want to do and what is not working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175181.1475750631000.7178.1576252200171%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Karl Wirth commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Hi Eric Daigneault - Thanks. For not stopping the reconcile I have tried some testing here and I think this is more a problem on the server than with p4-plugin. Perforce commands run in a loop and when the client side connection drops they need to get to a safe point in the command before they check if the network connection is still there and die if needed. This is usually when the database locks are released or at the end of processing an argument. If I kill (CTRL+C) a reconcile that takes 30 seconds run using P4 at the command line, I still see the command in p4 monitor for about 25 seconds in total. If I kill the Jenkins job I see similar timings (21 seconds approx) however I think it's easier to be accurate about the time you killed a command at the command line and more difficult to be consistent via Jenkins. So from this testing I think the command line and p4-plugin behavior is comparable. For the file handle, do you know if the file handle was released when the reconcile completed? Also why did you need to workaround it? Was killing the jobs a frequent need? I have tested here and was not able to reproduce the problem on Windows 10 but it may be related to the types/sizes of files etc. Was .Sources\Floor_Base_Interior_01.ZTL a special file? For example a symlink/junction? For the p4j*.tmp files, is it possible they were from an earlier plugib version? They used to be created and sometimes not cleaned up when using symlinks. That should have been fixed in 1.10.6: https://github.com/jenkinsci/p4-plugin/blob/master/RELEASE.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
