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

Wrong repository inference when used inside shared pipeline library

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins Version: 2.320
      Plugin Version: 1.2.0

      I am writing a shared pipeline library which uses the pipeline-gitstatuswrapper plugin. The plugin is configured so that it automatically infers its account, repo and sha step parameters.

      When using the shared library, sha is correctly inferred to the commit that is being built but repo and account are inferred to the repository of the pipeline library and not of the project being built.

      While this is also not the expected behavior, it also results in the pipline failing because the commit sha is valid on the inferred repository.

            hello_woof Zachary Sherwin
            ftsell Finn-Thorben Sell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: