git - Why does jenkins build from multiple commits when it shouldn't? -

i have parameterized job in jenkins. receives git hash , runs checkout commit hash (commit hash in branches parameter). problem when jenkins offline time , in meantime new commits pushed repo. when jenkins online again, receives commit hash , when supposed build 1 commit, takes commits were'nt built in meantime despite 1 hash passed checkout.

why happen , how can avoided?

edit: here's job log:

[pipeline] node running on master in /var/lib/jenkins/workspace/tester [pipeline] { [pipeline] stage (checkout) using ‘stage’ step without block argument deprecated entering stage checkout proceeding [pipeline] checkout > git rev-parse --is-inside-work-tree # timeout=10 fetching changes remote git repository > git config remote.origin.url http://testrepo.git # timeout=10 fetching upstream changes http://testrepo.git > git --version # timeout=10 > git fetch --tags --progress http://testrepo.git +refs/heads/*:refs/remotes/origin/* > git rev-parse <mycommithash>^{commit} # timeout=10 checking out revision <mycommithash> (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f <mycommithash> > git rev-list <someotherhash> # timeout=10 [pipeline] } [pipeline] // node [pipeline] end of pipeline finished: success