On Tue, Jun 4, 2019 at 5:16 PM Julien HENRY <[email protected]> wrote: > Is there any simple way (except some fragile local Git operation) to access > the original Git sha1 that triggered the PR build? In my example I need to > get ab86fe3afa0b9473ea9da76c87872bf89b9b5f3b
There is not currently any environmental variable for that purpose that I know of. You can simply try publishing a commit status for the hash you are given, and if that gives a 422 response, try its first parent instead, as I suggested in the thread leading to https://jira.sonarsource.com/browse/SONAR-10794 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1Dt3Bn3MWKM9uBaeDYnXxjwEUVuZC5Wai2Fh5i3xHv%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
