> Just committing, watching for
> errors in the seed job and fixing them isn't very problematic. The
> existing jobs are not touched, if the DSL does not parse correctly, and
> the errors are usually pretty clear where the issue might be. Just do it
> in prod, once it looks about what we want
On 9/4/19 9:01 AM, Mick Semb Wever wrote:
This is going to be a job('Cassandra-template-artifacts') {publishers
...} step in the template, if I recall. Not sure what email plugins are
installed. I'd be happy to look at a PR.
Quick or the dead around here :-)
It has been done manually, an
> This is going to be a job('Cassandra-template-artifacts') {publishers
> ...} step in the template, if I recall. Not sure what email plugins are
> installed. I'd be happy to look at a PR.
Quick or the dead around here :-)
It has been done manually, and a separate PR opened here:
https://gi
On 9/4/19 8:33 AM, Mick Semb Wever wrote:
Jenkins does have this functionality: with "E-mail Notification"
configuration under the "Post-build Actions" section. Emails are sent
when a build fails, becomes unstable or returns to stable, to a
specified ML and the authors of the breakage.
Is t
> Jenkins does have this functionality: with "E-mail Notification"
> configuration under the "Post-build Actions" section. Emails are sent
> when a build fails, becomes unstable or returns to stable, to a
> specified ML and the authors of the breakage.
>
> Is there any objection if I configur
