We're attempting to run some large pipeline jobs. Each job goes and runs a series of parallel jobs on multiple platforms for multiple targets.

When adding the options to include in changelog/polling that are now available:

            checkout([
                changelog: true, 
                poll: true, 
                scm: [
                    $class: 'PerforceScm', 
                    credential: credential, 
   ...

The job will try to poll for changes. It correctly polls the actual Jenkinsfile, but when it goes to poll for each separate checkout in the pipeline script, it loses track of the previous change it built at and continually triggers a new build.

The name of our generated clients is:
'jenkins-${NODE_NAME}${JOB_NAME}${BUILD_NUMBER}-' + platform

The p4 plugins normally adds a "Description:" field into the client tracking the last change. During my testing I can't get the plugin to set the Description into the correct client, and if I manually add the field to the client, it does not get read and processed.

Until this is corrected I can't use polling of each individual checkout.