accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: More jenkins results
Date Fri, 13 Mar 2015 20:54:25 GMT
Ok, I figured out how to do jenkins roles so that I can limit things 
down to a specific set of jobs.

I'll change my nightly 1.6 and master branch IT jobs to send to 
notifications@ and we can go from there. I won't duplicate normal UT 
jobs from apache jenkins.

Mike Drob wrote:
> If it goes to notifications@ that is inherently a noisy list and I'm not
> worried about Josh taking a week off and a nightly build failing and
> sending an email.
> Christopher, would a set of keys held in escrow cover your concerns?
> Josh, thanks for doing this and keeping it running on your own dime. A real
> mensch!
> On Mar 13, 2015 2:43 PM, "Christopher"<>  wrote:
>> I'm not suggesting to impose external control. I just think it'd be
>> nice to know that, if the worst were to happen, and the service
>> started behaving badly while you were on vacation, we'd have some
>> recourse to control the automated notices to the email lists.
>> [ If you do get hit by a truck, I *will* call you out on it ;) ]
>> --
>> Christopher L Tubbs II
>> On Fri, Mar 13, 2015 at 3:32 PM, Josh Elser<>  wrote:
>>> If I wasn't clear the first time, anyone can view the results right now.
>>> I'm still not sure why you feel the need to impose external control over
>> a
>>> system that I'm paying for and offering to provide as a service to the
>>> project. Unless I get hit by a truck, it's not like I won't be
>> responsive --
>>> and if I do rescind on that promise, you are more than welcome to call me
>>> out on it. Being unresponsive is one criticism that I don't think I've
>> been
>>> given WRT Accumulo.
>>> IMO, the real question here is are people going to be looking at these
>>> results and doing anything with them? If they're just going to /dev/null,
>>> it's not worth it to me and I'll just do triage/fixing as I find time.
>>> Christopher wrote:
>>>> Looks fine in Chrome to me (but my Chrome is using my shared NSS
>>>> certificate store for my system).
>>>> I can't think of anything immediately to configure... just speculating
>>>> that it might add utility when needed. At the very least, I would want
>>>> more than one person with the ability to turn off / modify the email
>>>> to the mailing list, if necessary.
>>>> Being able to view the results without configuration permissions would
>>>> still be added value on its own, though.
>>>> --
>>>> Christopher L Tubbs II
>>>> On Fri, Mar 13, 2015 at 2:56 PM, Josh Elser<>
>> wrote:
>>>>> Maybe this will help too. Last night's builds:
>>>>> If you use Chrome, I don't think they accept StartCom SSL certs as
>>>>> trusted
>>>>> (so you'll get the crazy-scary red warning page), but it should be
>>>>> trusted
>>>>> by default in FF.
>>>>> Josh Elser wrote:
>>>>>> Presently, you can see the full workspace for the last job that was
>> run.
>>>>>> I'd have to look into Jenkins permissions, but what exactly do you
>> think
>>>>>> you would need to configure?
>>>>>> Christopher wrote:
>>>>>>> That might only be valuable if we could log on to it to view
the test
>>>>>>> results and/or configure the jobs.
>>>>>>> --
>>>>>>> Christopher L Tubbs II
>>>>>>> On Fri, Mar 13, 2015 at 1:24 PM, Josh Elser<>
>>>>>>> wrote:
>>>>>>>> For those who don't know, I run a Jenkins instance on a VPS
I own.
>>>>>>>> I've been
>>>>>>>> running ITs for 1.6 and master nightly for some time now
and it's
>> been
>>>>>>>> really nice to get these results. It has just enough resources
>> run
>>>>>>>> through them reliably (some of the really heavy-handed tests
fail on
>>>>>>>> it),
>>>>>>>> but personally it feels like a good baseline for ensuring
the tests
>>>>>>>> are
>>>>>>>> runnable by anyone.
>>>>>>>> If others feel like they might get value from it, I can set
>> emails
>>>>>>>> to be
>>>>>>>> sent to the list instead
of just
>> to
>>>>>>>> myself.
>>>>>>>> Thoughts/Opinions?

View raw message