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

No builds triggered using p4 plugin polling with view filters

    Details

    • Similar Issues:

      Description

      P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/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):

      stage('Sync code') {
      steps{
      checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/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')) 
      }
      }
      

        Attachments

          Activity

          Hide
          p4karl Karl Wirth added a comment -

          Recommending that 'viewFilter' should use Perforce syntax. Moving to P4_VERIFY.

          Show
          p4karl Karl Wirth added a comment - Recommending that 'viewFilter' should use Perforce syntax. Moving to P4_VERIFY.
          Hide
          kahncode Samuel Kahn added a comment -

          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.

          Show
          kahncode Samuel Kahn added a comment - 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.
          Hide
          p4karl Karl Wirth added a comment -

          support@perforce.com are working with Samuel.

          Show
          p4karl Karl Wirth added a comment - support@perforce.com are working with Samuel.

            People

            • Assignee:
              p4karl Karl Wirth
              Reporter:
              kahncode Samuel Kahn
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: