We need to make sure that commit SHA that triggered the build via webhook is the same SHA that the repo is being checkout out.
Use case:
Dev-1 merges changes to repo 'a'. Within seconds, Dev-2 merges changes to repo 'a'.
Expectation:
Each commit triggers a separate build based on the webhook SHA that triggered the build.
Current result:
SHA of Jenkinsfile might be not the same as checkout code, since the merges might happen within seconds of each other.
[JENKINS-59210] Build exactly the commit from the webhook
Description |
Original:
We need to make sure that commit SHA that triggered the build via webhook is the same SHA that the repo is being checkout out. Use case: Dev-1 merges changes to repo 'a'. Within seconds, Dev-2 merges changes to repo 'a'. Expectation: Each commit triggers a separate build based on the webhook SHA that triggered the build. Current result: SHA of Jenkinsfile might be not the same as checkout code, since the merges might happen within seconds of each other. |
New:
We need to make sure that commit SHA that triggered the build via webhook is the same SHA that the repo is being checkout out. h4. Use case: Dev-1 merges changes to repo 'a'. Within seconds, Dev-2 merges changes to repo 'a'. h4. Expectation: Each commit triggers a separate build based on the webhook SHA that triggered the build. h4. Current result: SHA of Jenkinsfile might be not the same as checkout code, since the merges might happen within seconds of each other. |
Assignee | Original: Mark Waite [ markewaite ] |
Summary | Original: Extract commit SHA of Jenkinsfile | New: Build exactly the commit from the webhook |
Attachment | New: Screen Shot 2019-09-04 at 5.24.18 PM.png [ 48620 ] |