-
Improvement
-
Resolution: Fixed
-
Minor
-
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?
- duplicates
-
JENKINS-66890 Prefer successful/latest builds
-
- Resolved
-
[JENKINS-72015] Add option to filter not successful builds
Issue Type | Original: Story [ 10002 ] | New: Improvement [ 4 ] |
Summary | Original: Support for setting a different path | New: Add option to filter not successful builds |
Labels | New: hacktoberfest |
Labels | Original: hacktoberfest | New: hacktoberfest help-wanted |
Assignee | Original: Ulli Hafner [ drulli ] |
Link |
New:
This issue duplicates |
Assignee | New: Ulli Hafner [ drulli ] |
Labels | Original: hacktoberfest help-wanted |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Released As | New: https://github.com/jenkinsci/forensics-api-plugin/releases/tag/v2.4.0 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |