Skip to content

Commit

Permalink
Investigate settings to publish build results fron Jenkins to GitHub
Browse files Browse the repository at this point in the history
Main goal is to analyze what steps need to be taken to have the Jenkins
build results like compiler warnings and Maven problems be published to
the GitHub actions.

The initial step is just about how to get the results to GitHub. In a
later stage, those can the be further configured to have the build fail
if it would introduce additional warnings.
  • Loading branch information
ptziegler committed Nov 18, 2024
1 parent 60f96b7 commit 92e1e6c
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions Jenkinsfile
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,7 @@ BRANCH_NAME=${env.BRANCH_NAME}
post {
always {
junit allowEmptyResults: true, testResults: '**/target/surefire-reports/*.xml'
discoverGitReferenceBuild referenceJob: 'build-classic/master'
recordIssues publishAllIssues: true, tools: [java(), mavenConsole(), javaDoc()]
}

Expand Down

0 comments on commit 92e1e6c

Please sign in to comment.