You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux - 6.1.49-70.116.amzn2023.x86_64
Reproduction steps
We have a Jenkins job that's triggered via https://plugins.jenkins.io/ghprb/, where we configure the branch to run against to be ${ghprbActualCommit}, which should be the HEAD commit of the PR. As far as we can tell from the job log, the job is triggered against the correct HEAD commit, but the github check is published to the HEAD-1 commit, here's the system log we see, after enabling fine log for io.jenkins.plugins.checks and org.jenkinsci.plugins.ghprb:
Jan 31, 2025 6:38:14 AM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR
Pull request #36,182 was updated/initialized on <github_repo> at 1/31/25, 6:38 AM by <pr_author> (PR update)
Jan 31, 2025 6:38:14 AM FINE org.jenkinsci.plugins.ghprb.GhprbPullRequest
New commit. Sha: Head[dd54c2f08a1906da214b278c3cfd8a71b132f8d8 => c838597858a6b5c68d089ce07f9ef5eebac57dc8] Base[fbe32c9d80be87bbf6bdb645e805886b25dec022 => fbe32c9d80be87bbf6bdb645e805886b25dec022]
...
Jan 31, 2025 6:38:36 AM FINE io.jenkins.plugins.checks.github.GitHubChecksPublisher
Published check for repo: <github_repo>, sha: dd54c2f08a1906da214b278c3cfd8a71b132f8d8, job name: <job_name>, name: ci/jenkins-test, status: in_progress
...
Jan 31, 2025 6:39:12 AM FINE io.jenkins.plugins.checks.github.GitHubChecksPublisher
Published check for repo: <github_repo>, sha: dd54c2f08a1906da214b278c3cfd8a71b132f8d8, job name: <job_name>, name: ci/jenkins-test, status: completed
Here's the job log we see for the corresponding job:
06:38:24 GitHub pull request <pr_number> of commit c838597858a6b5c68d089ce07f9ef5eebac57dc8, no merge conflicts.
06:38:24 Checking out git https://github.com/<org>/<github_repo>.git into /var/jenkins_home/jobs/...
06:38:24 The recommended git tool is: git
06:38:24 using credential <github_app_credential>
06:38:24 Wiping out workspace first.
06:38:24 Cloning the remote Git repository
06:38:24 Using shallow clone with depth 1
06:38:24 Avoid fetching tags
06:38:24 Honoring refspec on initial clone
06:38:24 Cloning repository https://github.com/<org>/<github_repo>.git
06:38:24 > git init /var/jenkins_home/jobs/...
06:38:24 Fetching upstream changes from https://github.com/<org>/<github_repo>.git
06:38:24 > git --version # timeout=10
06:38:24 > git --version # 'git version 2.39.5'
06:38:24 using GIT_ASKPASS to set credentials Github app to set check status using https://plugins.jenkins.io/github-checks/
06:38:25 > git fetch --no-tags --force --progress --depth=1 -- https://github.com/<org>/<github_repo>.git +refs/pull/36182/*:refs/remotes/origin/pr/36182/* +refs/heads/master:refs/remotes/origin/master
06:38:32 > git config remote.origin.url https://github.com/<org>/<github_repo>.git
06:38:32 > git config --add remote.origin.fetch +refs/pull/36182/*:refs/remotes/origin/pr/36182/* # timeout=10
06:38:32 > git config --add remote.origin.fetch +refs/heads/master:refs/remotes/origin/master # timeout=10
06:38:32 Avoid second fetch
06:38:32 > git rev-parse c838597858a6b5c68d089ce07f9ef5eebac57dc8^{commit} # timeout=10
06:38:32 Checking out Revision c838597858a6b5c68d089ce07f9ef5eebac57dc8 (detached)
06:38:32 > git config core.sparsecheckout # timeout=10
06:38:32 > git checkout -f c838597858a6b5c68d089ce07f9ef5eebac57dc8 # timeout=10
06:38:33 Commit message: "Run no checks"
06:38:33 > git rev-list --no-walk dd54c2f08a1906da214b278c3cfd8a71b132f8d8 # timeout=10
06:38:33 First time build. Skipping changelog.
06:38:36 [GitHub Checks] GitHub check (name: ci/jenkins-test, status: in_progress) has been published.
Expected Results
Github check should be publishing to the c838597858a6b5c68d089ce07f9ef5eebac57dc8 commit
Actual Results
Github check is actually publishing to the dd54c2f08a1906da214b278c3cfd8a71b132f8d8 commit, which isn't the newest HEAD commit on the PR.
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux - 6.1.49-70.116.amzn2023.x86_64
Reproduction steps
We have a Jenkins job that's triggered via https://plugins.jenkins.io/ghprb/, where we configure the branch to run against to be
${ghprbActualCommit}
, which should be the HEAD commit of the PR. As far as we can tell from the job log, the job is triggered against the correct HEAD commit, but the github check is published to the HEAD-1 commit, here's the system log we see, after enabling fine log forio.jenkins.plugins.checks
andorg.jenkinsci.plugins.ghprb
:Here's the job log we see for the corresponding job:
Expected Results
Github check should be publishing to the
c838597858a6b5c68d089ce07f9ef5eebac57dc8
commitActual Results
Github check is actually publishing to the
dd54c2f08a1906da214b278c3cfd8a71b132f8d8
commit, which isn't the newest HEAD commit on the PR.Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: