You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by st...@apache.org on 2017/11/29 08:46:56 UTC
[maven-jenkins-env] branch master updated: Better commit message
formatting
This is an automated email from the ASF dual-hosted git repository.
stephenc pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-jenkins-env.git
The following commit(s) were added to refs/heads/master by this push:
new 4a5f51e Better commit message formatting
4a5f51e is described below
commit 4a5f51effb589e0abb551aad5d488c3450e675c6
Author: Stephen Connolly <st...@gmail.com>
AuthorDate: Wed Nov 29 08:46:49 2017 +0000
Better commit message formatting
It is important to indent multi-line comments correctly
---
vars/jenkinsNotify.groovy | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vars/jenkinsNotify.groovy b/vars/jenkinsNotify.groovy
index a8efeed..1c7e0ec 100644
--- a/vars/jenkinsNotify.groovy
+++ b/vars/jenkinsNotify.groovy
@@ -34,7 +34,7 @@ def call(Map params = [:]) {
messageBody = messageBody + "\n\nChanges:\n";
for (def changeSet in currentBuild.changeSets) {
for (def change in changeSet) {
- messageBody = messageBody + "\n* ${change.msg}"
+ messageBody = messageBody + "\n* ${change.msg.trim().replaceAll('\n','\n ')}"
}
}
}
--
To stop receiving notification emails like this one, please contact
['"commits@maven.apache.org" <co...@maven.apache.org>'].