GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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!

            Assignee:
            Kirill Merkushev
            Reporter:
            Logan Glickfield
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: