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

No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • P4 Plugin version 1.8.4

      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')) 
      }
      }
      

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

              Created:
              Updated: