[JENKINS-45319] Github event, CHANGE_ID not set

[timja]

 

We would like to process a GitHub pull Request on a Multi-Branch pipeline. The CHANGE_ID param is however not set (null), while it should be according to

https://jenkins.io/doc/book/pipeline/multibranch/

I posted the same bug here, with details on our plugins, and the event log. 

https://stackoverflow.com/questions/44757073/jenkins-multibranch-pipeline-job-change-id-not-set

Any suggestions on how to tackle this problem? I would think, we should like to see exactly what github is posting, is this somehow recorded in Jenkins? 

Thank You.

 

 

ace-editor	1.1	true
analysis-core	1.87	true
ansible	0.6.2	true
ansicolor	0.5.0	true
ant	1.5	true
antisamy-markup-formatter	1.5	true
authentication-tokens	1.3	true
blueocean	1.1.2	true
blueocean-autofavorite	1.0.0	true
blueocean-commons	1.1.2	true
blueocean-config	1.1.2	true
blueocean-dashboard	1.1.2	true
blueocean-display-url	2.0	true
blueocean-events	1.1.2	true
blueocean-git-pipeline	1.1.2	true
blueocean-github-pipeline	1.1.2	true
blueocean-i18n	1.1.2	true
blueocean-jwt	1.1.2	true
blueocean-personalization	1.1.2	true
blueocean-pipeline-api-impl	1.1.2	true
blueocean-pipeline-editor	0.2.0	true
blueocean-pipeline-scm-api	1.1.2	true
blueocean-rest	1.1.2	true
blueocean-rest-impl	1.1.2	true
blueocean-web	1.1.2	true
bouncycastle-api	2.16.1	true
branch-api	2.0.10	true
build-blocker-plugin	1.7.3	true
build-monitor-plugin	1.12+build.201704111018	true
build-name-setter	1.6.5	true
build-pipeline-plugin	1.5.7	true
build-timeout	1.18	true
cloudbees-folder	6.0.4	true
conditional-buildstep	1.3.6	true
config-file-provider	2.16.0	true
credentials	2.1.14	true
credentials-binding	1.12	true
dashboard-view	2.9.11	true
delivery-pipeline-plugin	1.0.2	true
display-url-api	2.0	true
docker-commons	1.7	true
docker-workflow	1.12	true
durable-task	1.14	true
email-ext	2.57.2	true
environment-script	1.2.5	true
external-monitor-job	1.7	true
favorite	2.3.0	true
git	3.3.1	true
git-client	2.4.6	true
git-server	1.7	true
github	1.27.0	true
github-api	1.85.1	true
github-branch-source	2.0.6	true
github-organization-folder	1.6	true
global-build-stats	1.4	true
gradle	1.27-SNAPSHOT (private-06/23/2017 09:49-wolf)	true
greenballs	1.15	true
handlebars	1.1.1	true
htmlpublisher	1.13	true
icon-shim	2.0.3	true
ivy	1.27.1	true
jackson2-api	2.7.3	true
javadoc	1.4	true
jobConfigHistory	2.16	true
jquery	1.11.2-0	true
jquery-detached	1.2.1	true
junit	1.20	true
ldap	1.15	true
mailer	1.20	true
mapdb-api	1.0.9.0	true
mask-passwords	2.10.1	true
matrix-auth	1.6	true
matrix-project	1.11	true
maven-plugin	2.16	true
metrics	3.1.2.10	true
momentjs	1.1.1	true
multi-branch-project-plugin	0.7	true
multiple-scms	0.6	true
pam-auth	1.3	true
parameterized-trigger	2.34	true
pipeline-build-step	2.5	true
pipeline-github-lib	1.0	true
pipeline-graph-analysis	1.4	true
pipeline-input-step	2.7	true
pipeline-milestone-step	1.3.1	true
pipeline-model-api	1.1.7	true
pipeline-model-declarative-agent	1.1.1	true
pipeline-model-definition	1.1.7	true
pipeline-model-extensions	1.1.7	true
pipeline-rest-api	2.8	true
pipeline-stage-step	2.2	true
pipeline-stage-tags-metadata	1.1.7	true
pipeline-stage-view	2.8	true
plain-credentials	1.4	true
promoted-builds	2.29	true
pubsub-light	1.8	true
resource-disposer	0.6	true
role-strategy	2.5.0	true
run-condition	1.0	true
scm-api	2.1.1	true
script-security	1.29	true
sonar	2.6.1	true
sse-gateway	1.15	true
ssh-credentials	1.13	true
ssh-slaves	1.20	true
structs	1.8	true
subversion	2.8	true
thinBackup	1.9	true
timestamper	1.8.8	true
token-macro	2.1	true
variant	1.1	true
windows-slaves	1.3.1	true
workflow-aggregator	2.5	true
workflow-api	2.17	true
workflow-basic-steps	2.5	true
workflow-cps	2.36	true
workflow-cps-global-lib	2.8	true
workflow-durable-task-step	2.12	true
workflow-job	2.11.1	true
workflow-multibranch	2.16	true
workflow-scm-step	2.5	true
workflow-step-api	2.11	true
workflow-support	2.14	true
ws-cleanup	0.33	true

---

Originally reported by dzonekl, imported from: Github event, CHANGE_ID not set

• assignee: vaimr
• status: Open
• priority: Minor
• resolution: Unresolved
• imported: 2022/01/10

[timja]

vaimr:

Answer in https://stackoverflow.com/a/46154606/6997786:

This variable sutup in the branch-api-plugin (setup source) and we have it working for pull requests or change requests.

For branches of the form -, it is not filled.

I can advise you to use:

{{BUILD_NUMBER The current build number, such as "153" }}

BUILD_ID The current build ID, identical to BUILD_NUMBER for builds created in 1.597+, but a YYYY-MM-DD_hh-mm-ss timestamp for older builds