dependabot[bot] on maven
Bump analysis-pom from 5.30.0 t… (compare)
dependabot[bot] on maven
Bump git-changelist-maven-exten… (compare)
uhafner on master
Bump analysis-pom from 5.28.0 t… Merge pull request #97 from jen… (compare)
uhafner on maven
I do not use Gradle on my own. But normally the format is not much different, so that the parser could be changed to parse both formats, here is an example: https://github.com/jenkinsci/analysis-model/blob/master/src/test/resources/edu/hm/hafner/analysis/parser/javac.log
Maybe it helps to see what is actually different in Gradle.
[Static Analysis] Created analysis result for 331 issues (found 0 new issues, fixed 0 issues)
[Static Analysis] Attaching ResultAction with ID 'analysis' to build 'Pull_Requests_SpotBugs_Pipeline_Build/PR-27926 #50'.
[Checks API] No suitable checks publisher found.
GitHub has been notified of this commit’s build result
Hi - thanks for the reference. I was able to get the issue sorted. Just one query - is it possible to define a branch as the baseline branch for new issues? The build which we will be running is for a multibranch pipeline against pull requests. We want to verify that in each pull request, no new warnings are introduced as a result of those changes, otherwise the build fails.
I can see there are quality gates, which I've added with the type NEW
, however this compares the basline number of warnings against the previously ran build on the feature branch. I'd like to compare the baseline against the target branch's recent build. Is this possible?
java()
is not affected, so it seems related to the files, somehow.
java()
is not affected, so it seems related to the files, somehow.
java.lang.IllegalStateException: ID analysis is already used by another action: io.jenkins.plugins.analysis.core.model.ResultAction for Static Analysis
script {
def mavenConsoleIssues = scanForIssues tool: mavenConsole("maven-${PLATFORM}")
def javaIssues = scanForIssues tool: java("java-${PLATFORM}")
def javaDocIssues = scanForIssues tool: javaDoc("javaDoc-${PLATFORM}")
def analysisId = "analysis-${PLATFORM}"
echo "analysisId: ${analysisId}"
publishIssues id: analysisId, issues: [mavenConsoleIssues, javaIssues, javaDocIssues]
Hi everyone - I'm trying to run multiple instances of the sarif
tool within a Jenkinsfile. For example:
recordIssues tool: sarif(pattern: 'results-tool1.sarif')
recordIssues tool: sarif(pattern: 'results-tool2.sarif')
This will cause incorrect UX in Jenkins, with 2 SARIF Warnings Tabs pointing to the same link. Is it possible to separate the data properly?