• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • git-forensics-plugin
    • None

      Currently, the git-forensics can't be used in a pipeline where some branches are split into different folders, e.g., main is in "/project/repo/prod" and everything else is in "/project/repo/dev". The pipeline in "dev" has to access the "prod" folder in order to get the coverage result (via code-coverage-api plugin) of the latest successful build in main. Currently, this is not possible and the plugin reports that no reference build can be found.

      I could take the `referenceJob` option as a workaround and set it to "/project/repo/prod" but then the code-coverage-api plugin gets the latest build and not the latest successful one.

       

      Any chance of adding such an option to set the right path?

          [JENKINS-72015] Add option to filter not successful builds

          Ulli Hafner added a comment -

          I'm not sure what you mean with different path? The referenceJob parameter exactly does provide such an option already.

          So moving the option to select only successful builds from the warnings plugin to the forensics plugin makes more sense.

          Ulli Hafner added a comment - I'm not sure what you mean with different path? The referenceJob parameter exactly does provide such an option already. So moving the option to select only successful builds from the warnings plugin to the forensics plugin makes more sense.

          Ok, I was not quite sure if that was the case, because it already took the latest successful build, when both branches were in the same directory.

          Yes, the option to select only successful builds would fit

          Klaus Strießnig added a comment - Ok, I was not quite sure if that was the case, because it already took the latest successful build, when both branches were in the same directory. Yes, the option to select only successful builds would fit

            drulli Ulli Hafner
            kirdock Klaus Strießnig
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: