[jbosstools-dev] Can we have a jenkins build triggered upon github PR?

Xavier Coulon xcoulon at redhat.com
Tue Apr 26 12:43:18 EDT 2016


starting with a) would be great, indeed.

/Xavier

> On 26 Apr 2016, at 17:50, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> a first.
> 
> b is a separate thing and much more complex IMO
> 
> c how is that different from b ?
> 
> in other words, start with a :)
> 
> /max
>> Hi
>> 
>> I'd love to get a build triggered when I create a PR in github. That
>> would allow me to force awareness of breaking tests with a change.
>> When talking to Nick he was pointing out that there are actually 3 items
>> that he's after currently, where my suggestion is the 1st of these aims.
>> 
>> a) does the PR break my tests / want a green light on the PR page
>> b) does the PR break downstream (eg., API change in Base breaks Server
>> or UI change in Server breaks Openshift)
>> c) does the PR need to be aggregated into JBT or JBDS so we can see it
>> in the larger context
>> 
>> a) is what I'd love to get and is good enough for me now.
>> b) is imho a nice-to-have but wasnt that much of a problem in OpenShift
>> lately.
>> c) I guess is the larger picture where we want to achieve continous
>> delivery.
>> 
>> Nick wants to know about the need of other component leads. So please
>> speak up. a), b), c), all of them, etc?
>> 
>> Cheers
>> Andre
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



More information about the jbosstools-dev mailing list