[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax 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.188416.1518459572000.11163.1575381001059%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax 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.188416.1518459572000.11161.1575380940297%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax Change By: Karl Wirth Summary: No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax 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.188416.1518459572000.11159.1575380940261%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters Change By: Karl Wirth Assignee: Karl Wirth 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title W Basu updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters Change By: W Basu Labels: P4_VERIFY P4_SUPPORT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Karl Wirth commented on JENKINS-49514 Re: No builds triggered using p4 plugin polling with view filters Recommending that 'viewFilter' should use Perforce syntax. Moving to P4_VERIFY. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters Change By: Paul Allen Labels: P4_SUPPORT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Samuel Kahn commented on JENKINS-49514 Re: No builds triggered using p4 plugin polling with view filters In this case after some experimentation on my side the problem seems to come from the "/..." at the end of the paths, which should work for a workspace view, but somehow do not work here, I still believe that is a bug considering paths using ... wildcards are generally working in all perforce commands and tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Karl Wirth commented on JENKINS-49514 Re: No builds triggered using p4 plugin polling with view filters supp...@perforce.com are working with Samuel. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn updated an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Change By:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/ source game /... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/ game/ content which is what the view filter reflects.Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded?Here is the checkout stage of my pipeline (with edited project names):{code:java}stage('Sync code') {steps{checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/ source game /...//project/main/ game/ content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn updated an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Change By:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/source/... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/content which is what the view filter reflects.Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded?Here is the checkout stage of my pipeline (with edited project names): {code:java} stage('Sync code') \ { steps \ { checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/source/... - //project/main/content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins - $ \ {NODE_NAME} - $ \ {JOB_NAME} - $ \ {EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) } } {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn created an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-12 18:19
Environment:
P4 Plugin version 1.8.4
Priority:
Major
Reporter:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/source/... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/content which is what the view filter reflects. Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded? Here is the checkout stage of my pipeline (with edited project names): stage('Sync code') { steps{ checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/source/... //project/main/content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) } }
