The jobs should be fixed now (regarding security settings).
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Sonntag, 2. September 2018 10:52
> An: Ant Developers List
> Betreff: Re: Jenkins-Builds failing
>
> I see that Ant 1.9.13
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/IN
otocols=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
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
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 A
