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

GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • github-plugin
    • None

      We're using the Shared Libraries Plugin with our Jenkins Pipeline along with a checkout step.

      Combined this means there are two separate checkouts when the pipeline runs.

      When I then try to call a step with GitHubCommitStatusSetter, it then tries to set the status for both commits against both repositories (i.e. 4 different combinations of commit hash/repos). This results in {{FileNotFoundException}}s that fail the build. But this will obviously always fail because each commit is only valid for one of the repositories.

      I see I can hardcode repository and sha values, but unfortunately with the Github Organizational plugin, I don't have access to the sha directly.

      Is there anything that can be done to make this work? Thanks!

            lanwen Kirill Merkushev
            lsglick Logan Glickfield
            Votes:
            3 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: