This is related to -JENKINS-15961-

I am using the Folders plugin in Jenkins to organize jobs and within a folder, I have a Pipeline job configured for 'Pipeline Script from SCM'. This job is pretty standard and there are no additional behaviors or options configured outside of the repo URL. I have checked the box for 'GitHub hook trigger for GITScm polling' under 'Build Triggers' so that when there is a push to the repo added in the pipeline job, the job gets built.

In the folder, I configure a Pipeline Library. Currently, this library isn't versioned and everything just pulls the 'master' branch to use. When I push changes to the library, this also triggers the pipeline job within the folder which I don't want. 

Observed Behavior:

• using the 'Modern SCM' retrieval method, If I check the box for 'Ignore on push notifications' for the Pipeline Library, pushing to the library repo triggers the pipeline job. 
• using the 'Legacy SCM' retrieval method, if I add the additional parameter for 'Don't trigger a build on commit notifications', pushing to the library repo triggers the pipeline job. 

Expected behavior:

• the pushes to the library should not trigger the pipeline job

Does this have something to do with the polling logic seeing that the Pipeline Library ref has been updated rather than the push notification triggering the build? The pipeline job seems to trigger as soon as I merge something into the Library even with the ignore option on.