Add reporting for weekly Jenkins builds - #547
Draft
DerDaehne wants to merge 1 commit into
Draft
Conversation
- Both stages "Unit Test" and "Sonar-Scanner" will perform unit tests, so we can merge these into one step. - builds triggered by timer event would have empty RecipientProviders, resulting in a situation where weekly build would not report the build status to anybody. From now on, the whole team will get informed via email
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Jenkins pipeline to consolidate Maven test + Sonar execution into a single stage and ensures timer-triggered (weekly) builds send email notifications to the whole team.
Changes:
- Merge “Unit Test” and “Sonar-Scanner” into a single “Test & SonarScanner” stage running
mvn ... verify sonar:sonar. - Respect the
noCacheparameter when building the Docker image. - Add dedicated email reporting for timer-triggered weekly builds and refactor timer detection into
isTriggeredByTimer().
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+235
to
+243
| if (isTriggeredByTimer()) { | ||
| currentBuild.displayName = "#${env.BUILD_NUMBER} weekly" | ||
| emailext( | ||
| subject: "Weekly build ${currentBuild.currentResult}: ${env.JOB_NAME} #${env.BUILD_NUMBER}", | ||
| body: '${SCRIPT, template="groovy-html.template"}', | ||
| mimeType: 'text/html', | ||
| to: env.GOP_DEVELOPERS | ||
| ) | ||
| } |
| script { | ||
| if (!isTriggeredByTimer()) { | ||
| emailext( | ||
| subject: "${currentBuild.result}: ${env.JOB_NAME} #${env.BUILD_NUMBER}", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both stages "Unit Test" and "Sonar-Scanner" will perform unit tests, so we can merge these into one step.
builds triggered by timer event would have empty RecipientProviders, resulting in a situation where weekly build would not report the build status to anybody. From now on, the whole team will get informed via email