I think Jenkins asked again after there was an upgrade - seems to happen when 
the PR was opened for a few months.


________________________________
From: Hyukjin Kwon <gurwls...@gmail.com>
Sent: Monday, September 3, 2018 7:05 AM
To: Sean Owen
Cc: dev
Subject: Re: Jenkins automatic disabling service - who and why?

> Looks like for some reason Jenkins first asked for admin approval well after 
> the discussion started.

Oh, for the specific PR, Felix approved a Jenkins test. Jenkins asked this 
before. Somehow after few weeks(?), Jenkins asked it again. It happened 
globally in multiple PRs.
It's not shown because when we type "ok to test", the Jenkins asking is gone 
away.

2018년 9월 3일 (월) 오후 8:54, Hyukjin Kwon 
<gurwls...@gmail.com<mailto:gurwls...@gmail.com>>님이 작성:
Not a big deal but it has been few months since I saw this, and wondering why 
it suddenly asks Jenkins admin verification from at certain point.

I had a small argument about pinging stuff related with this and I failed to 
give the reasons. So I was simply wondering why and who.



On Mon, 3 Sep 2018, 8:04 pm Sean Owen, 
<sro...@gmail.com<mailto:sro...@gmail.com>> wrote:
I'm not sure if anything changed. What is the particular issue here? Looks like 
for some reason Jenkins first asked for admin approval well after the 
discussion started. Nobody asked for a test after that. Can you not trigger it 
from the web app UI?

On Mon, Sep 3, 2018, 1:54 AM Hyukjin Kwon 
<gurwls...@gmail.com<mailto:gurwls...@gmail.com>> wrote:
Hi all,

I lately noticed we started to block Jenkins tests in old PRs. For instance, 
see https://github.com/apache/spark/pull/18447
I don't explicitly object this idea but at least can I ask who and why this was 
started?
Is it for notification purpose or to save resource? Did I miss some discussion 
about this?

Reply via email to