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

make merge commit sha1 available to downstream jobs

    XMLWordPrintable

Details

    • Improvement
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • ghprb-plugin
    • None

    Description

      It would be useful if the merge commit sha1 - I.e. the b4af1bf184f8f2fa6e50a784dda17916d97dc629 from:

      Checking out Revision b4af1bf184f8f2fa6e50a784dda17916d97dc629 (refs/remotes/origin/pr/165/merge)
      

      could be made available to downstream jobs through a build-trigger parameter (i.e. as an environment variable similar to ghprbActualCommit, etc.

      The use-case for this is that your downstream job, say a test job, wants to be able to check-out the exact same code that was built into what is being tested.

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            bpatterson ben patterson
            brianjmurrell Brian J Murrell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: