[JENKINS-67826] Directly expose full payload from triggered GitHub webhooks

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.

---
Originally reported by jriojas, imported from: Directly expose full payload from triggered GitHub webhooks

• status: Open
  
• priority: Minor
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 2
  
• imported: 2025-12-02
  

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.