Directly expose full payload from triggered GitHub webhooks

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When constructing a Jenkins pipeline that will run both on a branch push and pull requests events, there is the situation where a closed pull request (such as from being merged), will fire off a GitHub Pull Request payload, yet env.CHANGE_ID will be empty since that PR id is no longer active. This causes extraneous jobs to be created, and it would be great if there was a way to parse the actual payload that Jenkins receives from GitHub without alterations or bubbling up select attributes in predetermined env variables. I just want the payload, and I don't want to mess with the Generic Webhook Plugin.

      Any feedback or suggestions would be greatly appreciated. This has been an on-going issue at my place of employment for ~3 years now and handling this has always been a dreadful experience.

            Assignee:
            Unassigned
            Reporter:
            Joshua Riojas
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: