Required Data for WebHook
This article describes how to collect the minimum required information for troubleshooting SCM Webhook issues.
If the required data is bigger than 50 MB you will not be able to use ZenDesk to upload all the information. On this case we would like to encourage you to use our upload service in order to attach all the required information.
Environment
Required Data check list
Jenkins side
-
Dedicated Loggers
-
Support Bundle
-
Job Description
-
If applicable, the branch indexing logs
-
If applicable, plugin configuration (GitHub or Bitbucket)
Dedicated Loggers
Create a dedicated logger depending on the Source Code Management selected for the job.
Support bundle
Support Bundle generated after adding logging and reproducing the issue. Please, follow the KB below in case you don’t know how to generate a support bundle.
-
What is a support bundle and how to create one, please make sure to include
Jenkins Global Configuration File (Encrypted secrets are redacted). Otherwise, please attach GitHub/Bitbucket plugin configuration (endpoints, …) as follows:
GitHub plugin configuration
The file $JENKINS_HOME/github-plugin-configuration.xml is needed. Alternatively, you could enable Jenkins Global Configuration File (Encrypted secrets are redacted) and Other Jenkins Configuration Files (Encrypted secrets are redacted) for the support bundle generation.
BitBucket plugin configuration
The file $JENKINS_HOME/com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration.xml is needed. Alternatively, you could enable Jenkins Global Configuration File (Encrypted secrets are redacted) and Other Jenkins Configuration Files (Encrypted secrets are redacted) for the support bundle generation.