> >> 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]
&
;> -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
t; 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
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
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
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
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
- 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
&g
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 nobod
t;>> 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: Gi
t;>
>>>> 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---
> > Opened a ticket
>> > https://issues.apache.org/jira/browse/INFRA-16799
>> >
>> > Jan
>> >
>> > > -Ursprüngliche Nachricht-
>> > > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
>> > > Gesendet: Sonnt
pache.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: R
: 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 infras
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
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.
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
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
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:
>
>
20 matches
Mail list logo
