Skip to content

Commit cf3b7a0

Browse files
author
Ataxexe
committed
add a readme file
1 parent 6a7733d commit cf3b7a0

File tree

1 file changed

+41
-0
lines changed

1 file changed

+41
-0
lines changed

README.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
= Jenkins Notifier
2+
3+
This is a plugin to enable build notifications through [Pushover][] or [Telegram][].
4+
5+
== How to build
6+
7+
Just execute a `mvn package` and upload the *hpi* package to your Jenkins instance.
8+
9+
== How to configure
10+
11+
There are global and specific options:
12+
13+
=== Global options
14+
15+
Global options should be configured in Jenkins System Configuration. You'll need to set
16+
an Application Token for Pushover and/or a Bot Token for Telegram.
17+
18+
=== Specific options
19+
20+
There are per-job configurations. You need to add a post-build step (there is a separated
21+
step for each notification service) and configure the target to receive notifications.
22+
23+
== How you'll be notified
24+
25+
Notifications will include:
26+
27+
- The project's name
28+
- The build number
29+
- The build result
30+
- The build link
31+
32+
If you are receiving notifications through Pushover, the notification will be sent with
33+
high priority in case of a fail build, low priority in case of a success build and normal
34+
priority for the other cases.
35+
36+
Note that Telegram doesn't have a way to set priority for messages (and is understandable
37+
because Telegram is a chat platform and not a notification platform like Pushover).
38+
39+
== How to contribute
40+
41+
Open an issue, spread the project, use it, fork it...

0 commit comments

Comments
 (0)