You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2022/01/13 21:54:06 UTC
[camel-website] branch pr/notify-zulip updated (ea445b9 -> 5e7d308)
This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a change to branch pr/notify-zulip
in repository https://gitbox.apache.org/repos/asf/camel-website.git.
discard ea445b9 tmp: fail fast (will be removed)
discard 2c53eed chore: failed build notification on Zulip
new 5e7d308 chore: failed build notification on Zulip
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ea445b9)
\
N -- N -- N refs/heads/pr/notify-zulip (5e7d308)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Jenkinsfile | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
[camel-website] 01/01: chore: failed build notification on Zulip
Posted by zr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch pr/notify-zulip
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 5e7d308910389b924b0452ec83b53a271bbe90f3
Author: Zoran Regvart <zo...@regvart.com>
AuthorDate: Thu Jan 13 22:43:12 2022 +0100
chore: failed build notification on Zulip
This uses the Zulip mail-in functionality to send messages for failed
builds.
---
Jenkinsfile | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Jenkinsfile b/Jenkinsfile
index 346c897..d90471e 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -110,5 +110,11 @@ pipeline {
always {
sh "$WORKSPACE/docker-pipe/teardown.sh"
}
+ fixed {
+ mail subject: 'Website build status', body: "🥳 Build succeeded!", to: 'camel-website.874fb06555c2b4407efde9f9a3b13c13.show-sender@streams.zulipchat.com'
+ }
+ unsuccessful {
+ mail subject: 'Website build status', body: "😞 Build failed. Please have a look at the build output at: ${env.BUILD_URL}", to: 'camel-website.874fb06555c2b4407efde9f9a3b13c13.show-sender@streams.zulipchat.com'
+ }
}
}