Today I realized that I want to be notified (via the "publisher") of
successful builds, even if the previous build was successful. I want
this so I can be sure the CI is actually still running without
problems.
I browsed the source code, and found the method that seems to specify
which updates to send when (Utils#interpret_state). Once I understood
how that works, I realized there is already a configuration option for
this behavior! Which works great.
So, I'm contributing an update to the FAQ, below! (I would commit to
Github, if you allow "outside" or "beginning user" committers on your
project.)
Cheers,
Matt
--------------------------
[FAQ] update on how to be notified of all activity, including
successful builds
changed
doc/site/src/faq.page158
@@ -154,3 +154,17 @@ If you want to add Darcs (or other custom SCM)
project to cerberus, you should e
<pre>cerberus add PROJECT_DIR SCM=darcs</pre>
Currently supported SCM systems are SVN, Darcs, Perforce and CVS.
+
+### How to be notified of all activity (including successful builds)
+
+By default, Cerberus does not publish a notification after a
successful build, unless the build before it was unsuccessful.
+
+To always be notified of successful builds:
+
+<pre>
+publisher:
+ on_event: all
+</pre>
+
+
+
We accept contributions from everyone, no matter what the level of
previous contribution so don't hesitate to submit any kind of patch or
GitHub pull requests in the future.
Thanks again,
Craig
> --
>
> You received this message because you are subscribed to the Google Groups "Cerberus" group.
> To post to this group, send email to cerbe...@googlegroups.com.
> To unsubscribe from this group, send email to cerberusci+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cerberusci?hl=en.
>
>
>