Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-46827

Pass-through Git Commit passes wrong revison

    Details

    • Similar Issues:

      Description

      I have a MultiJob which triggers jobs for different architectures. I've enabled Pass-through Git Commit that was built and if a build with the same parameters gets scheduled again it passes the revision of the previous build to the downstream projects, instead of the one the MultiJob has checked out.
      In that case also GIT_REVISION variable is evaluate to that wrong revision, but that doesn't harm me.

      > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
      Fetching changes from the remote Git repository
      > /usr/bin/git config remote.origin.url git://github.com/xbmc/xbmc.git # timeout=10
      Pruning obsolete local branches
      Fetching upstream changes from git://github.com/xbmc/xbmc.git
      > /usr/bin/git --version # timeout=10
      > /usr/bin/git fetch --tags --progress git://github.com/xbmc/xbmc.git +refs/pull/12474/:refs/remotes/origin/pr/12474/ --prune
      > /usr/bin/git rev-parse refs/remotes/origin/pr/12474/merge^

      {commit} # timeout=10
      > /usr/bin/git rev-parse refs/remotes/origin/origin/pr/12474/merge^{commit}

      # timeout=10
      Checking out Revision be44d74d23294facd47403349709374f5f152b44 (refs/remotes/origin/pr/12474/merge)
      > /usr/bin/git config core.sparsecheckout # timeout=10
      > /usr/bin/git checkout -f be44d74d23294facd47403349709374f5f152b44
      Commit message: "Merge 5f186ed6a2dbb9d2816721ec9ae1439a8ffc6bd3 into fee5e9eb94c6b129c514b3fac7b71db71de4009a"
      > /usr/bin/git rev-list aece29c14bdeb045d2fd4e12beff9da42b21e504 # timeout=10
      Run condition [Always] enabling prebuild for step [BuilderChain]
      Set build name.
      New build name is 'pr12474-dd18f54'
      >> Job status: [WIN-32] the 'build only if scm changes' feature is disabled.
      Starting build job WIN-32.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [WIN-64] the 'build only if scm changes' feature is disabled.
      Starting build job WIN-64.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [IOS] the 'build only if scm changes' feature is disabled.
      Starting build job IOS.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [IOS-ARM64] the 'build only if scm changes' feature is disabled.
      Starting build job IOS-ARM64.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [LINUX-64] the 'build only if scm changes' feature is disabled.
      Starting build job LINUX-64.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [LINUX-RBPI] the 'build only if scm changes' feature is disabled.
      Starting build job LINUX-RBPI.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [OSX-64] the 'build only if scm changes' feature is disabled.
      Starting build job OSX-64.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [Android-ARM] the 'build only if scm changes' feature is disabled.
      Starting build job Android-ARM.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: Skipping [Android-X86]. This subjob has been disabled.
      >> Job status: [Android-ARM64] the 'build only if scm changes' feature is disabled.
      Starting build job Android-ARM64.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca
      >> Job status: [LINUX-64-Wayland] the 'build only if scm changes' feature is disabled.
      Starting build job LINUX-64-Wayland.
      Pass-through Git Commit: dd18f544300c4e9b284940c92a0687c6081520ca

      be44d74 is the revision which should have been build, dd18f5 is the one that was build in a previous run, but shouldn't have build again

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment - - edited

          I have never used the multi-job plugin.  I had not heard of "pass-through git commit that was built" prior to this bug report.  

          I've removed myself as the assignee and assigned this bug to the multi-job plugin rather than the git plugin.  If the multi-job plugin maintainer finds that the root of the issue is in the git plugin, then this bug can be assigned back to the git plugin.

          Show
          markewaite Mark Waite added a comment - - edited I have never used the multi-job plugin .  I had not heard of "pass-through git commit that was built" prior to this bug report.   I've removed myself as the assignee and assigned this bug to the multi-job plugin rather than the git plugin.  If the multi-job plugin maintainer finds that the root of the issue is in the git plugin, then this bug can be assigned back to the git plugin.
          Hide
          yorammi Yoram Michaeli added a comment -

          Closing issue as part of tikal-multijob-plugin issues cleanup.
          If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

          Show
          yorammi Yoram Michaeli added a comment - Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

            People

            • Assignee:
              Unassigned
              Reporter:
              rechi Lukas Rechberger
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: