subject:"Re\: Jenkins\-Builds failing"

Re: Jenkins-Builds failing

2018-09-02 Thread Gintautas Grigelionis

I see that Ant 1.9.13 is available as a choice, but Ivy Check job is still
owned by hibou, and thus it is not possible to change the configuration.
Is there a case about changing the ownership of all Ivy jobs? Or is it so
that dependencies between Jenkins jobs are still an issue?

Gintas

On Mon, 13 Aug 2018 at 12:26, Jaikiran Pai  wrote:

> Noted. Just waiting for the infra team to sort out the access issue.
>
> -Jaikiran
>
>
> On 12/08/18 2:28 AM, Gintautas Grigelionis wrote:
> > Hi Jan and Jaikiran,
> >
> > looks like IvyDE trunk build needs attention, too (SSL protocol failure
> > when resolving Checkstyle).
> >
> > Thanks, Gintas
> >
> > On Wed, 8 Aug 2018 at 13:23, Jan Matèrne (jhm) 
> wrote:
> >
> >> Tried to change from "Ant 1.9.9" to "Ant (latest)".
> >> An "Ant 1.10.1" or an "Ant 1.9.9" are the latest available named
> versions.
> >>
> >> Got an
> >>   Access denied
> >>   This job's current authorization strategy does not permit jhm to
> modify
> >> the job configuration
> >>
> >> Asked in https://issues.apache.org/jira/browse/INFRA-16799 for
> >> checking+fixing all of our jobs.
> >>
> >>
> >> Jan
> >>
> >>> -Ursprüngliche Nachricht-
> >>> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> >>> Gesendet: Montag, 6. August 2018 06:45
> >>> An: dev@ant.apache.org
> >>> Betreff: Re: Jenkins-Builds failing
> >>>
> >>> Sure, will fix it this week. Right now, I don't have necessary
> >>> permissions to edit it.
> >>>
> >>> -Jaikiran
> >>>
> >>>
> >>> On 05/08/18 8:58 PM, Gintautas Grigelionis wrote:
> >>>> There's one more Jenkins job failing due to outdated Ant, Ivy Check (
> >>>> https://builds.apache.org/view/All/job/Ivy-check/).
> >>>> Could you please check it, Jaikiran?
> >>>>
> >>>> Thanks, Gintas
> >>>>
> >>>> On Sun, 29 Jul 2018 at 15:13, Jaikiran Pai 
> >>> wrote:
> >>>>> I would like to test/import a few more projects (that Nicolas
> >>>>> mentioned in one the mails) locally into the latest upstream version
> >>>>> of the IDE, before starting a release. I have only tested a few so
> >>> far.
> >>>>> -Jaikiran
> >>>>>
> >>>>> On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
> >>>>>> Thanks, Jaikiran. Would you be willing to restart the release
> >>>>>> process for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43,
> >>> Jaikiran
> >>>>>> Pai  wrote:
> >>>>>>> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> >>>>>>>> Almost all jobs that I know of have been taken care of now.
> >>>>>>>> There's a "Ivy-tests-Windows" job which is pending, but for that
> >>> I
> >>>>>>>> need some help from infra team. I am discussing it with them
> >>>>>>>> separately and I expect it to be resolved soon. I'll fix that job
> >>> tomorrow.
> >>>>>>> This is now done too. -Jaikiran
> >>>>>>> --
> >>> -
> >>>>>>> -- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
> >>>>>>> additional commands, e-mail: dev-h...@ant.apache.org
> >>>>> 
> >>> -
> >>>>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
> >>> additional
> >>>>> commands, e-mail: dev-h...@ant.apache.org
> >>>>>
> >>>>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> >>> commands, e-mail: dev-h...@ant.apache.org
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> >> For additional commands, e-mail: dev-h...@ant.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins-Builds failing

2018-08-13 Thread Jaikiran Pai

Noted. Just waiting for the infra team to sort out the access issue.

-Jaikiran


On 12/08/18 2:28 AM, Gintautas Grigelionis wrote:
> Hi Jan and Jaikiran,
>
> looks like IvyDE trunk build needs attention, too (SSL protocol failure
> when resolving Checkstyle).
>
> Thanks, Gintas
>
> On Wed, 8 Aug 2018 at 13:23, Jan Matèrne (jhm)  wrote:
>
>> Tried to change from "Ant 1.9.9" to "Ant (latest)".
>> An "Ant 1.10.1" or an "Ant 1.9.9" are the latest available named versions.
>>
>> Got an
>>   Access denied
>>   This job's current authorization strategy does not permit jhm to modify
>> the job configuration
>>
>> Asked in https://issues.apache.org/jira/browse/INFRA-16799 for
>> checking+fixing all of our jobs.
>>
>>
>> Jan
>>
>>> -Ursprüngliche Nachricht-
>>> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
>>> Gesendet: Montag, 6. August 2018 06:45
>>> An: dev@ant.apache.org
>>> Betreff: Re: Jenkins-Builds failing
>>>
>>> Sure, will fix it this week. Right now, I don't have necessary
>>> permissions to edit it.
>>>
>>> -Jaikiran
>>>
>>>
>>> On 05/08/18 8:58 PM, Gintautas Grigelionis wrote:
>>>> There's one more Jenkins job failing due to outdated Ant, Ivy Check (
>>>> https://builds.apache.org/view/All/job/Ivy-check/).
>>>> Could you please check it, Jaikiran?
>>>>
>>>> Thanks, Gintas
>>>>
>>>> On Sun, 29 Jul 2018 at 15:13, Jaikiran Pai 
>>> wrote:
>>>>> I would like to test/import a few more projects (that Nicolas
>>>>> mentioned in one the mails) locally into the latest upstream version
>>>>> of the IDE, before starting a release. I have only tested a few so
>>> far.
>>>>> -Jaikiran
>>>>>
>>>>> On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
>>>>>> Thanks, Jaikiran. Would you be willing to restart the release
>>>>>> process for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43,
>>> Jaikiran
>>>>>> Pai  wrote:
>>>>>>> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
>>>>>>>> Almost all jobs that I know of have been taken care of now.
>>>>>>>> There's a "Ivy-tests-Windows" job which is pending, but for that
>>> I
>>>>>>>> need some help from infra team. I am discussing it with them
>>>>>>>> separately and I expect it to be resolved soon. I'll fix that job
>>> tomorrow.
>>>>>>> This is now done too. -Jaikiran
>>>>>>> --
>>> -
>>>>>>> -- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
>>>>>>> additional commands, e-mail: dev-h...@ant.apache.org
>>>>> 
>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
>>> additional
>>>>> commands, e-mail: dev-h...@ant.apache.org
>>>>>
>>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
>>> commands, e-mail: dev-h...@ant.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
>> For additional commands, e-mail: dev-h...@ant.apache.org
>>
>>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-08-11 Thread Gintautas Grigelionis

Hi Jan and Jaikiran,

looks like IvyDE trunk build needs attention, too (SSL protocol failure
when resolving Checkstyle).

Thanks, Gintas

On Wed, 8 Aug 2018 at 13:23, Jan Matèrne (jhm)  wrote:

> Tried to change from "Ant 1.9.9" to "Ant (latest)".
> An "Ant 1.10.1" or an "Ant 1.9.9" are the latest available named versions.
>
> Got an
>   Access denied
>   This job's current authorization strategy does not permit jhm to modify
> the job configuration
>
> Asked in https://issues.apache.org/jira/browse/INFRA-16799 for
> checking+fixing all of our jobs.
>
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> > Gesendet: Montag, 6. August 2018 06:45
> > An: dev@ant.apache.org
> > Betreff: Re: Jenkins-Builds failing
> >
> > Sure, will fix it this week. Right now, I don't have necessary
> > permissions to edit it.
> >
> > -Jaikiran
> >
> >
> > On 05/08/18 8:58 PM, Gintautas Grigelionis wrote:
> > > There's one more Jenkins job failing due to outdated Ant, Ivy Check (
> > > https://builds.apache.org/view/All/job/Ivy-check/).
> > > Could you please check it, Jaikiran?
> > >
> > > Thanks, Gintas
> > >
> > > On Sun, 29 Jul 2018 at 15:13, Jaikiran Pai 
> > wrote:
> > >
> > >> I would like to test/import a few more projects (that Nicolas
> > >> mentioned in one the mails) locally into the latest upstream version
> > >> of the IDE, before starting a release. I have only tested a few so
> > far.
> > >>
> > >> -Jaikiran
> > >>
> > >> On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
> > >>> Thanks, Jaikiran. Would you be willing to restart the release
> > >>> process for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43,
> > Jaikiran
> > >>> Pai  wrote:
> > >>>> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> > >>>>> Almost all jobs that I know of have been taken care of now.
> > >>>>> There's a "Ivy-tests-Windows" job which is pending, but for that
> > I
> > >>>>> need some help from infra team. I am discussing it with them
> > >>>>> separately and I expect it to be resolved soon. I'll fix that job
> > tomorrow.
> > >>>> This is now done too. -Jaikiran
> > >>>> --
> > -
> > >>>> -- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
> > >>>> additional commands, e-mail: dev-h...@ant.apache.org
> > >>
> > >> 
> > -
> > >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
> > additional
> > >> commands, e-mail: dev-h...@ant.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> > commands, e-mail: dev-h...@ant.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins-Builds failing

2018-08-05 Thread Jaikiran Pai

Sure, will fix it this week. Right now, I don't have necessary
permissions to edit it.

-Jaikiran


On 05/08/18 8:58 PM, Gintautas Grigelionis wrote:
> There's one more Jenkins job failing due to outdated Ant, Ivy Check (
> https://builds.apache.org/view/All/job/Ivy-check/).
> Could you please check it, Jaikiran?
>
> Thanks, Gintas
>
> On Sun, 29 Jul 2018 at 15:13, Jaikiran Pai  wrote:
>
>> I would like to test/import a few more projects (that Nicolas mentioned
>> in one the mails) locally into the latest upstream version of the IDE,
>> before starting a release. I have only tested a few so far.
>>
>> -Jaikiran
>>
>> On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
>>> Thanks, Jaikiran. Would you be willing to restart the release process
>>> for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43, Jaikiran Pai
>>>  wrote:
 On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> Almost all jobs that I know of have been taken care of now. There's
> a "Ivy-tests-Windows" job which is pending, but for that I need some
> help from infra team. I am discussing it with them separately and I
> expect it to be resolved soon. I'll fix that job tomorrow.
 This is now done too. -Jaikiran
 -
 To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
 commands, e-mail: dev-h...@ant.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
>> For additional commands, e-mail: dev-h...@ant.apache.org
>>
>>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-08-05 Thread Gintautas Grigelionis

There's one more Jenkins job failing due to outdated Ant, Ivy Check (
https://builds.apache.org/view/All/job/Ivy-check/).
Could you please check it, Jaikiran?

Thanks, Gintas

On Sun, 29 Jul 2018 at 15:13, Jaikiran Pai  wrote:

> I would like to test/import a few more projects (that Nicolas mentioned
> in one the mails) locally into the latest upstream version of the IDE,
> before starting a release. I have only tested a few so far.
>
> -Jaikiran
>
> On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
> > Thanks, Jaikiran. Would you be willing to restart the release process
> > for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43, Jaikiran Pai
> >  wrote:
> >> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> >>> Almost all jobs that I know of have been taken care of now. There's
> >>> a "Ivy-tests-Windows" job which is pending, but for that I need some
> >>> help from infra team. I am discussing it with them separately and I
> >>> expect it to be resolved soon. I'll fix that job tomorrow.
> >> This is now done too. -Jaikiran
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> >> commands, e-mail: dev-h...@ant.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins-Builds failing

2018-07-29 Thread Jaikiran Pai

I would like to test/import a few more projects (that Nicolas mentioned
in one the mails) locally into the latest upstream version of the IDE,
before starting a release. I have only tested a few so far.

-Jaikiran

On 28/07/18 2:28 PM, Gintautas Grigelionis wrote:
> Thanks, Jaikiran. Would you be willing to restart the release process
> for IvyDE now? Gintas On Fri, 27 Jul 2018 at 15:43, Jaikiran Pai
>  wrote:
>> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
>>> Almost all jobs that I know of have been taken care of now. There's
>>> a "Ivy-tests-Windows" job which is pending, but for that I need some
>>> help from infra team. I am discussing it with them separately and I
>>> expect it to be resolved soon. I'll fix that job tomorrow. 
>> This is now done too. -Jaikiran
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
>> commands, e-mail: dev-h...@ant.apache.org 
>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-07-28 Thread Gintautas Grigelionis

Thanks, Jaikiran. Would you be willing to restart the release process for
IvyDE now?

Gintas

On Fri, 27 Jul 2018 at 15:43, Jaikiran Pai  wrote:

>
> On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> > Almost all jobs that I know of have been taken care of now. There's a
> > "Ivy-tests-Windows" job which is pending, but for that I need some help
> > from infra team. I am discussing it with them separately and I expect it
> > to be resolved soon. I'll fix that job tomorrow.
> This is now done too.
>
> -Jaikiran
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins-Builds failing

2018-07-27 Thread Jaikiran Pai



On 25/07/18 6:45 PM, Jaikiran Pai wrote:
> Almost all jobs that I know of have been taken care of now. There's a
> "Ivy-tests-Windows" job which is pending, but for that I need some help
> from infra team. I am discussing it with them separately and I expect it
> to be resolved soon. I'll fix that job tomorrow.
This is now done too.

-Jaikiran

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-07-25 Thread Jaikiran Pai

Almost all jobs that I know of have been taken care of now. There's a
"Ivy-tests-Windows" job which is pending, but for that I need some help
from infra team. I am discussing it with them separately and I expect it
to be resolved soon. I'll fix that job tomorrow.

-Jaikiran


On 25/07/18 11:07 AM, Jaikiran Pai wrote:
> There are a few more jobs that need to be reconfigured a bit to get them
> working. I'm working with infra team to have that sorted out. Please
> ignore the failure mails from those jobs for now.
>
> -Jaikiran
>
> On 25/07/18 10:30 AM, Jaikiran Pai wrote:
>> I've committed a change[1] to handle this in the part where we trigger
>> the tutorial run. [1]
>> https://github.com/apache/ant-ivy/commit/43ddccb859b94c79350ece7520af4c991c2bb5e6
>> -Jaikiran On 24/07/18 10:53 PM, Gintautas Grigelionis wrote:
>>> Thank you for all attempts, the failure occurs in run-tutorial macro
>>> (forked JVM). What would be the best way to forwarding Java
>>> arguments/system properties? Gintas On Tue, 24 Jul 2018 at 09:14,
>>> Gintautas Grigelionis  wrote:
>>>> It must be set as Java parameter, not Ant parameter. Gintas On Tue,
>>>> 24 Jul 2018 at 08:38, Jan Matèrne (jhm)  wrote:
>>>>> "Looks like someone called 'hibou' restricted the job to
>>>>> themselves. (See screenshot attached to this ticket)" This was a
>>>>> "run as hibou" configuration. @Nicolas: What was the reason to add
>>>>> that? Is it required? Gavin removed that part and I could add the
>>>>> https.protocols=TLSv1.2 parameter. Job restarted. Jan
>>>>>> -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm)
>>>>>> [mailto:apa...@materne.de] Gesendet: Sonntag, 22. Juli 2018 12:54
>>>>>> An: 'Ant Developers List' Betreff: AW: Jenkins-Builds failing
>>>>>> Checked by myself that a PMC chair could do (AFAIK). Opened a
>>>>>> ticket https://issues.apache.org/jira/browse/INFRA-16799 Jan
>>>>>>> -Ursprüngliche Nachricht- Von: Gintautas Grigelionis
>>>>>>> [mailto:g.grigelio...@gmail.com] Gesendet: Sonntag, 22. Juli 2018
>>>>>>> 10:48 An: Ant Developers List Betreff: Re: Jenkins-Builds failing
>>>>>>> Should we ask infra if nobody else knows about Jenkins
>>>>>>> authorization? Gintas On Fri, 20 Jul 2018 at 11:26, Jan Matèrne
>>>>>>> (jhm)  wrote:
>>>>>>>> Neither do I. Jan
>>>>>>>>> -Ursprüngliche Nachricht- Von: Jaikiran Pai
>>>>>>>>> [mailto:jai.forums2...@gmail.com] Gesendet: Freitag, 20. Juli
>>>>>>>>> 2018 10:15 An: dev@ant.apache.org Betreff: Re: Jenkins-Builds
>>>>>>>>> failing Now that I checked the job's logs, I think that's true.
>>>>>>>>> We had this issue in Ant too (not really against Maven repos,
>>>>>>>>> but HTTPS hosted Apache infrastructure). I tried setting that
>>>>>>>>> property in the job, but I too don't have the necessary
>>>>>>>>> authorization. I 
>>>>>> don't
>>>>>>>>> remember if I ever had those permissions or if it's something 
>>>>>> that
>>>>>>>>> changed with the recent Jenkins upgrade. -Jaikiran On 20/07/18
>>>>>>>>> 1:34 PM, Gintautas Grigelionis wrote:
>>>>>>>>>> My hypothesis is that Java 7 must have TLS version forced to 
>>>>>> 1.2
>>>>>>>>>> in order to avoid protocol errors when downloading new
>>>>>>>>>> binaries from Maven Central because earlier versions are
>>>>>>>>>> disabled [1] (and TLS 1.0 is the default in Java 7). Gintas 1.
>>>>>>>>>> https://blog.pcisecuritystandards.org/are-you-ready-for-30- 
>>>>>> june-
>>>>>>> 20
>>>>>>>>>> 18- 
>>>>>>>>> s
>>>>>>>>>> ayin-goodbye-to-ssl-early-tls On Fri, 20 Jul 2018 at 09:31,
>>>>>>>>>> Jaikiran Pai  
>>>>>>>>> wrote:
>>>>>>>>>>> Haven't checked the job, but why is this system property 
>>>>>>> required
>>>>>>>>>>> to be set? -Jaikiran On 20/07/18 12:51 AM, Gintautas
>>>>>>>>>>> Grigelionis wrote:
>

Re: Jenkins-Builds failing

2018-07-25 Thread Nicolas Lalevée




> Le 24 juil. 2018 à 08:38, Jan Matèrne (jhm)  a écrit :
> 
> "Looks like someone called 'hibou' restricted the job to themselves. (See 
> screenshot attached to this ticket)"
> 
> This was a "run as hibou" configuration.
> 
> @Nicolas: What was the reason to add that? Is it required?

For some reason, this was the only way to make job dependencies work: once 
IvyDE is built, it will trigger the build of the updatesite. When I setup it, 
there was some right issues, the job trigger was done as ‘anonymous’, so I 
forced the job to run as 'me'.

Nicolas

> 
> 
> Gavin removed that part and I could add the https.protocols=TLSv1.2 parameter.
> Job restarted.
> 
> 
> Jan
> 
> 
>> -Ursprüngliche Nachricht-
>> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
>> Gesendet: Sonntag, 22. Juli 2018 12:54
>> An: 'Ant Developers List'
>> Betreff: AW: Jenkins-Builds failing
>> 
>> Checked by myself that a PMC chair could do (AFAIK).
>> Opened a ticket
>> https://issues.apache.org/jira/browse/INFRA-16799
>> 
>> Jan
>> 
>>> -Ursprüngliche Nachricht-----
>>> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
>>> Gesendet: Sonntag, 22. Juli 2018 10:48
>>> An: Ant Developers List
>>> Betreff: Re: Jenkins-Builds failing
>>> 
>>> Should we ask infra if nobody else knows about Jenkins authorization?
>>> 
>>> Gintas
>>> 
>>> On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm) 
>>> wrote:
>>> 
>>>> Neither do I.
>>>> 
>>>> Jan
>>>> 
>>>>> -Ursprüngliche Nachricht-
>>>>> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
>>>>> Gesendet: Freitag, 20. Juli 2018 10:15
>>>>> An: dev@ant.apache.org
>>>>> Betreff: Re: Jenkins-Builds failing
>>>>> 
>>>>> Now that I checked the job's logs, I think that's true. We had
>>>>> this issue in Ant too (not really against Maven repos, but HTTPS
>>>>> hosted Apache infrastructure). I tried setting that property in
>>>>> the job, but I too don't have the necessary authorization. I
>> don't
>>>>> remember if I ever had those permissions or if it's something
>> that
>>>>> changed with the recent Jenkins upgrade.
>>>>> 
>>>>> -Jaikiran
>>>>> 
>>>>> 
>>>>> On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
>>>>>> My hypothesis is that Java 7 must have TLS version forced to
>> 1.2
>>>>>> in order to avoid protocol errors when downloading new binaries
>>>>>> from Maven Central because earlier versions are disabled [1]
>>>>>> (and TLS 1.0 is the default in Java 7).
>>>>>> 
>>>>>> Gintas
>>>>>> 
>>>>>> 1.
>>>>>> https://blog.pcisecuritystandards.org/are-you-ready-for-30-
>> june-
>>> 20
>>>>>> 18-
>>>>> s
>>>>>> ayin-goodbye-to-ssl-early-tls
>>>>>> 
>>>>>> On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai
>>>>>> 
>>>>> wrote:
>>>>>> 
>>>>>>> Haven't checked the job, but why is this system property
>>> required
>>>>>>> to be set?
>>>>>>> 
>>>>>>> -Jaikiran
>>>>>>> 
>>>>>>> 
>>>>>>> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
>>>>>>>> I'd like to add a Java option to Ivy builds
>>>>>>>> -Dhttps.protocols=TLSv1.2
>>>>>>> but I
>>>>>>>> get
>>>>>>>> This job's current authorization strategy does not permit
>>> gintas
>>>>>>>> to
>>>>>>> modify
>>>>>>>> the job configuration
>>>>>>>> 
>>>>>>>> Gintas
>>>>>>>> 
>>>>>>>> On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis <
>>>>>>> g.grigelio...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Ant nightly is stuck on archiving for 30 hours now.
>>>>>>>>> It should be escalated, I believe that could have something
>>>>>>>>> to do with
>>

Re: Jenkins-Builds failing

2018-07-24 Thread Jaikiran Pai

There are a few more jobs that need to be reconfigured a bit to get them
working. I'm working with infra team to have that sorted out. Please
ignore the failure mails from those jobs for now.

-Jaikiran

On 25/07/18 10:30 AM, Jaikiran Pai wrote:
> I've committed a change[1] to handle this in the part where we trigger
> the tutorial run. [1]
> https://github.com/apache/ant-ivy/commit/43ddccb859b94c79350ece7520af4c991c2bb5e6
> -Jaikiran On 24/07/18 10:53 PM, Gintautas Grigelionis wrote:
>> Thank you for all attempts, the failure occurs in run-tutorial macro
>> (forked JVM). What would be the best way to forwarding Java
>> arguments/system properties? Gintas On Tue, 24 Jul 2018 at 09:14,
>> Gintautas Grigelionis  wrote:
>>> It must be set as Java parameter, not Ant parameter. Gintas On Tue,
>>> 24 Jul 2018 at 08:38, Jan Matèrne (jhm)  wrote:
>>>> "Looks like someone called 'hibou' restricted the job to
>>>> themselves. (See screenshot attached to this ticket)" This was a
>>>> "run as hibou" configuration. @Nicolas: What was the reason to add
>>>> that? Is it required? Gavin removed that part and I could add the
>>>> https.protocols=TLSv1.2 parameter. Job restarted. Jan
>>>>> -Ursprüngliche Nachricht- Von: Jan Matèrne (jhm)
>>>>> [mailto:apa...@materne.de] Gesendet: Sonntag, 22. Juli 2018 12:54
>>>>> An: 'Ant Developers List' Betreff: AW: Jenkins-Builds failing
>>>>> Checked by myself that a PMC chair could do (AFAIK). Opened a
>>>>> ticket https://issues.apache.org/jira/browse/INFRA-16799 Jan
>>>>>> -Ursprüngliche Nachricht- Von: Gintautas Grigelionis
>>>>>> [mailto:g.grigelio...@gmail.com] Gesendet: Sonntag, 22. Juli 2018
>>>>>> 10:48 An: Ant Developers List Betreff: Re: Jenkins-Builds failing
>>>>>> Should we ask infra if nobody else knows about Jenkins
>>>>>> authorization? Gintas On Fri, 20 Jul 2018 at 11:26, Jan Matèrne
>>>>>> (jhm)  wrote:
>>>>>>> Neither do I. Jan
>>>>>>>> -Ursprüngliche Nachricht- Von: Jaikiran Pai
>>>>>>>> [mailto:jai.forums2...@gmail.com] Gesendet: Freitag, 20. Juli
>>>>>>>> 2018 10:15 An: dev@ant.apache.org Betreff: Re: Jenkins-Builds
>>>>>>>> failing Now that I checked the job's logs, I think that's true.
>>>>>>>> We had this issue in Ant too (not really against Maven repos,
>>>>>>>> but HTTPS hosted Apache infrastructure). I tried setting that
>>>>>>>> property in the job, but I too don't have the necessary
>>>>>>>> authorization. I 
>>>>> don't
>>>>>>>> remember if I ever had those permissions or if it's something 
>>>>> that
>>>>>>>> changed with the recent Jenkins upgrade. -Jaikiran On 20/07/18
>>>>>>>> 1:34 PM, Gintautas Grigelionis wrote:
>>>>>>>>> My hypothesis is that Java 7 must have TLS version forced to 
>>>>> 1.2
>>>>>>>>> in order to avoid protocol errors when downloading new
>>>>>>>>> binaries from Maven Central because earlier versions are
>>>>>>>>> disabled [1] (and TLS 1.0 is the default in Java 7). Gintas 1.
>>>>>>>>> https://blog.pcisecuritystandards.org/are-you-ready-for-30- 
>>>>> june-
>>>>>> 20
>>>>>>>>> 18- 
>>>>>>>> s
>>>>>>>>> ayin-goodbye-to-ssl-early-tls On Fri, 20 Jul 2018 at 09:31,
>>>>>>>>> Jaikiran Pai  
>>>>>>>> wrote:
>>>>>>>>>> Haven't checked the job, but why is this system property 
>>>>>> required
>>>>>>>>>> to be set? -Jaikiran On 20/07/18 12:51 AM, Gintautas
>>>>>>>>>> Grigelionis wrote:
>>>>>>>>>>> I'd like to add a Java option to Ivy builds
>>>>>>>>>>> -Dhttps.protocols=TLSv1.2 
>>>>>>>>>> but I
>>>>>>>>>>> get This job's current authorization strategy does not permit 
>>>>>> gintas
>>>>>>>>>>> to 
>>>>>>>>>> modify
>>>>>>>>>>> the job configuration Gintas On Tue, 3 Jul 2018 at 19:09,
>>>>>>>>>>> Gintautas Gr

Re: Jenkins-Builds failing

2018-07-24 Thread Jaikiran Pai

I've committed a change[1] to handle this in the part where we trigger
the tutorial run.


[1]
https://github.com/apache/ant-ivy/commit/43ddccb859b94c79350ece7520af4c991c2bb5e6

-Jaikiran


On 24/07/18 10:53 PM, Gintautas Grigelionis wrote:
> Thank you for all attempts, the failure occurs in run-tutorial macro
> (forked JVM).
> What would be the best way to forwarding Java arguments/system properties?
>
> Gintas
>
> On Tue, 24 Jul 2018 at 09:14, Gintautas Grigelionis 
> wrote:
>
>> It must be set as Java parameter, not Ant parameter.
>>
>> Gintas
>>
>> On Tue, 24 Jul 2018 at 08:38, Jan Matèrne (jhm)  wrote:
>>
>>> "Looks like someone called 'hibou' restricted the job to themselves. (See
>>> screenshot attached to this ticket)"
>>>
>>> This was a "run as hibou" configuration.
>>>
>>> @Nicolas: What was the reason to add that? Is it required?
>>>
>>>
>>> Gavin removed that part and I could add the https.protocols=TLSv1.2
>>> parameter.
>>> Job restarted.
>>>
>>>
>>> Jan
>>>
>>>
>>>> -Ursprüngliche Nachricht-
>>>> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
>>>> Gesendet: Sonntag, 22. Juli 2018 12:54
>>>> An: 'Ant Developers List'
>>>> Betreff: AW: Jenkins-Builds failing
>>>>
>>>> Checked by myself that a PMC chair could do (AFAIK).
>>>> Opened a ticket
>>>> https://issues.apache.org/jira/browse/INFRA-16799
>>>>
>>>> Jan
>>>>
>>>>> -Ursprüngliche Nachricht-
>>>>> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
>>>>> Gesendet: Sonntag, 22. Juli 2018 10:48
>>>>> An: Ant Developers List
>>>>> Betreff: Re: Jenkins-Builds failing
>>>>>
>>>>> Should we ask infra if nobody else knows about Jenkins authorization?
>>>>>
>>>>> Gintas
>>>>>
>>>>> On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm) 
>>>>> wrote:
>>>>>
>>>>>> Neither do I.
>>>>>>
>>>>>> Jan
>>>>>>
>>>>>>> -Ursprüngliche Nachricht-
>>>>>>> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
>>>>>>> Gesendet: Freitag, 20. Juli 2018 10:15
>>>>>>> An: dev@ant.apache.org
>>>>>>> Betreff: Re: Jenkins-Builds failing
>>>>>>>
>>>>>>> Now that I checked the job's logs, I think that's true. We had
>>>>>>> this issue in Ant too (not really against Maven repos, but HTTPS
>>>>>>> hosted Apache infrastructure). I tried setting that property in
>>>>>>> the job, but I too don't have the necessary authorization. I
>>>> don't
>>>>>>> remember if I ever had those permissions or if it's something
>>>> that
>>>>>>> changed with the recent Jenkins upgrade.
>>>>>>>
>>>>>>> -Jaikiran
>>>>>>>
>>>>>>>
>>>>>>> On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
>>>>>>>> My hypothesis is that Java 7 must have TLS version forced to
>>>> 1.2
>>>>>>>> in order to avoid protocol errors when downloading new binaries
>>>>>>>> from Maven Central because earlier versions are disabled [1]
>>>>>>>> (and TLS 1.0 is the default in Java 7).
>>>>>>>>
>>>>>>>> Gintas
>>>>>>>>
>>>>>>>> 1.
>>>>>>>> https://blog.pcisecuritystandards.org/are-you-ready-for-30-
>>>> june-
>>>>> 20
>>>>>>>> 18-
>>>>>>> s
>>>>>>>> ayin-goodbye-to-ssl-early-tls
>>>>>>>>
>>>>>>>> On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai
>>>>>>>> 
>>>>>>> wrote:
>>>>>>>>> Haven't checked the job, but why is this system property
>>>>> required
>>>>>>>>> to be set?
>>>>>>>>>
>>>>>>>>> -Jaikiran
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
>&g

Re: Jenkins-Builds failing

2018-07-24 Thread Gintautas Grigelionis

Thank you for all attempts, the failure occurs in run-tutorial macro
(forked JVM).
What would be the best way to forwarding Java arguments/system properties?

Gintas

On Tue, 24 Jul 2018 at 09:14, Gintautas Grigelionis 
wrote:

> It must be set as Java parameter, not Ant parameter.
>
> Gintas
>
> On Tue, 24 Jul 2018 at 08:38, Jan Matèrne (jhm)  wrote:
>
>> "Looks like someone called 'hibou' restricted the job to themselves. (See
>> screenshot attached to this ticket)"
>>
>> This was a "run as hibou" configuration.
>>
>> @Nicolas: What was the reason to add that? Is it required?
>>
>>
>> Gavin removed that part and I could add the https.protocols=TLSv1.2
>> parameter.
>> Job restarted.
>>
>>
>> Jan
>>
>>
>> > -Ursprüngliche Nachricht-
>> > Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
>> > Gesendet: Sonntag, 22. Juli 2018 12:54
>> > An: 'Ant Developers List'
>> > Betreff: AW: Jenkins-Builds failing
>> >
>> > Checked by myself that a PMC chair could do (AFAIK).
>> > Opened a ticket
>> > https://issues.apache.org/jira/browse/INFRA-16799
>> >
>> > Jan
>> >
>> > > -Ursprüngliche Nachricht-
>> > > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
>> > > Gesendet: Sonntag, 22. Juli 2018 10:48
>> > > An: Ant Developers List
>> > > Betreff: Re: Jenkins-Builds failing
>> > >
>> > > Should we ask infra if nobody else knows about Jenkins authorization?
>> > >
>> > > Gintas
>> > >
>> > > On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm) 
>> > > wrote:
>> > >
>> > > > Neither do I.
>> > > >
>> > > > Jan
>> > > >
>> > > > > -Ursprüngliche Nachricht-
>> > > > > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
>> > > > > Gesendet: Freitag, 20. Juli 2018 10:15
>> > > > > An: dev@ant.apache.org
>> > > > > Betreff: Re: Jenkins-Builds failing
>> > > > >
>> > > > > Now that I checked the job's logs, I think that's true. We had
>> > > > > this issue in Ant too (not really against Maven repos, but HTTPS
>> > > > > hosted Apache infrastructure). I tried setting that property in
>> > > > > the job, but I too don't have the necessary authorization. I
>> > don't
>> > > > > remember if I ever had those permissions or if it's something
>> > that
>> > > > > changed with the recent Jenkins upgrade.
>> > > > >
>> > > > > -Jaikiran
>> > > > >
>> > > > >
>> > > > > On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
>> > > > > > My hypothesis is that Java 7 must have TLS version forced to
>> > 1.2
>> > > > > > in order to avoid protocol errors when downloading new binaries
>> > > > > > from Maven Central because earlier versions are disabled [1]
>> > > > > > (and TLS 1.0 is the default in Java 7).
>> > > > > >
>> > > > > > Gintas
>> > > > > >
>> > > > > > 1.
>> > > > > > https://blog.pcisecuritystandards.org/are-you-ready-for-30-
>> > june-
>> > > 20
>> > > > > > 18-
>> > > > > s
>> > > > > > ayin-goodbye-to-ssl-early-tls
>> > > > > >
>> > > > > > On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai
>> > > > > > 
>> > > > > wrote:
>> > > > > >
>> > > > > >> Haven't checked the job, but why is this system property
>> > > required
>> > > > > >> to be set?
>> > > > > >>
>> > > > > >> -Jaikiran
>> > > > > >>
>> > > > > >>
>> > > > > >> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
>> > > > > >>> I'd like to add a Java option to Ivy builds
>> > > > > >>> -Dhttps.protocols=TLSv1.2
>> > > > > >> but I
>> > > > > >>> get
>> > > > > >>> This job's current authorization strategy does not permit
>> > >

Re: Jenkins-Builds failing

2018-07-24 Thread Gintautas Grigelionis

It must be set as Java parameter, not Ant parameter.

Gintas

On Tue, 24 Jul 2018 at 08:38, Jan Matèrne (jhm)  wrote:

> "Looks like someone called 'hibou' restricted the job to themselves. (See
> screenshot attached to this ticket)"
>
> This was a "run as hibou" configuration.
>
> @Nicolas: What was the reason to add that? Is it required?
>
>
> Gavin removed that part and I could add the https.protocols=TLSv1.2
> parameter.
> Job restarted.
>
>
> Jan
>
>
> > -Ursprüngliche Nachricht-
> > Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> > Gesendet: Sonntag, 22. Juli 2018 12:54
> > An: 'Ant Developers List'
> > Betreff: AW: Jenkins-Builds failing
> >
> > Checked by myself that a PMC chair could do (AFAIK).
> > Opened a ticket
> > https://issues.apache.org/jira/browse/INFRA-16799
> >
> > Jan
> >
> > > -Ursprüngliche Nachricht-
> > > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> > > Gesendet: Sonntag, 22. Juli 2018 10:48
> > > An: Ant Developers List
> > > Betreff: Re: Jenkins-Builds failing
> > >
> > > Should we ask infra if nobody else knows about Jenkins authorization?
> > >
> > > Gintas
> > >
> > > On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm) 
> > > wrote:
> > >
> > > > Neither do I.
> > > >
> > > > Jan
> > > >
> > > > > -Ursprüngliche Nachricht-
> > > > > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> > > > > Gesendet: Freitag, 20. Juli 2018 10:15
> > > > > An: dev@ant.apache.org
> > > > > Betreff: Re: Jenkins-Builds failing
> > > > >
> > > > > Now that I checked the job's logs, I think that's true. We had
> > > > > this issue in Ant too (not really against Maven repos, but HTTPS
> > > > > hosted Apache infrastructure). I tried setting that property in
> > > > > the job, but I too don't have the necessary authorization. I
> > don't
> > > > > remember if I ever had those permissions or if it's something
> > that
> > > > > changed with the recent Jenkins upgrade.
> > > > >
> > > > > -Jaikiran
> > > > >
> > > > >
> > > > > On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
> > > > > > My hypothesis is that Java 7 must have TLS version forced to
> > 1.2
> > > > > > in order to avoid protocol errors when downloading new binaries
> > > > > > from Maven Central because earlier versions are disabled [1]
> > > > > > (and TLS 1.0 is the default in Java 7).
> > > > > >
> > > > > > Gintas
> > > > > >
> > > > > > 1.
> > > > > > https://blog.pcisecuritystandards.org/are-you-ready-for-30-
> > june-
> > > 20
> > > > > > 18-
> > > > > s
> > > > > > ayin-goodbye-to-ssl-early-tls
> > > > > >
> > > > > > On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai
> > > > > > 
> > > > > wrote:
> > > > > >
> > > > > >> Haven't checked the job, but why is this system property
> > > required
> > > > > >> to be set?
> > > > > >>
> > > > > >> -Jaikiran
> > > > > >>
> > > > > >>
> > > > > >> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> > > > > >>> I'd like to add a Java option to Ivy builds
> > > > > >>> -Dhttps.protocols=TLSv1.2
> > > > > >> but I
> > > > > >>> get
> > > > > >>> This job's current authorization strategy does not permit
> > > gintas
> > > > > >>> to
> > > > > >> modify
> > > > > >>> the job configuration
> > > > > >>>
> > > > > >>> Gintas
> > > > > >>>
> > > > > >>> On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis <
> > > > > >> g.grigelio...@gmail.com>
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> Ant nightly is stuck on archiving for 30 hours now.
> > > > > >>>> It should be escalated, I beli

Re: Jenkins-Builds failing

2018-07-22 Thread Gintautas Grigelionis

Should we ask infra if nobody else knows about Jenkins authorization?

Gintas

On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm)  wrote:

> Neither do I.
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Freitag, 20. Juli 2018 10:15
> > An: dev@ant.apache.org
> > Betreff: Re: Jenkins-Builds failing
> >
> > Now that I checked the job's logs, I think that's true. We had this
> > issue in Ant too (not really against Maven repos, but HTTPS hosted
> > Apache infrastructure). I tried setting that property in the job, but I
> > too don't have the necessary authorization. I don't remember if I ever
> > had those permissions or if it's something that changed with the recent
> > Jenkins upgrade.
> >
> > -Jaikiran
> >
> >
> > On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
> > > My hypothesis is that Java 7 must have TLS version forced to 1.2 in
> > > order to avoid protocol errors when downloading new binaries from
> > > Maven Central because earlier versions are disabled [1] (and TLS 1.0
> > > is the default in Java 7).
> > >
> > > Gintas
> > >
> > > 1.
> > > https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-
> > s
> > > ayin-goodbye-to-ssl-early-tls
> > >
> > > On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai 
> > wrote:
> > >
> > >> Haven't checked the job, but why is this system property required to
> > >> be set?
> > >>
> > >> -Jaikiran
> > >>
> > >>
> > >> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> > >>> I'd like to add a Java option to Ivy builds
> > >>> -Dhttps.protocols=TLSv1.2
> > >> but I
> > >>> get
> > >>> This job's current authorization strategy does not permit gintas to
> > >> modify
> > >>> the job configuration
> > >>>
> > >>> Gintas
> > >>>
> > >>> On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis <
> > >> g.grigelio...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> Ant nightly is stuck on archiving for 30 hours now.
> > >>>> It should be escalated, I believe that could have something to do
> > >>>> with
> > >> the
> > >>>> last upgrade of Jenkins.
> > >>>>
> > >>>> Gintas
> > >>>>
> > >>>> On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:
> > >>>>
> > >>>>> Several of our Jenkins builds are failing:
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> IvyDE:
> > >>>>>
> > >>>>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
> > >>>>>
> > >>>>>
> > https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/cons
> > >>>>> ole
> > >>>>>
> > >>>>> Can't get
> > >>>>>
> > >>>>>
> > >> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-
> > 2
> > >> 0130208
> > >>>>> 151217/wtp4x-R-3.4.2-20130208151217.zip
> > >>>>> <
> > >> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-
> > 2
> > >> 0130208151217/wtp4x-R-3.4.2-20130208151217.zip
> > >>>>> to
> > >>>>>
> > >>>>>
> > >> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-
> > 3.4.
> > >> 2-20130
> > >>>>> 208151217.zip
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> The source URL gives a 404.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> AntLib - AntUnit
> > >>>>>
> > >>>>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
> > >>>>>
> > >>>>>
> > >>>>>
> > >> https://builds.apache.org/view/A/view/Ant/job/AntLib-
> > antunit/lastBuil
> > >> d/conso
> > >>>>> le
> > >>>>>
> > >>>>> [ivy:resolve]

Re: Jenkins-Builds failing

2018-07-20 Thread Jaikiran Pai

Now that I checked the job's logs, I think that's true. We had this
issue in Ant too (not really against Maven repos, but HTTPS hosted
Apache infrastructure). I tried setting that property in the job, but I
too don't have the necessary authorization. I don't remember if I ever
had those permissions or if it's something that changed with the recent
Jenkins upgrade.

-Jaikiran


On 20/07/18 1:34 PM, Gintautas Grigelionis wrote:
> My hypothesis is that Java 7 must have TLS version forced to 1.2 in order
> to avoid protocol errors when downloading new binaries from Maven Central
> because earlier versions are disabled [1] (and TLS 1.0 is the default in
> Java 7).
>
> Gintas
>
> 1.
> https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls
>
> On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai  wrote:
>
>> Haven't checked the job, but why is this system property required to be
>> set?
>>
>> -Jaikiran
>>
>>
>> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
>>> I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2
>> but I
>>> get
>>> This job's current authorization strategy does not permit gintas to
>> modify
>>> the job configuration
>>>
>>> Gintas
>>>
>>> On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis <
>> g.grigelio...@gmail.com>
>>> wrote:
>>>
 Ant nightly is stuck on archiving for 30 hours now.
 It should be escalated, I believe that could have something to do with
>> the
 last upgrade of Jenkins.

 Gintas

 On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:

> Several of our Jenkins builds are failing:
>
>
>
> IvyDE:
>
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
>
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
>
> Can't get
>
>
>> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208
> 151217/wtp4x-R-3.4.2-20130208151217.zip
> <
>> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208151217/wtp4x-R-3.4.2-20130208151217.zip
> to
>
>
>> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-3.4.2-20130
> 208151217.zip
>
>
>
> The source URL gives a 404.
>
>
>
>
>
> AntLib - AntUnit
>
> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
>
>
>
>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/lastBuild/conso
> le
>
> [ivy:resolve]   Server access error at url
>
>
>> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testuti
> l-1.8.1.pom
> <
>> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testutil-1.8.1.pom
> (javax.net.ssl.SSLException: Received fatal alert:
> protocol_version)
>
>
>
>
>
> AntLib - SVN
>
> same problem as for AU
>
>
>
>
>
> Ivy
>
> https://builds.apache.org/view/A/view/Ant/job/Ivy/
>
> https://builds.apache.org/view/A/view/Ant/job/Ivy/lastBuild/console
>
> same problem as for AU
>
>
>
>
>
> Ant Nightly
>
> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/
>
>
>
>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/lastBuild/console
> all runs fine, but "Archiving artifacts" requires lt of time …
>
>
>
>
>
> Ideas?
>
>
>
> Jan
>
>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
>> For additional commands, e-mail: dev-h...@ant.apache.org
>>
>>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-07-20 Thread Gintautas Grigelionis

My hypothesis is that Java 7 must have TLS version forced to 1.2 in order
to avoid protocol errors when downloading new binaries from Maven Central
because earlier versions are disabled [1] (and TLS 1.0 is the default in
Java 7).

Gintas

1.
https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls

On Fri, 20 Jul 2018 at 09:31, Jaikiran Pai  wrote:

> Haven't checked the job, but why is this system property required to be
> set?
>
> -Jaikiran
>
>
> On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> > I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2
> but I
> > get
> > This job's current authorization strategy does not permit gintas to
> modify
> > the job configuration
> >
> > Gintas
> >
> > On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis <
> g.grigelio...@gmail.com>
> > wrote:
> >
> >> Ant nightly is stuck on archiving for 30 hours now.
> >> It should be escalated, I believe that could have something to do with
> the
> >> last upgrade of Jenkins.
> >>
> >> Gintas
> >>
> >> On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:
> >>
> >>> Several of our Jenkins builds are failing:
> >>>
> >>>
> >>>
> >>> IvyDE:
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
> >>>
> >>> Can't get
> >>>
> >>>
> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208
> >>> 151217/wtp4x-R-3.4.2-20130208151217.zip
> >>> <
> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208151217/wtp4x-R-3.4.2-20130208151217.zip
> >
> >>> to
> >>>
> >>>
> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-3.4.2-20130
> >>> 208151217.zip
> >>>
> >>>
> >>>
> >>> The source URL gives a 404.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> AntLib - AntUnit
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
> >>>
> >>>
> >>>
> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/lastBuild/conso
> >>> le
> >>>
> >>> [ivy:resolve]   Server access error at url
> >>>
> >>>
> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testuti
> >>> l-1.8.1.pom
> >>> <
> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testutil-1.8.1.pom
> >
> >>> (javax.net.ssl.SSLException: Received fatal alert:
> >>> protocol_version)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> AntLib - SVN
> >>>
> >>> same problem as for AU
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Ivy
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/Ivy/
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/Ivy/lastBuild/console
> >>>
> >>> same problem as for AU
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Ant Nightly
> >>>
> >>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/
> >>>
> >>>
> >>>
> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/lastBuild/console
> >>>
> >>> all runs fine, but "Archiving artifacts" requires lt of time …
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Ideas?
> >>>
> >>>
> >>>
> >>> Jan
> >>>
> >>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins-Builds failing

2018-07-20 Thread Jaikiran Pai

Haven't checked the job, but why is this system property required to be set?

-Jaikiran


On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2 but I
> get
> This job's current authorization strategy does not permit gintas to modify
> the job configuration
>
> Gintas
>
> On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis 
> wrote:
>
>> Ant nightly is stuck on archiving for 30 hours now.
>> It should be escalated, I believe that could have something to do with the
>> last upgrade of Jenkins.
>>
>> Gintas
>>
>> On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:
>>
>>> Several of our Jenkins builds are failing:
>>>
>>>
>>>
>>> IvyDE:
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
>>>
>>> Can't get
>>>
>>> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208
>>> 151217/wtp4x-R-3.4.2-20130208151217.zip
>>> 
>>> to
>>>
>>> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-3.4.2-20130
>>> 208151217.zip
>>>
>>>
>>>
>>> The source URL gives a 404.
>>>
>>>
>>>
>>>
>>>
>>> AntLib - AntUnit
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
>>>
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/lastBuild/conso
>>> le
>>>
>>> [ivy:resolve]   Server access error at url
>>>
>>> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testuti
>>> l-1.8.1.pom
>>> 
>>> (javax.net.ssl.SSLException: Received fatal alert:
>>> protocol_version)
>>>
>>>
>>>
>>>
>>>
>>> AntLib - SVN
>>>
>>> same problem as for AU
>>>
>>>
>>>
>>>
>>>
>>> Ivy
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/Ivy/
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/Ivy/lastBuild/console
>>>
>>> same problem as for AU
>>>
>>>
>>>
>>>
>>>
>>> Ant Nightly
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/
>>>
>>>
>>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/lastBuild/console
>>>
>>> all runs fine, but "Archiving artifacts" requires lt of time …
>>>
>>>
>>>
>>>
>>>
>>> Ideas?
>>>
>>>
>>>
>>> Jan
>>>
>>>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Jenkins-Builds failing

2018-07-19 Thread Gintautas Grigelionis

I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2 but I
get
This job's current authorization strategy does not permit gintas to modify
the job configuration

Gintas

On Tue, 3 Jul 2018 at 19:09, Gintautas Grigelionis 
wrote:

> Ant nightly is stuck on archiving for 30 hours now.
> It should be escalated, I believe that could have something to do with the
> last upgrade of Jenkins.
>
> Gintas
>
> On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:
>
>> Several of our Jenkins builds are failing:
>>
>>
>>
>> IvyDE:
>>
>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
>>
>> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
>>
>> Can't get
>>
>> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208
>> 151217/wtp4x-R-3.4.2-20130208151217.zip
>> 
>> to
>>
>> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-3.4.2-20130
>> 208151217.zip
>>
>>
>>
>> The source URL gives a 404.
>>
>>
>>
>>
>>
>> AntLib - AntUnit
>>
>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
>>
>>
>> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/lastBuild/conso
>> le
>>
>> [ivy:resolve]   Server access error at url
>>
>> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testuti
>> l-1.8.1.pom
>> 
>> (javax.net.ssl.SSLException: Received fatal alert:
>> protocol_version)
>>
>>
>>
>>
>>
>> AntLib - SVN
>>
>> same problem as for AU
>>
>>
>>
>>
>>
>> Ivy
>>
>> https://builds.apache.org/view/A/view/Ant/job/Ivy/
>>
>> https://builds.apache.org/view/A/view/Ant/job/Ivy/lastBuild/console
>>
>> same problem as for AU
>>
>>
>>
>>
>>
>> Ant Nightly
>>
>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/
>>
>>
>> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/lastBuild/console
>>
>> all runs fine, but "Archiving artifacts" requires lt of time …
>>
>>
>>
>>
>>
>> Ideas?
>>
>>
>>
>> Jan
>>
>>

Re: Jenkins-Builds failing

2018-07-03 Thread Gintautas Grigelionis

Ant nightly is stuck on archiving for 30 hours now.
It should be escalated, I believe that could have something to do with the
last upgrade of Jenkins.

Gintas

On Mon, 2 Jul 2018 at 14:18, Jan Matèrne  wrote:

> Several of our Jenkins builds are failing:
>
>
>
> IvyDE:
>
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/
>
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
>
> Can't get
>
> http://download.eclipse.org/webtools/downloads/drops/R3.4.2/R-3.4.2-20130208
> 151217/wtp4x-R-3.4.2-20130208151217.zip
> 
> to
>
> /home/jenkins/jenkins-slave/workspace/IvyDE/dependencies/wtp4x-R-3.4.2-20130
> 208151217.zip
>
>
>
> The source URL gives a 404.
>
>
>
>
>
> AntLib - AntUnit
>
> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/
>
>
> https://builds.apache.org/view/A/view/Ant/job/AntLib-antunit/lastBuild/conso
> le
>
> [ivy:resolve]   Server access error at url
>
> https://repo1.maven.org/maven2/org/apache/ant/ant-testutil/1.8.1/ant-testuti
> l-1.8.1.pom
> 
> (javax.net.ssl.SSLException: Received fatal alert:
> protocol_version)
>
>
>
>
>
> AntLib - SVN
>
> same problem as for AU
>
>
>
>
>
> Ivy
>
> https://builds.apache.org/view/A/view/Ant/job/Ivy/
>
> https://builds.apache.org/view/A/view/Ant/job/Ivy/lastBuild/console
>
> same problem as for AU
>
>
>
>
>
> Ant Nightly
>
> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/
>
> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/lastBuild/console
>
> all runs fine, but "Archiving artifacts" requires lt of time …
>
>
>
>
>
> Ideas?
>
>
>
> Jan
>
>

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

Re: Jenkins-Builds failing

20 matches

Site Navigation

Mail list logo

Footer information