Jenkins is set up and was working for a time.  Then one night I magically 
stopped getting notifications.

Ralph

On Apr 14, 2014, at 2:18 PM, Matt Sicker <[email protected]> wrote:

> Oh, my bad, I thought I was replying to the dev list. That's what happens 
> when I don't pay attention!
> 
> I'm not sure about the github thing. I tried filing a ticket with INFRA and 
> they basically said "fuck github" in so many words. As long as Jenkins is set 
> up, we don't need to worry about Travis.
> 
> 
> On 14 April 2014 10:30, Ralph Goers <[email protected]> wrote:
> Matt, 
> 
> Please reply to commits to the dev list.  Although I do review the commits it 
> isn’t always as timely as reviewing the dev list.
> 
> Yes, I have a github account although I rarely use it.
> 
> I’ve never even heard of Travis before so it may require a bit of work.  
> Also, all PMC members should have the same authorizations I do.  In fact, 
> Christian should have a few more as PMC chair.
> 
> Ralph
> 
> 
> On Apr 13, 2014, at 4:27 PM, Matt Sicker <[email protected]> wrote:
> 
>> Ralph, do you have a GitHub account set up? You may have to be the one to 
>> allow Travis CI to work.
>> 
>> 
>> On 13 April 2014 17:10, <[email protected]> wrote:
>> Author: mattsicker
>> Date: Sun Apr 13 23:10:02 2014
>> New Revision: 1587119
>> 
>> URL: http://svn.apache.org/r1587119
>> Log:
>> Add basic travis config.
>> 
>>   - Not sure if this will work with GitHub, but it's worth a shot!
>> 
>> Added:
>>     logging/log4j/log4j2/trunk/.travis.yml
>> 
>> Added: logging/log4j/log4j2/trunk/.travis.yml
>> URL: 
>> http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/.travis.yml?rev=1587119&view=auto
>> ==============================================================================
>> --- logging/log4j/log4j2/trunk/.travis.yml (added)
>> +++ logging/log4j/log4j2/trunk/.travis.yml Sun Apr 13 23:10:02 2014
>> @@ -0,0 +1,5 @@
>> +language: java
>> +
>> +jdk:
>> +    - oraclejdk8
>> +    - oraclejdk7
>> 
>> 
>> 
> 
> 
> 
> 
> -- 
> Matt Sicker <[email protected]>

Reply via email to