[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title W Basu Perforce closed an issue as Won't Do Punting as it no longer matches our direction and features Jenkins / JENKINS-56162 p4 plugin doesn't add '/...' to older p4sync calls. Change By: W Basu Perforce Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197612.1550267378000.20951.1559654400508%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title W Basu Perforce commented on JENKINS-56162 Re: p4 plugin doesn't add '/...' to older p4sync calls. Matthew Hall - we appreciate the pain, however, adding the support back as feature will cause more disruption than help. However, as Karl Wirth said, he can help you for this one-off update where possible. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197612.1550267378000.20948.1559654340132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56162 p4 plugin doesn't add '/...' to older p4sync calls. Change By: Karl Wirth Labels: P4_B P4_A Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth commented on JENKINS-56162 Re: p4 plugin doesn't add '/...' to older p4sync calls. Hi Matthew Hall. Happy to help and I appreciate how painful that's going to be. FYI Wrishi Basu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Matthew Hall commented on JENKINS-56162 Re: p4 plugin doesn't add '/...' to older p4sync calls. Thanks for the info Karl. This is a rough change to suddenly run into, because we now have to go and fix several hundred Jenkinsfiles across multiple teams and groups. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56162 p4 plugin doesn't add '/...' to older p4sync calls. Change By: Karl Wirth Labels: P4_C Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth commented on JENKINS-56162 Re: p4 plugin doesn't add '/...' to older p4sync calls. Reproduction Steps: (1) Install p4-plugin 1.8.12 (2) Create pipeline job (editor is fine) and a 'p4sync' step that has a classic depot view that ends in a folder. For example '//depot/Project1/main'. (3) Run the job. '/...' is appended to client view and files under path are synced. (4) Upgrade to 1.9.6 (5) Force run the same job. '/...' is not appended to client view. No files are synced because 'main' is a folder not a file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56162 p4 plugin doesn't add '/...' to older p4sync calls. Change By: Karl Wirth Labels: P4_C P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Karl Wirth commented on JENKINS-56162 Re: p4 plugin doesn't add '/...' to older p4sync calls. Hi Matthew Hall, Thanks for highlighting this. It's an interesting one because the developers seem to have corrected the behavior to be correct Perforce behavior and documented it in the bubble help: List of one or more depot paths (separated by new lines) For example //depot/A/... //depot/B/... //depot/C/file.txt So in your example '//depot/svrtools/mainline/sme-tools/jenkins_test' is specifying the file not the folder 'jenkins_test'. However that breaks backward compatible systems that relied on the old behavior. I know we have been asked to support the usage case of only syncing a single file so we cant just revert to the old behavior without additional checking. Therefore I'm going to flag this to the product managers. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-56162
p4 plugin doesn't add '/...' to older p4sync calls.
Change By:
Matthew Hall
Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call:{code:java} p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test', format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true ] ){code}We get in the resultant client:{noformat}View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test{noformat}Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767If we revert plugin to older, and then delete generated client, we see the difference in c.txt output. We also see our view has changed : {noformat}View: //d-alviso/svrtools/mainline/sme-tools/jenkins_test/... //build-repo01-jenkins-test/...{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-56162 p4 plugin doesn't add '/...' to older p4sync calls. Change By: Matthew Hall Attachment: c.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-56162
p4 plugin doesn't add '/...' to older p4sync calls.
Change By:
Matthew Hall
Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call:{code:java} p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test', format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true ] ){code}We get in the resultant client:{noformat}View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test{noformat}Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767 If we revert plugin to older, and then delete generated client, we see the difference in c.txt output.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-56162
p4 plugin doesn't add '/...' to older p4sync calls.
Change By:
Matthew Hall
Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call: {code:java} p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test', format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true ] ) {code} We get in the resultant client: {noformat} View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test {noformat} Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails fro
[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.
Title: Message Title
Matthew Hall created an issue
Jenkins / JENKINS-56162
p4 plugin doesn't add '/...' to older p4sync calls.
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
a.txt
Components:
p4-plugin
Created:
2019-02-15 21:49
Priority:
Major
Reporter:
Matthew Hall
Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call: p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test', format: user + '${NODE_NAME}${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true ] ) We get in the resultant client: View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in : https://swarm.workshop.perforce.com/changes/24767
