If the community wishes we can enable travis-ci to do email alerts. It will
email the person who broke the branch.
On 17 September 2014 12:33, sebgoa wrote:
> Hi folks,
>
> With Travis tests now passing, it's a good time for everyone to get
> familiar with it and understanding the tests that are
The checkin by Min was not the problem (Edisons was on his own branch)
Rohit showed me the travis run on this commit in his travis account. It was
green.
So our travis setup is not perfect yet :(
On Wed, Sep 17, 2014 at 2:34 PM, Ian Duffy wrote:
> If the community wishes we can enable travis-ci
On 17-Sep-2014, at 2:58 pm, Daan Hoogland wrote:
> The checkin by Min was not the problem (Edisons was on his own branch)
> Rohit showed me the travis run on this commit in his travis account. It was
> green.
>
> So our travis setup is not perfect yet :(
We have a hypothesis that all the apache
On Sep 17, 2014, at 3:28 PM, Rohit Yadav wrote:
>
> On 17-Sep-2014, at 2:58 pm, Daan Hoogland wrote:
>> The checkin by Min was not the problem (Edisons was on his own branch)
>> Rohit showed me the travis run on this commit in his travis account. It was
>> green.
>>
>> So our travis setup is
I only checked into my personal branch: pytest, which is converting nose to
pytest, so if you run nose against pytest test cases, definitely, it will fail.
I think it's ok to fail for travis on my pytest branch at this time, as I
haven't start the discussion in the community about how to improve
Hi All,
For anybody interested I setup my own mirror of cloudstack:
https://github.com/cs-travis-runs/cs-travis-run
It will check for updates every 5 minutes.
As this isn't owned by the apache travis account we get all 5 concurrent
jobs to ourselves. Along with this we can assign user roles so pe
