Only default value of sha1 getting chosen

[shehzan10]

We are experiencing the problem where the default value of sha1 in parameterized builds (in our case "master") and not the github commit from the PR. The correct PR/commit status on Github is being set, but the build is always with the commit on default value of sha1.

This however, does NOT happen if sha1 is not parameterized.

Here are 2 sample build logs for the same pr: With sha1 parameterized and Without sha1 parameterized. As you can see, the github setting status is working correctly. However, the checkout is revising to master on the build with sha1 parameterized.

This was also suggested by a user (zachmccormick) in #415.

Using GHPRB v1.32.2 with Jenkins LTS 1.651.2.

[Puneeth-n]

@shehzan10 This seems to be an issue because of the recent security update on jenkins.