cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <da...@gnsa.us>
Subject Re: Automatically trigger a new Jenkins build
Date Mon, 09 Nov 2015 17:00:56 GMT
Which Jenkins?

On Thu, Oct 29, 2015 at 10:11 AM, Remi Bergsma
<RBergsma@schubergphilis.com> wrote:
> Hi all,
>
> Just had a chat with Miguel.
> He showed me that if we setup Github to notify Jenkins on “issue comments”
> (next to “pull requests” we have now) and then set a “trigger phrase” in
> Jenkins, we could automatically trigger a new build by typing “go build”. No
> more need to force push commits by the author.
>
> Shall we set this up? Can we do this David?
>
> Regards,
> Remi
>
>
> From: Remi Bergsma
> Date: Thursday 29 October 2015 08:47
> To: "dev@cloudstack.apache.org"
> Subject: Jenkins failures
>
> Hi,
>
> Can someone please look why Jenkins fails so often recently? It feels like a
> casino and slows down merging of PRs since we want to merge when they “are
> green”. This requires forse pushing many times now, including the wait.
>
> I’d prefer not to start ignoring them..
>
> Thanks for the help!
>
> Regards,
> Remi
>

Mime
View raw message