We are trying to avoid build steps as much as possible, for example skipping some of then when a build was triggered by a upstream project but did not have any changes on its own or a commit message contained a specified string (aka [skip ci]).

Therefor we heavily rely on the currentBuild.changeSets.

Unfortunatly we recently discovered that builds are triggered when a force push is used (which is good) to a repository, but the changes are empty (thats not expected). This can also be seen in the corresponding UI.

There might be other constellations where it does not work but this is one we could reproduce.