Adding the properties step to your pipeline script causes changes in job configuration xml for every build, even if there are no changes in the configuration. This results in misleading the user that every build have config changes and storing configuration history for every build. This behaviour is making the job config history useless. 

What is happening is that the order of <actions> sub elements, in job configuration xml, is constantly changing, however the overall configuration for every build is the same. The job configuration difference page is showing 'no lines changed'. I have attached config.xml for two consecutive builds.

I have tested this behaviour for Build blocker plugin property, but it is the same for very property.

Steps to reproduce:

1. Add anywhere in your pipeline script properties step:

properties([
    [
        $class: 'BuildBlockerProperty', 
        blockLevel: 'GLOBAL', 
        blockingJobs: 'examplejob', 
        scanQueueFor: 'DISABLED', 
        useBuildBlocker: true
    ]
])

or any other property:

properties([
    disableConcurrentBuilds()
])