Re: [Tails-dev] Automated builds specification

On Tue, Feb 17, 2015 at 09:47:51PM +0100, intrigeri wrote:
> bertagaz wrote (16 Feb 2015 14:37:56 GMT) :
> > On Thu, Feb 12, 2015 at 12:22:45AM +0100, intrigeri wrote:
> >> Here's one more: the proposed notification mechanism makes sense to me
> >> for topic branches. But for "base" branches, it's more complicated:
>
> >> Thoughts?
>
> > Agree with that as stated in my previous email.
>
> OK, good. Then I'll let you capture in the specification that problem,
> and our currently preferred solution.

Done.

> What follows is only interesting for Jenkins folks. I guess almost
> everyone but DrWhax and bertagaz can stop here.
>
> > I think it is doable to differenciate them, by splitting the daily
> > and on git push job definiton maybe.
>
> => I think this trick would make the overall thing hard to understand
> and draw conclusions from, for anyone not deeply involved in our
> Jenkins stuff.

That's my opinion too.

> > Having a look at plugins might help, as well as how other projects
> > do that (as you stated elsewhere).
>
> Yep. At least the obvious candidate (Email-ext plugin) doesn't seem
> able to email different recipients depending on what triggered the
> build out-of-the-box. But apparently, one can set up two 'Script -
> After Build' email triggers in the Email-ext configuration: one emails
> the culprit, the other emails the RM. And then, they do something or
> not depending on a variable we set during the build, based on what
> triggered the build. Likely the cleaner and simpler solution.
>
> Otherwise, we could have Jenkins email some pipe script that will
> forward to the right person depending on 1. whether it's a base
> branch; and 2. whether the build was triggered by a push or by
> something else. This should work if we can get the email notification
> to pass the needed info in it. E.g. the full console output currently
> has "Started by timer" or "Started by an SCM change", but this is not
> part of the email notification. Could work, but a bit hackish and all
> kinds of things can go wrong.
>
> Also, I've seen lots of people documenting crazy similar things with
> some of these plugins: "Run Condition", "Conditional BuildStep",
> "Flexible Publish" and "Any Build step". But then it gets too
> complicated for me to dive into it right now.

Yes, feel also quite lost in all this big Jenkins ecosystem sometimes. But
it's certainly doable. I'll spend time digging into this too.

> If you prefer, in the future I can dump such research results into the
> blueprint instead of here. Just tell me where it should go.

The blueprint/automated_builds_and_tests/jenkins page seems perfect for
that.

bert.