Jenkins when used with Github Pull Request Builder uses a special branch. It's ref is created by Github.
It looks like this pull/ID/head which is the head of your Pull Request or pull/ID/merge which is your PR merged into your intended branch. The result is a sha that differs than what you find in your pull request.
Because it still has a full working git repo in the checkout though, and ruby-test-reporter gives that precedence over info in environment variables coverage is reported with the wrong sha.
Jenkins when used with Github Pull Request Builder uses a special branch. It's ref is created by Github.
It looks like this
pull/ID/head
which is the head of your Pull Request orpull/ID/merge
which is your PR merged into your intended branch. The result is a sha that differs than what you find in your pull request.Because it still has a full working git repo in the checkout though, and ruby-test-reporter gives that precedence over info in environment variables coverage is reported with the wrong sha.