On August 26, 2014 at 8:57:41 AM, Justin Pettit (jpet...@nicira.com) wrote:
>
> > On Aug 26, 2014, at 8:48 AM, Ben Pfaff wrote:
> >
> >> On Mon, Aug 25, 2014 at 06:13:14PM +0200, Thomas Graf wrote:
> >> Can you setup a mailing list for the reports on openvswitch.org
> >> and set an environment va
> On Aug 26, 2014, at 8:48 AM, Ben Pfaff wrote:
>
>> On Mon, Aug 25, 2014 at 06:13:14PM +0200, Thomas Graf wrote:
>> Can you setup a mailing list for the reports on openvswitch.org
>> and set an environment variable in the github settings to contain
>> the address of the list? [1]
>
> Justin, c
On Mon, Aug 25, 2014 at 06:13:14PM +0200, Thomas Graf wrote:
> Can you setup a mailing list for the reports on openvswitch.org
> and set an environment variable in the github settings to contain
> the address of the list? [1]
Justin, can we create an "ovs-build" or "ovs-ci" mailing list?
_
On 08/25/14 at 06:13pm, Thomas Graf wrote:
> I'll work out the travis.yml details, looks like extending it
> with something like below should do:
>
> notifications:
> email:
> recipients:
> - $BUILD_CI_LIST
>
> Can you setup a mailing list for the reports on openvswitch.org
> and set
On 08/25/14 at 09:01am, Ben Pfaff wrote:
> On Mon, Aug 25, 2014 at 05:58:09PM +0200, Thomas Graf wrote:
> > On 08/25/14 at 08:50am, Ben Pfaff wrote:
> > > Is there a way to get emailed build success/failure reports?
> >
> > Yes:
> >
> > 1. You can connect the main ovs git repo to travis-ci. This
On Mon, Aug 25, 2014 at 05:58:09PM +0200, Thomas Graf wrote:
> On 08/25/14 at 08:50am, Ben Pfaff wrote:
> > Is there a way to get emailed build success/failure reports?
>
> Yes:
>
> 1. You can connect the main ovs git repo to travis-ci. This will
>result in a email to both the author and comm
On 08/25/14 at 08:50am, Ben Pfaff wrote:
> This sounds great. Applied.
Thanks
> Is there a way to get emailed build success/failure reports?
Yes:
1. You can connect the main ovs git repo to travis-ci. This will
result in a email to both the author and commiter if a new
commit to any bran
On Mon, Aug 25, 2014 at 02:51:00PM +0200, Thomas Graf wrote:
> This enables the use of travis-ci via github. Linking any ovs
> github repo to travis-ci [0] will automatically lead to a build
> and testsuite run being triggered for each new commit or pull
> requests against the repo.
>
> The introd
On 08/25/14 at 02:51pm, Thomas Graf wrote:
> This enables the use of travis-ci via github. Linking any ovs
> github repo to travis-ci [0] will automatically lead to a build
> and testsuite run being triggered for each new commit or pull
> requests against the repo.
Given the above, we can consider
This enables the use of travis-ci via github. Linking any ovs
github repo to travis-ci [0] will automatically lead to a build
and testsuite run being triggered for each new commit or pull
requests against the repo.
The introduction of any warnings will cause the build to fail as
both gcc and clang
10 matches
Mail list logo
