Hi Ann, Thank you for that information. Sadly this isn't a viable option due to two reasons
1. Having to embed the Github user token in the curl command, which means adding that to the Jenkinsfile script 2. The webhook still takes the value of the build state for the last pipeline. So although I can define separate values and I see three check marks in the PR in github, if the second pipeline marks the build as a failure then the pr-merge status is also set to failure. Kind regards, Ian On Saturday, September 9, 2017 at 6:18:36 AM UTC+1, Ann B wrote: > > Hi Ian- > > I'm sorry that I cannot answer your question directly, as we do not use a > web hook. > > Have you thought of posting to the github statuses api - > https://developer.github.com/v3/repos/statuses/#create-a-status with a > separate link for each of your pipelines? We kick off all of our pipeline > jobs in parallel (static, functional, unit, etc). Each job adds a Statuses > link to the PR with an initial value of 'Pending' with a link to the > running job in jenkins. As each parallel job finishes, it updates the PR > Status with 'Failed' or 'Passes'. > > Ann > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a662c5ae-5c92-40ac-9169-9446477d9f60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
