Controlling a MultiBranch Pipeline Change log

[Brian Weiner]

I'm setting up a chain of projects, where when Project A finishes building, I invoke Project B using the "build" command.  However, the build command always sync's to whatever HEAD is currently set to on the remote.  My Jenkinsfile, later syncs to the hash I want.  However, at this point the change log is already polluted.

I.e. in Project B I want to build at hash X, however, at spin up Project B clones to hash Y, where Y is newer than X.  All the changes between X and Y are now part of the change log.

Any way to get around this?