Re: Ant jenkins jobs

[Jaikiran Pai]

The Apache infra team have addressed this issue and I am now able to 
trigger the job runs.


-Jaikiran

On 12/06/24 10:55 am, Jaikiran Pai wrote:
It looks like something has changed with our Jenkins instance and I 
can no longer trigger Ant jobs - I don't see the "Build/Build with 
Parameters" link or any such link which allows you to trigger the job, 
even after I am successfully logged in.


Could one of you who previously used to trigger some of these jobs, 
please see if you are able to trigger one? My question to the infra 
team hasn't seen any response so far.


-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

Ant jenkins jobs

[Jaikiran Pai]

It looks like something has changed with our Jenkins instance and I can 
no longer trigger Ant jobs - I don't see the "Build/Build with 
Parameters" link or any such link which allows you to trigger the job, 
even after I am successfully logged in.


Could one of you who previously used to trigger some of these jobs, 
please see if you are able to trigger one? My question to the infra team 
hasn't seen any response so far.


-Jaikiran


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

Re: Jenkins build became unstable: Ant » Ant-Build-Matrix-master-Linux » ubuntu,jdk_1.8_latest #128

[Matt Benson]

Interesting, I'll have to have another look. Thanks Stefan!

Matt

On Sun, Mar 6, 2022, 6:38 AM Stefan Bodewig  wrote:

> On 2022-02-15, Matt Benson wrote:
>
> > So my tests for scriptcondition return values were using beanshell
> > because I couldn't figure out any way to get rhino to return a value
> > from the script. I can't understand which optional dependencies are
> > present during the build, where they are, nor how they get there. Are
> > they in the lib of the actual Ant installation used by Jenkins? Who
> > can help me with this?
>
> Sorry, I'm pretty ,uch restricted to weekends right now - or even less.
>
> AFAIK there the Ant installation does not come with any optional
> dependencies, but I may be wrong.
>
> This is what the build job definition for building master on Linux
> currently says:
>
> java -version && ./build.sh -f fetch.xml -Ddest=optional && ./bootstrap.sh
> && ./build.sh clean jars javadocs test
>
> so dependencies should be in lib/optional
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins build became unstable: Ant » Ant-Build-Matrix-master-Linux » ubuntu,jdk_1.8_latest #128

[Stefan Bodewig]

On 2022-02-15, Matt Benson wrote:

> So my tests for scriptcondition return values were using beanshell
> because I couldn't figure out any way to get rhino to return a value
> from the script. I can't understand which optional dependencies are
> present during the build, where they are, nor how they get there. Are
> they in the lib of the actual Ant installation used by Jenkins? Who
> can help me with this?

Sorry, I'm pretty ,uch restricted to weekends right now - or even less.

AFAIK there the Ant installation does not come with any optional
dependencies, but I may be wrong.

This is what the build job definition for building master on Linux
currently says:

java -version && ./build.sh -f fetch.xml -Ddest=optional && ./bootstrap.sh && 
./build.sh clean jars javadocs test

so dependencies should be in lib/optional

Stefan

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

Re: Jenkins build became unstable: Ant » Ant-Build-Matrix-master-Linux » ubuntu,jdk_1.8_latest #128

[Matt Benson]

So my tests for scriptcondition return values were using beanshell because
I couldn't figure out any way to get rhino to return a value from the
script. I can't understand which optional dependencies are present during
the build, where they are, nor how they get there. Are they in the lib of
the actual Ant installation used by Jenkins? Who can help me with this?

Matt

On Mon, Feb 14, 2022, 4:14 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-Matrix-master-Linux/OS=ubuntu,jdk=jdk_1.8_latest/128/display/redirect?page=changes
> >
>
>

Re: Build failed in Jenkins: Ant » Ant-Build-from-POMs #120

[Matt Benson]

I saw the Windows related failure and will fix it today.

Thanks,
Matt

On Wed, Feb 9, 2022, 11:16 PM Jaikiran Pai  wrote:

> Hello Matt,
>
> That job keeps failing every other time. I haven't had a chance to
> understand why it fails nor do I know what that job is for. I think you
> can ignore that specific job failure since it's not your commits which
> is causing it.
>
> The only failure that looks related to the recent commits is in a
> different job (on Windows) -
>
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-Matrix-master-Windows/OS=Windows,jdk=jdk_1.8_latest/120/testReport/src.tests.antunit.taskdefs/pathconvert-test_xml/testDirsep/
>
> -Jaikiran
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Build failed in Jenkins: Ant » Ant-Build-from-POMs #120

[Jaikiran Pai]

Hello Matt,

That job keeps failing every other time. I haven't had a chance to 
understand why it fails nor do I know what that job is for. I think you 
can ignore that specific job failure since it's not your commits which 
is causing it.


The only failure that looks related to the recent commits is in a 
different job (on Windows) - 
https://ci-builds.apache.org/job/Ant/job/Ant-Build-Matrix-master-Windows/OS=Windows,jdk=jdk_1.8_latest/120/testReport/src.tests.antunit.taskdefs/pathconvert-test_xml/testDirsep/


-Jaikiran


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

Re: Build failed in Jenkins: Ant » Ant-Build-from-POMs #120

[Matt Benson]

These failures don't seem to be related to my changes. Does anybody have
any idea about them?

Matt

On Wed, Feb 9, 2022, 1:37 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/120/display/redirect
> >
>
> Changes:
>
>
> --
> [...truncated 453.39 KB...]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
> ant-jdepend ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/target/ant-jdepend/classes
> >
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources
> (default-testResources) @ ant-jdepend ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/src/etc/poms/ant-jdepend/src/test/resources
> >
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> ant-jdepend ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/target/ant-jdepend/testcases
> >
> [INFO] <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/src/tests/junit/org/apache/tools/ant/taskdefs/optional/jdepend/JDependTest.java>:
> <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/src/tests/junit/org/apache/tools/ant/taskdefs/optional/jdepend/JDependTest.java>
> uses or overrides a deprecated API.
> [INFO] <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/src/tests/junit/org/apache/tools/ant/taskdefs/optional/jdepend/JDependTest.java>:
> Recompile with -Xlint:deprecation for details.
> [INFO]
> [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ ant-jdepend
> ---
> [INFO]
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.tools.ant.util.facade.ImplementationSpecificArgumentTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 0.078 s - in
> org.apache.tools.ant.util.facade.ImplementationSpecificArgumentTest
> [INFO] Running org.apache.tools.ant.util.facade.FacadeTaskHelperTest
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 0.001 s - in org.apache.tools.ant.util.facade.FacadeTaskHelperTest
> [INFO] Running org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 1.295 s - in org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
> [INFO] --- maven-jar-plugin:3.1.0:jar (default-jar) @ ant-jdepend ---
> [INFO] Building jar: <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/target/ant-jdepend/ant-jdepend-1.10.13-SNAPSHOT.jar
> >
> [INFO]
> [INFO] ---< org.apache.ant:ant-jmf
> >---
> [INFO] Building Apache Ant + JMF 1.10.13-SNAPSHOT
>  [19/27]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ant-jmf ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ant-jmf ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources to META-INF
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ ant-jmf
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/target/ant-jmf/classes
> >
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources
> (default-testResources) @ ant-jmf ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POMs/ws/src/etc/poms/ant-jmf/src/test/resources
> >
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> ant-jmf ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ ant-jmf ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:3.1.0:jar (default-jar) @ ant-jmf ---
> [INFO] Building jar: <
> https://ci-builds.apache.org/job/Ant/job/Ant-Build-from-POM

Re: [ant] branch master updated: Avoid connection refused errors by leaving some time between the gets, works locally lets see if it also works for jenkins

[Jaikiran Pai]

Hi Martijn,

You are right - these tests have been failing regularly with connection
refused issues on Jenkins. Your commit seems to have improved the
situation although, they still seem to fail once in a while like here
https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%201.8.0_121%20(unlimited%20security)%2064-bit%20Windows%20only,label_exp=Windows/894/testReport/junit/src.tests.antunit.taskdefs/get-test_xml/testTemporaryRedirect/

-Jaikiran

On 26/05/19 12:35 PM, j...@apache.org wrote:
> Hi all
>
> Sorry the patch also contains another change, yesterday I updated the
> get-test.xml to also use https to the extend possible, and I did
> "break" the test case following a redirect from http to https. After
> fixing this I immediately put a workaround in place for the connection
> refused errors we often get in the get-test and gunzip-test.
>
> Br Martijn
>
>
>
> On 26-05-19 08:46, j...@apache.org wrote:
>> This is an automated email from the ASF dual-hosted git repository.
>>
>> jkf pushed a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/ant.git
>>
>>
>> The following commit(s) were added to refs/heads/master by this push:
>>   new 9b4393b  Avoid connection refused errors by leaving some
>> time between the gets, works locally lets see if it also works for
>> jenkins
>> 9b4393b is described below
>>
>> commit 9b4393b85ca7acebd7b228ea5ee79e4aa7e810a8
>> Author: jkf 
>> AuthorDate: Sun May 26 08:46:09 2019 +0200
>>
>>  Avoid connection refused errors by leaving some time between the
>> gets, works locally lets see if it also works for jenkins
>> ---
>>   src/tests/antunit/taskdefs/get-test.xml    | 12 +++-
>>   src/tests/antunit/taskdefs/gunzip-test.xml |  2 ++
>>   2 files changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/src/tests/antunit/taskdefs/get-test.xml
>> b/src/tests/antunit/taskdefs/get-test.xml
>> index b6b5e11..2133321 100644
>> --- a/src/tests/antunit/taskdefs/get-test.xml
>> +++ b/src/tests/antunit/taskdefs/get-test.xml
>> @@ -20,12 +20,14 @@
>>     
>>       > value="https://ant.apache.org/webtest/gettest; />
>> +  > value="http://ant.apache.org/webtest/gettest/http-to-https.txt; />
>>       
>>   
>>     
>>       
>> +    
>>   
>>     
>>   
>> @@ -39,6 +41,7 @@
>>     
>>     
>> +  
>>     > dest="${output}/permanent.tmp"/>
>>   
>>     
>> @@ -52,6 +55,7 @@
>>   
>>     
>> +  
>>     
>>   
>>     
>> @@ -65,6 +69,7 @@
>>   
>>     
>> +  
>>     
>>   
>>     
>> @@ -78,6 +83,7 @@
>>   
>>     
>> +  
>>     
>>   
>>     
>> @@ -95,6 +101,7 @@
>>       
>> +  
>>     
>>     > dest="${output}/infinite.tmp"/>
>>   
>> @@ -102,6 +109,7 @@
>>       
>> +  
>>     
>>   https://ant.apache.org/index.html"/>
>>   https://ant.apache.org/faq.html"/>
>> @@ -111,6 +119,7 @@
>>   
>>       
>> +    
>>   
>>   
>>     
>> @@ -125,7 +134,8 @@
>>       
>> -    > dest="${output}/http-to-https-redirect.tmp"/>
>> +    
>> +    > dest="${output}/http-to-https-redirect.tmp"/>
>>   
>>   
>>     > resource="${output}/http-to-https-redirect.tmp" substring="hello
>> world"/>
>> diff --git a/src/tests/antunit/taskdefs/gunzip-test.xml
>> b/src/tests/antunit/taskdefs/gunzip-test.xml
>> index f8ec6d9..19ca0ce 100644
>> --- a/src/tests/antunit/taskdefs/gunzip-test.xml
>> +++ b/src/tests/antunit/taskdefs/gunzip-test.xml
>> @@ -39,6 +39,7 @@
>>     
>>       
>> +    
>>   
>>     > url="https://ant.apache.org/webtest/gunzip/greeting.txt.gz"/>
>>   
>> @@ -49,6 +50,7 @@
>>     
>>       
>> +    
>>   
>>     > url="https://ant.apache.org/webtest/gunzip/greeting.txt.gz"/>
>>   
>>
>
> -
> 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: [ant] branch master updated: Avoid connection refused errors by leaving some time between the gets, works locally lets see if it also works for jenkins

[jkf]

Hi all

Sorry the patch also contains another change, yesterday I updated the 
get-test.xml to also use https to the extend possible, and I did "break" 
the test case following a redirect from http to https. After fixing this 
I immediately put a workaround in place for the connection refused 
errors we often get in the get-test and gunzip-test.


Br Martijn



On 26-05-19 08:46, j...@apache.org wrote:

This is an automated email from the ASF dual-hosted git repository.

jkf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant.git


The following commit(s) were added to refs/heads/master by this push:
  new 9b4393b  Avoid connection refused errors by leaving some time between 
the gets, works locally lets see if it also works for jenkins
9b4393b is described below

commit 9b4393b85ca7acebd7b228ea5ee79e4aa7e810a8
Author: jkf 
AuthorDate: Sun May 26 08:46:09 2019 +0200

 Avoid connection refused errors by leaving some time between the gets, 
works locally lets see if it also works for jenkins
---
  src/tests/antunit/taskdefs/get-test.xml| 12 +++-
  src/tests/antunit/taskdefs/gunzip-test.xml |  2 ++
  2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/src/tests/antunit/taskdefs/get-test.xml 
b/src/tests/antunit/taskdefs/get-test.xml
index b6b5e11..2133321 100644
--- a/src/tests/antunit/taskdefs/get-test.xml
+++ b/src/tests/antunit/taskdefs/get-test.xml
@@ -20,12 +20,14 @@

  
https://ant.apache.org/webtest/gettest; />

+  http://ant.apache.org/webtest/gettest/http-to-https.txt; />
  


  

  


+
  

  
@@ -39,6 +41,7 @@

  
  

+  

  

@@ -52,6 +55,7 @@
  
  
  

+  

  

@@ -65,6 +69,7 @@
  
  
  

+  

  

@@ -78,6 +83,7 @@
  
  
  

+  

  

@@ -95,6 +101,7 @@
  
  
  

+  


  
@@ -102,6 +109,7 @@
  
  
  

+  

  https://ant.apache.org/index.html"/>
  https://ant.apache.org/faq.html"/>
@@ -111,6 +119,7 @@
  
  


+
  
  

@@ -125,7 +134,8 @@
  

  from HTTP to HTTPS works without an error. See bugzilla-62499 for 
details">
-
+
+
  
  

diff --git a/src/tests/antunit/taskdefs/gunzip-test.xml 
b/src/tests/antunit/taskdefs/gunzip-test.xml
index f8ec6d9..19ca0ce 100644
--- a/src/tests/antunit/taskdefs/gunzip-test.xml
+++ b/src/tests/antunit/taskdefs/gunzip-test.xml
@@ -39,6 +39,7 @@

  


+
  
https://ant.apache.org/webtest/gunzip/greeting.txt.gz"/>
  
@@ -49,6 +50,7 @@

  


+
  
https://ant.apache.org/webtest/gunzip/greeting.txt.gz"/>
  



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

AW: Jenkins-Builds failing

[jhm]

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 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
> >
> >


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

Re: Jenkins-Builds failing

[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: Build failed in Jenkins: Ant-Build-Matrix-master-Windows » JDK 10 b46 (Windows Only),Windows #771

[Jaikiran Pai]

I am going to disable this JDK 10 b46 against Windows job. It's been
failing for a while and all due to infrastructure issues. I don't see
any other JDK 10 (Windows) selection option either. Any objections to
disabling these tests against this version, on Windows?

-Jaikiran

On 27/08/18 5:59 PM, Apache Jenkins Server wrote:
> See 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/771/display/redirect>
>
> --
> Started by upstream project "Ant-Build-Matrix-master-Windows" build number 771
> originally caused by:
>  Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on windows-2016-1 (Windows) in workspace 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/>
> [WS-CLEANUP] Deleting project workspace...
> ERROR: [WS-CLEANUP] Cannot delete workspace: remote file operation failed: 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/>
>  at hudson.remoting.Channel@1c74f1c0:JNLP4-connect connection from 
> ec2-34-228-168-168.compute-1.amazonaws.com/34.228.168.168:57603: 
> java.nio.file.AccessDeniedException: 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/>
>  -> 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/_ws-cleanup_1535372992775>
> ERROR: Cannot delete workspace: remote file operation failed: 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/>
>  at hudson.remoting.Channel@1c74f1c0:JNLP4-connect connection from 
> ec2-34-228-168-168.compute-1.amazonaws.com/34.228.168.168:57603: 
> java.nio.file.AccessDeniedException: 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/>
>  -> 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/_ws-cleanup_1535372992775>
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: Test reports were 
> found but none of them are new. Did leafNodes run? 
> For example, 
> <https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%2010%20b46%20(Windows%20Only),label_exp=Windows/ws/build\antunit\xml\TEST-src.tests.antunit.bugfixes.br50866.br50866-test_xml.xml>
>  is 1 mo 12 days old
>


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

Re: Build failed in Jenkins: Ivy-tests-ubuntu » ubuntu,JDK 1.7 (latest) #360

[Maarten Coene]

And the ModuleDescriptorMemoryCacheTest failure must be my fault.
I'll look into it later this week or next week.

Maarten

  Van: Jaikiran Pai 
 Aan: Ant Developers List  
 Verzonden: vrijdag 24 augustus 9:02 2018
 Onderwerp: Re: Build failed in Jenkins: Ivy-tests-ubuntu » ubuntu,JDK 1.7 
(latest) #360
   
More of a FYI - The URLResolverTest failures, in this list, appear to be
my fault, introduced in a commit I pushed this week. I will take a look
tonight to see what the issue there is and fix (or rollback) my changes.

-Jaikiran


On 24/08/18 12:22 PM, Apache Jenkins Server wrote:
> See 
> <https://builds.apache.org/job/Ivy-tests-ubuntu/OS=ubuntu,jdk=JDK%201.7%20(latest)/360/display/redirect?page=changes>
>
> Changes:
>
> [maartenc] FIX: ModuleDescriptorMemoryCache didn't detect outdated entries 
> when Ivy
>
> --
> [...truncated 32.16 KB...]
>    [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,962 sec
>    [junit] Running org.apache.ivy.ant.IvyCleanCacheTest
>    [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,552 sec
>    [junit] Running org.apache.ivy.ant.IvyConfigureTest
>    [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,596 sec
>    [junit] Running org.apache.ivy.ant.IvyConvertPomTest
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,937 sec
>    [junit] Running org.apache.ivy.ant.IvyDeliverTest
>    [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>4,205 sec
>    [junit] Running org.apache.ivy.ant.IvyDependencyTreeTest
>    [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,566 sec
>    [junit] Running org.apache.ivy.ant.IvyDependencyUpdateCheckerTest
>    [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,926 sec
>    [junit] Running org.apache.ivy.ant.IvyFindRevisionTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,868 sec
>    [junit] Running org.apache.ivy.ant.IvyInfoRepositoryTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,778 sec
>    [junit] Running org.apache.ivy.ant.IvyInfoTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,749 sec
>    [junit] Running org.apache.ivy.ant.IvyInstallTest
>    [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,384 sec
>    [junit] Running org.apache.ivy.ant.IvyListModulesTest
>    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,618 sec
>    [junit] Running org.apache.ivy.ant.IvyPostResolveTaskTest
>    [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,92 sec
>    [junit] Running org.apache.ivy.ant.IvyPublishTest
>    [junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>4,851 sec
>    [junit] Running org.apache.ivy.ant.IvyReportTest
>    [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,306 sec
>    [junit] Running org.apache.ivy.ant.IvyRepositoryReportTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,284 sec
>    [junit] Running org.apache.ivy.ant.IvyResolveTest
>    [junit] Tests run: 35, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
>4,11 sec
>    [junit] Running org.apache.ivy.ant.IvyResourcesTest
>    [junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,492 sec
>    [junit] Running org.apache.ivy.ant.IvyRetrieveBuildFileTest
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,295 sec
>    [junit] Running org.apache.ivy.ant.IvyRetrieveTest
>    [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,52 sec
>    [junit] Running org.apache.ivy.ant.IvyTaskTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,524 sec
>    [junit] Running org.apache.ivy.ant.IvyVarTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,602 sec
>    [junit] Running org.apache.ivy.core.NormalRelativeUrlResolverTest
>    [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>0,324 sec
>    [junit] Running org.apache.ivy.core.cache.DefaultRepositoryCacheManagerTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
>1,011 sec
>    [junit] Running org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest
>    [junit] Tests run: 10, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 
>1,004 sec
>    [junit] Test org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest 
>FAILED
>    [junit] Running org.apache.ivy.core.deliver.DeliverTe

Re: Build failed in Jenkins: Ivy-tests-ubuntu » ubuntu,JDK 1.7 (latest) #360

[Jaikiran Pai]

More of a FYI - The URLResolverTest failures, in this list, appear to be
my fault, introduced in a commit I pushed this week. I will take a look
tonight to see what the issue there is and fix (or rollback) my changes.

-Jaikiran


On 24/08/18 12:22 PM, Apache Jenkins Server wrote:
> See 
> <https://builds.apache.org/job/Ivy-tests-ubuntu/OS=ubuntu,jdk=JDK%201.7%20(latest)/360/display/redirect?page=changes>
>
> Changes:
>
> [maartenc] FIX: ModuleDescriptorMemoryCache didn't detect outdated entries 
> when Ivy
>
> --
> [...truncated 32.16 KB...]
> [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,962 sec
> [junit] Running org.apache.ivy.ant.IvyCleanCacheTest
> [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,552 sec
> [junit] Running org.apache.ivy.ant.IvyConfigureTest
> [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,596 sec
> [junit] Running org.apache.ivy.ant.IvyConvertPomTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,937 sec
> [junit] Running org.apache.ivy.ant.IvyDeliverTest
> [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 4,205 sec
> [junit] Running org.apache.ivy.ant.IvyDependencyTreeTest
> [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,566 sec
> [junit] Running org.apache.ivy.ant.IvyDependencyUpdateCheckerTest
> [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,926 sec
> [junit] Running org.apache.ivy.ant.IvyFindRevisionTest
> [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,868 sec
> [junit] Running org.apache.ivy.ant.IvyInfoRepositoryTest
> [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,778 sec
> [junit] Running org.apache.ivy.ant.IvyInfoTest
> [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,749 sec
> [junit] Running org.apache.ivy.ant.IvyInstallTest
> [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 3,384 sec
> [junit] Running org.apache.ivy.ant.IvyListModulesTest
> [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,618 sec
> [junit] Running org.apache.ivy.ant.IvyPostResolveTaskTest
> [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,92 sec
> [junit] Running org.apache.ivy.ant.IvyPublishTest
> [junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 4,851 sec
> [junit] Running org.apache.ivy.ant.IvyReportTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 3,306 sec
> [junit] Running org.apache.ivy.ant.IvyRepositoryReportTest
> [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,284 sec
> [junit] Running org.apache.ivy.ant.IvyResolveTest
> [junit] Tests run: 35, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
> 4,11 sec
> [junit] Running org.apache.ivy.ant.IvyResourcesTest
> [junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,492 sec
> [junit] Running org.apache.ivy.ant.IvyRetrieveBuildFileTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,295 sec
> [junit] Running org.apache.ivy.ant.IvyRetrieveTest
> [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 3,52 sec
> [junit] Running org.apache.ivy.ant.IvyTaskTest
> [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,524 sec
> [junit] Running org.apache.ivy.ant.IvyVarTest
> [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,602 sec
> [junit] Running org.apache.ivy.core.NormalRelativeUrlResolverTest
> [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 0,324 sec
> [junit] Running 
> org.apache.ivy.core.cache.DefaultRepositoryCacheManagerTest
> [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
> 1,011 sec
> [junit] Running org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest
> [junit] Tests run: 10, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 
> 1,004 sec
> [junit] Test org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest 
> FAILED
> [junit] Running org.apache.ivy.core.deliver.DeliverTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 2,105 sec
> [junit] Running org.apache.ivy.core.event.IvyEventFilterTest
> [junit] Tests run: 5, Failures: 0, Errors: 0, Skip

Re: Jenkins-Builds failing

[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

[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
>
>

AW: Jenkins-Builds failing

[jhm]

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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

AW: Jenkins-Builds failing

[jhm]

"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 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:
> &g

AW: Jenkins-Builds failing

[jhm]

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
> > > >> 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
> > > >>>>>
> > > >

Re: Jenkins-Builds failing

[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] 

AW: Jenkins-Builds failing

[jhm]

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]   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/consol
> >>>>> e
> >>>>>
> >>>>> 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/c
> >> onsole
> >>>>> 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



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

Re: Jenkins-Builds failing

[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

[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

[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
>>> <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

[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
>> <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
>>
>>

Re: Jenkins-Builds failing

[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
> <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
>
>

Jenkins-Builds failing

[Jan Matèrne]

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: AntUnit Bug Causing Jenkins Failures

[Jaikiran Pai]

Sounds fine to me.

-Jaikiran


On 04/06/18 1:08 PM, Stefan Bodewig wrote:

Hi all

one of the recurring issues that make Jenkins builds fail is a
thread-safety bug in AntUnit's log capturing code. This is supposed to
be fixed in AntUnit's master branch.

I propose to build an alpha version of AntUnit and push that to Ant's
lib/optional - and then monitor Jenkins for a while validating the
fix. And if it seems to work, cut a new AntUnit release.

This would break build jobs that try to populate lib/optional from
existing repos (either via fetch.xml or Ivy or whatever) until the next
AntUnit release has been published. I am not aware of any such CI job
but thought it would be good to ask before going forward.

Stefan

-
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: signjar-test failures in Jenkins

[Stefan Bodewig]

On 2018-03-20, Stefan Bodewig wrote:

> it looks as if I had broken every single Jenkins build. Of course the
> test pass on my machine with all JDKs I've got installed.

No, it fails on Java10 for me, because jarsigner -verify now dies for a
self-signed certificate. I'll try to figure out when this changed and if
there is a way to get the test to pass.

Stefan

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

signjar-test failures in Jenkins

[Stefan Bodewig]

Hi all

it looks as if I had broken every single Jenkins build. Of course the
test pass on my machine with all JDKs I've got installed.

Can anybody who gets test errors in his/her local environment please run

./build.sh -f src/tests/antunit/taskdefs/signjar-test.xml 
testVerifyJarStrictPKCS12 -v

and post the results? AntUnit's "jarsigner returned 1" is not really
helpful for me right now :-)

Stefan

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

Re: AW: Ant nightly Jenkins job

[Jaikiran Pai]

This is now done. The Ant_Nightly job now generates the Ant distribution 
which can be used for testing the bug fixes/features that go into the 
"master" branch. The distribution is available at 
https://builds.apache.org/job/Ant_Nightly/lastSuccessfulBuild/artifact/distribution/


-Jaikiran


On 01/03/18 6:54 PM, Jan Matèrne (jhm) wrote:

sure
Jan


-Ursprüngliche Nachricht-
Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
Gesendet: Donnerstag, 1. März 2018 12:50
An: Ant Developers List
Betreff: Ant nightly Jenkins job

Would it be OK if I redo the Ant nightly jenkins job[1] to be a bit
more useful and publish an actual nightly binary, for users to try out
if they wish to?

[1] https://builds.apache.org/job/Ant_Nightly/

-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

Ant nightly Jenkins job

[Jaikiran Pai]

Would it be OK if I redo the Ant nightly jenkins job[1] to be a bit more 
useful and publish an actual nightly binary, for users to try out if 
they wish to?


[1] https://builds.apache.org/job/Ant_Nightly/

-Jaikiran


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

AW: Ant Nightly Build Job in Jenkins

[jhm]

https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly/configure means:
ant -f launch-build.xml -Ddistribution
ant -f check.xml rat dumphtml simiancheck
where dumphtml=checkstyle+htmlreport


Haven't done a deep check what the SonarQube checks.
I think similarity checks could be included, but RAT checks are missing.
I don't think that RAT could be included in the SonarQube at the moment.


Jan

> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Sonntag, 28. Januar 2018 13:03
> An: dev@ant.apache.org
> Betreff: Re: Ant Nightly Build Job in Jenkins
> 
> On 2018-01-28, Stefan Bodewig wrote:
> 
> > On 2018-01-28, Jan Matèrne (jhm) wrote:
> 
> >> Updated the target to use actual 2.5.8.  But there is still a
> problem
> >> when using two formatters, so I commented the txt-formatter out.
> 
> BTW, does this build run any tools that are not also part of the
> SonarQube build?
> 
> Stefan
> 
> -
> 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: Ant Nightly Build Job in Jenkins

[Stefan Bodewig]

On 2018-01-28, Stefan Bodewig wrote:

> On 2018-01-28, Jan Matèrne (jhm) wrote:

>> Updated the target to use actual 2.5.8.  But there is still a problem
>> when using two formatters, so I commented the txt-formatter out.

BTW, does this build run any tools that are not also part of the
SonarQube build?

Stefan

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

Re: Ant Nightly Build Job in Jenkins

[Stefan Bodewig]

On 2018-01-28, Jan Matèrne (jhm) wrote:

> Updated the target to use actual 2.5.8.  But there is still a problem
> when using two formatters, so I commented the txt-formatter out.

Thanks!

Stefan

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

AW: Ant Nightly Build Job in Jenkins

[jhm]

Updated the target to use actual 2.5.8.
But there is still a problem when using two formatters, so I commented the 
txt-formatter out.

Jan

> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Samstag, 27. Januar 2018 19:16
> An: Ant Developers List
> Betreff: Re: Ant Nightly Build Job in Jenkins
> 
> Simian stands for "similarity analysis" and is supposed to check for
> copy-paste code duplications.
> 
> I guess the older versions of simian disapper from the site as new
> versions are released. Currently, 2.5.8 is the latest version.
> There should be no harm updating to the latest version, ditto for
> checkstyle (Ivy project uses version 7, since version 8 as resolved by
> Ivy fails, and I did not have time to investigate what causes that yet)
> and findbugs.
> 
> Gintas
> 
> 
> 
> 2018-01-27 18:53 GMT+01:00 Stefan Bodewig <bode...@apache.org>:
> 
> > Hi all
> >
> > is anybody familiar with the things we try to do with the job called
> > "Ant Nightly"? It has been failing for months now and the reason is
> > not Ant but the build process which tries to download a
> > "simian-2.4.0.tar.gz" that simply doesn't exist at the expected URI.
> >
> > Stefan
> >
> > -
> > 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: Ant Nightly Build Job in Jenkins

[Gintautas Grigelionis]

Simian stands for "similarity analysis" and is supposed to check for
copy-paste code duplications.

I guess the older versions of simian disapper from the site as new versions
are released. Currently, 2.5.8 is the latest version.
There should be no harm updating to the latest version, ditto for
checkstyle (Ivy project uses version 7, since version 8 as resolved by Ivy
fails,
and I did not have time to investigate what causes that yet) and findbugs.

Gintas



2018-01-27 18:53 GMT+01:00 Stefan Bodewig :

> Hi all
>
> is anybody familiar with the things we try to do with the job called
> "Ant Nightly"? It has been failing for months now and the reason is not
> Ant but the build process which tries to download a
> "simian-2.4.0.tar.gz" that simply doesn't exist at the expected URI.
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Stefan Bodewig]

Strangely the test passes when I run it manually on the VM running
Gump. I'll look into it further but am running out of time for now.

Stefan

On 2017-12-13, Jaikiran Pai wrote:

> Do let me know if there's anything I can do to help investigate
> this. I'm curious myself to see what's causing this.

> -Jaikiran


> On 13/12/17 2:56 AM, Stefan Bodewig wrote:
>> On 2017-12-12, Stefan Bodewig wrote:

>>> On 2017-12-12, Jaikiran Pai wrote:
>>>> So the one final test that's still failing is this one[1]. It's
>>>> failing consistently only on Jenkins, that too with only Java 8
>>>> (jdk1.8.0_131). I have tried reproducing that one locally with that
>>>> exact Java version and even the latest Java 8 and haven't been able to
>>>> reproduce it. Before I try and debug this on that Jenkins environment
>>>> (which doesn't seem to be easy to do), I would like to know if this is
>>>> reproducible for anyone else.
>>> No, I haven't been able either.
>> it also fails in Gump:
>> http://vmgump-vm3.apache.org/ant/test-ant/gump_work/build_ant_test-ant.txt

>> I have got shell access to vmgump-vm3 and will try to find some time
>> understanding the error in the comming days.

>> Stefan

>> -
>> 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: Build failed in Jenkins: Ant-Build-Matrix-1.9.x-Linux » JDK 1.6 (latest) #134

[Jaikiran Pai]

It's back to normal [1], so the crash seems to be specific to certain 
nodes on Jenkins, for Java 6. I don't plan to look more into this.


[1] 
https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/135/


-Jaikiran


On 13/12/17 8:40 PM, Jaikiran Pai wrote:


So we have now had 2 runs of this job failing with a JVM crash:

Run 133
[exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gunzip-test.xml>
  [exec] [au:antunit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 
0.804 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToDir took 0.462 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToFile took 0.305 sec
  [exec] [au:antunit] Target: testWithFileResourceToFile took 0.018 sec
  [exec] [au:antunit] Target: testWithFileResourceToDirectory took 0.003 sec
  [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gzip-test.xml>
*[exec] *** Error in `/home/jenkins/tools/java/latest1.6/jre/bin/java': 
free(): invalid next size (fast): 0x7f90ec35b630 *** *  [exec] [au:antunit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.01 sec

  [exec] [au:antunit] Target: testFailNone took 0.003 sec
  [exec] [au:antunit] Target: testFailTwo took 0.001 sec
  [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/hostinfo-test.xml>
and run 134

See<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/134/display/redirect>

--
[...truncated 101.33 KB...]
  
  [exec] [au:antunit] Build File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gunzip-test.xml>

  [exec] [au:antunit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 
0.087 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToDir took 0.041 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToFile took 0.028 sec
  [exec] [au:antunit] Target: testWithFileResourceToFile took 0.002 sec
  [exec] [au:antunit] Target: testWithFileResourceToDirectory took 0.001 sec
  [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gzip-test.xml>
  [exec] [au:antunit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 
0.01 sec
  [exec] [au:antunit] Target: testFailNone took 0.003 sec
  [exec] [au:antunit] Target: testFailTwo took 0.001 sec
  [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/hostinfo-test.xml>
  *[exec] *** Error in 
`/home/jenkins/tools/java/latest1.6/jre/bin/java': malloc(): memory 
corruption: 0x7f57b0325620 

  [exec] Aborted



both seem to have happened when the gzip antunit test was in 
progress/ended. Plus, I just committed a Zip class related change to 
this branch[1]. So most likely _not_ a coincidence. But given this a 
JVM crash (in Java 6), it most likely is a JVM issue. I'll see if I 
can find something on this, before we decide if at all we need to 
rollback that commit.


[1] 
https://github.com/apache/ant/commit/0fd2a86369aab41db316b1064a559bae08afae0f


-Jaikiran

Re: Github ant repo now integrated with Jenkins for pull request testing

[Jaikiran Pai]

On 12/12/17 8:05 PM, Jaikiran Pai wrote:



The next few days, I'll probably try and see if I can get a Linux 
based job to run alongside this Windows job for PRs.
We now have a Linux one too for the PRs 
https://builds.apache.org/job/Ant%20Github-PR-Linux/. It has the same 
characteristics as the Windows one, except that this one runs on Linux.


-Jaikiran

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

Re: Build failed in Jenkins: Ant-Build-Matrix-1.9.x-Linux » JDK 1.6 (latest) #134

[Jaikiran Pai]

So we have now had 2 runs of this job failing with a JVM crash:

Run 133

[exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gunzip-test.xml>
 [exec] [au:antunit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 
0.804 sec
 [exec] [au:antunit] Target: testWithNonFileResourceToDir took 0.462 sec
 [exec] [au:antunit] Target: testWithNonFileResourceToFile took 0.305 sec
 [exec] [au:antunit] Target: testWithFileResourceToFile took 0.018 sec
 [exec] [au:antunit] Target: testWithFileResourceToDirectory took 0.003 sec
 [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gzip-test.xml>
*[exec] *** Error in `/home/jenkins/tools/java/latest1.6/jre/bin/java': 
free(): invalid next size (fast): 0x7f90ec35b630 *** *  [exec] [au:antunit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.01 sec

 [exec] [au:antunit] Target: testFailNone took 0.003 sec
 [exec] [au:antunit] Target: testFailTwo took 0.001 sec
 [exec] [au:antunit] Build 
File:<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/hostinfo-test.xml>

and run 134

See 
<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/134/display/redirect>

--
[...truncated 101.33 KB...]
  
  [exec] [au:antunit] Build File: <https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gunzip-test.xml>

  [exec] [au:antunit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 
0.087 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToDir took 0.041 sec
  [exec] [au:antunit] Target: testWithNonFileResourceToFile took 0.028 sec
  [exec] [au:antunit] Target: testWithFileResourceToFile took 0.002 sec
  [exec] [au:antunit] Target: testWithFileResourceToDirectory took 0.001 sec
  [exec] [au:antunit] Build File: 
<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/gzip-test.xml>
  [exec] [au:antunit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 
0.01 sec
  [exec] [au:antunit] Target: testFailNone took 0.003 sec
  [exec] [au:antunit] Target: testFailTwo took 0.001 sec
  [exec] [au:antunit] Build File: 
<https://builds.apache.org/job/Ant-Build-Matrix-1.9.x-Linux/jdk=JDK%201.6%20(latest)/ws/src/tests/antunit/taskdefs/hostinfo-test.xml>
  *[exec] *** Error in `/home/jenkins/tools/java/latest1.6/jre/bin/java': 
malloc(): memory corruption: 0x7f57b0325620 

  [exec] Aborted



both seem to have happened when the gzip antunit test was in 
progress/ended. Plus, I just committed a Zip class related change to 
this branch[1]. So most likely _not_ a coincidence. But given this a JVM 
crash (in Java 6), it most likely is a JVM issue. I'll see if I can find 
something on this, before we decide if at all we need to rollback that 
commit.


[1] 
https://github.com/apache/ant/commit/0fd2a86369aab41db316b1064a559bae08afae0f


-Jaikiran

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Jaikiran Pai]

Do let me know if there's anything I can do to help investigate this. 
I'm curious myself to see what's causing this.


-Jaikiran


On 13/12/17 2:56 AM, Stefan Bodewig wrote:

On 2017-12-12, Stefan Bodewig wrote:


On 2017-12-12, Jaikiran Pai wrote:

So the one final test that's still failing is this one[1]. It's
failing consistently only on Jenkins, that too with only Java 8
(jdk1.8.0_131). I have tried reproducing that one locally with that
exact Java version and even the latest Java 8 and haven't been able to
reproduce it. Before I try and debug this on that Jenkins environment
(which doesn't seem to be easy to do), I would like to know if this is
reproducible for anyone else.

No, I haven't been able either.

it also fails in Gump:
http://vmgump-vm3.apache.org/ant/test-ant/gump_work/build_ant_test-ant.txt

I have got shell access to vmgump-vm3 and will try to find some time
understanding the error in the comming days.

Stefan

-
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 build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Stefan Bodewig]

On 2017-12-12, Stefan Bodewig wrote:

> On 2017-12-12, Jaikiran Pai wrote:

>> So the one final test that's still failing is this one[1]. It's
>> failing consistently only on Jenkins, that too with only Java 8
>> (jdk1.8.0_131). I have tried reproducing that one locally with that
>> exact Java version and even the latest Java 8 and haven't been able to
>> reproduce it. Before I try and debug this on that Jenkins environment
>> (which doesn't seem to be easy to do), I would like to know if this is
>> reproducible for anyone else.

> No, I haven't been able either.

it also fails in Gump:
http://vmgump-vm3.apache.org/ant/test-ant/gump_work/build_ant_test-ant.txt

I have got shell access to vmgump-vm3 and will try to find some time
understanding the error in the comming days.

Stefan

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

Github ant repo now integrated with Jenkins for pull request testing

[Jaikiran Pai]

We now have integrated our Jenkins build environment hosted by 
apache.org with our Ant github repo[1], such that whenever a pull 
request is submitted, it now triggers a build and runs tests against the 
submitted pull request and then comments/adds a status to the PR on how 
the build went. This is going to help us in doing some basic 
verification of the changes that's being proposed in the PR.


The job resides at [2]. Few details about this job:

1. The goal of this job is to run tests against the PR. It doesn't 
produce any binaries. Furthermore, unlike the Ant Matrix builds, this 
one does _not_ run against all possible combinations of JDK/OS.


2. This job has been configured to be run against Windows (for now). I 
decided to use Windows since that's the one where we usually run into 
issues and not many of us Ant developers are on Windows. I _might_ add 
another job for the PRs which tests against Linux, but I'm not sure if 
there's a easy way to do that. So for now, it's going to be just Windows.


3. This job uses Java 8 runtime to compile and run the tests, 
irrespective of which branch the PR is submitted against. What this 
means is even if you submit this PR against 1.9.x branch of Ant, the 
minimum compatible Java version of which is Java 5, this job will still 
use Java 8 to both compile and run the job. This means, it may not be 
able to catch certain (compilation or other) issues. I did not find a 
way to conditionally choose a JDK version for the job nor did I find a 
way to conditionally choose a job for a PR (based on what branch it is 
submitted). So we will have to do with this, till we support multiple 
branches. However, given that this is just for basic testing and there 
will be PR reviewers to actually do the review and then another round of 
tests that get triggered when the PR is merged, I'm not too worried 
about this constraint for now.


4. Finally, the regular Ant Matrix builds are unchanged and will 
continue to build after commits are pushed to relevant branches to the 
Ant upstream repo. Those jobs will remain unaffected by this change.


5. A very minor detail - I have intentionally named the job with a space 
character in its name so that the checkout location too will contain 
that space in the directory path (Jenkins uses the project name to 
create directories for the checked out job). This will allow us to catch 
certain issues we typically have with URI parsing and such. But that's 
just a minor detail and doesn't have anything to do with the PR 
integration itself.


The next few days, I'll probably try and see if I can get a Linux based 
job to run alongside this Windows job for PRs.


One other thing - unlike the similar integration we have for Ant Ivy 
job/repo, this one is much more advanced (in a good way) plugin that's 
been configured with this Ant repo. This has much more finer grained 
controls over what can be triggered and who can trigger/retrigger the 
jobs from pull requests. This still follows the apache build conventions 
and in fact uses the same technique as many other apache hosted projects 
do. I'll migrate the one for Ivy to this scheme once things settle down 
with this one.


[1] https://github.com/apache/ant

[2] https://builds.apache.org/job/Ant%20Github-PR-Windows/


-Jaikiran


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

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Stefan Bodewig]

On 2017-12-12, Jaikiran Pai wrote:

> So the one final test that's still failing is this one[1]. It's
> failing consistently only on Jenkins, that too with only Java 8
> (jdk1.8.0_131). I have tried reproducing that one locally with that
> exact Java version and even the latest Java 8 and haven't been able to
> reproduce it. Before I try and debug this on that Jenkins environment
> (which doesn't seem to be easy to do), I would like to know if this is
> reproducible for anyone else.

No, I haven't been able either.

Stefan

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

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Jaikiran Pai]

So the one final test that's still failing is this one[1]. It's failing 
consistently only on Jenkins, that too with only Java 8 (jdk1.8.0_131). 
I have tried reproducing that one locally with that exact Java version 
and even the latest Java 8 and haven't been able to reproduce it. Before 
I try and debug this on that Jenkins environment (which doesn't seem to 
be easy to do), I would like to know if this is reproducible for anyone 
else.


[1] 
https://builds.apache.org/job/Ant-Build-Matrix-master-Linux/lastCompletedBuild/jdk=JDK%201.8%20(latest)/testReport/org.apache.tools.ant.taskdefs.optional.unix/SymlinkTest/testRecreate/


-Jaikiran

On 10/12/17 3:13 PM, Stefan Bodewig wrote:

On 2017-12-10, Stefan Bodewig wrote:


testCreateDoubleHanging is related to
https://bz.apache.org/bugzilla/show_bug.cgi?id=38199 judging from the
history. Here the link points to a non-existent file and Files.exists
returns false in Java8.

fixed by

@@ -37,6 +37,7 @@ import java.io.IOException;
  import java.io.InputStream;
  import java.io.PrintStream;
  import java.nio.file.Files;
+import java.nio.file.LinkOption;
  import java.nio.file.Path;
  import java.nio.file.Paths;
  import java.util.ArrayList;
@@ -440,7 +441,7 @@ public class Symlink extends DispatchTask {
  private void doLink(String res, String lnk) throws BuildException {
  final Path link = Paths.get(lnk);
  final Path target = Paths.get(res);
-final boolean alreadyExists = Files.exists(link);
+final boolean alreadyExists = Files.exists(link, 
LinkOption.NOFOLLOW_LINKS);
  if (!alreadyExists) {
  // if the path (at which the link is expected to be created) 
isn't already present
  // then we just go ahead and attempt to symlink


-
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: Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Stefan Bodewig]

On 2017-12-12, Jaikiran Pai wrote:

>>> So I have now pushed a fix[1] on top of my previous changes, which
>>> should accommodate both these use cases (and continue to use Java 7
>>> APIs for symlinking).
>> This is very useful, many thanks. We may want to modify the manual so it
>> becomes clear that overwrite will replace regular files as well.
> Done. The documentation of symlink task is now updated
> https://github.com/apache/ant/commit/485b92fe7494c5473e019329cbf7a33e556acad6

Thanks

Stefan

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

Re: Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Jaikiran Pai]

So I have now pushed a fix[1] on top of my previous changes, which
should accommodate both these use cases (and continue to use Java 7
APIs for symlinking).

This is very useful, many thanks. We may want to modify the manual so it
becomes clear that overwrite will replace regular files as well.
Done. The documentation of symlink task is now updated 
https://github.com/apache/ant/commit/485b92fe7494c5473e019329cbf7a33e556acad6


-Jaikiran

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

Re: Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Stefan Bodewig]

On 2017-12-12, Jaikiran Pai wrote:

> I went back and read up both these bugzilla reports again and I now
> realize that supporting one doesn't necessarily mean not supporting
> the other. BZ-43426 is about letting existing file be overwritten
> (irrespective of the type of the file) if the overwrite flag is
> true. BZ-58683 is about not overwriting any kind of file, if overwrite
> flag is false (before the changes I introduced, it was in fact
> overwriting files even when overwrite was false, a side-effect of the
> ln -s usage).

Great!

> So I have now pushed a fix[1] on top of my previous changes, which
> should accommodate both these use cases (and continue to use Java 7
> APIs for symlinking).

This is very useful, many thanks. We may want to modify the manual so it
becomes clear that overwrite will replace regular files as well.

Stefan

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

Re: Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Jaikiran Pai]

I went back and read up both these bugzilla reports again and I now 
realize that supporting one doesn't necessarily mean not supporting the 
other. BZ-43426 is about letting existing file be overwritten 
(irrespective of the type of the file) if the overwrite flag is true. 
BZ-58683 is about not overwriting any kind of file, if overwrite flag is 
false (before the changes I introduced, it was in fact overwriting files 
even when overwrite was false, a side-effect of the ln -s usage).


So I have now pushed a fix[1] on top of my previous changes, which 
should accommodate both these use cases (and continue to use Java 7 APIs 
for symlinking). No change has been done to the existing test and it now 
passes. Do let me know, if this is good enough to have BZ-58683 fixed 
and yet maintain backward compatibility with existing released versions 
of Ant. If you do see any issues with this set of changes, I am willing 
to undo them and go back to the original state that was before I started 
these changes.


[1] 
https://github.com/apache/ant/commit/b3c7d5dc451960986a94d24785a2c1d24b0b0d6a


-Jaikiran


On 10/12/17 5:15 PM, Stefan Bodewig wrote:

[@Steve I'm trying to drag you in as you've been the one who brought in
the change that gets contested by
https://bz.apache.org/bugzilla/show_bug.cgi?id=58683 and maybe you
recall the details better than we do.]

On 2017-12-10, Jaikiran Pai wrote:


On 10/12/17 3:09 PM, Stefan Bodewig wrote:

On 2017-12-10, Jaikiran Pai wrote:

I'll investigate why this is failing (local tests pass for me) and fix it.

Target testCreateOverFile in the antunit test explicitly tries to
replace a file with a link, doing exactly what the bugzilla report says
is a bug. So the behavior seems to have been intentional.
We now need to figure out whether the bug report was genuine (and list
the change as breaking) or we want to revert part of your fix, change
the documentation and change the bugzilla issue's resolution to a
WONTFIX.

The symlink task documentation[1] states this for the "overwrite" attribute:

Overwrite existing links or not.

It does explicitly mention that it's meant for overwriting links. The
test here, like you note, tries to overwrite a non-symlink file and
IMO it should error out, like it does with this change. After all, the
entire symlink task is meant to just deal with symlinks and
overwriting non-symlinks doesn't seem right. Having said that, I do
agree that this is a change in behaviour and we should list this as
such, if we do decide to let this change stay.
The reason why that existing test was introduced in first place and
the feature to let the symlink task overwrite a non-symlink file goes
back to this issue
https://bz.apache.org/bugzilla/show_bug.cgi?id=43426. The rationale in
that description seems to be that the Unix ln -sf apparently allows
overwriting non-symlink file with a symlink. Given that context, I'm
not really sure how we should proceed. Should we make this breaking
change or should we let the prior behaviour continue?
I'm in favour of this breaking change, but I won't mind switching back
to the prior behaviour if you and others think that's a better thing
to do.

Thank you for digging into the history, Jaikiran.

43426 is explicitly listed as a fixed bug (in 1.8.0) so I'm leaning
towards keeping and documenting the behavior of allowing  to
replace regular files.

Stefan

-
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: Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Stefan Bodewig]

[@Steve I'm trying to drag you in as you've been the one who brought in
the change that gets contested by
https://bz.apache.org/bugzilla/show_bug.cgi?id=58683 and maybe you
recall the details better than we do.]

On 2017-12-10, Jaikiran Pai wrote:

> On 10/12/17 3:09 PM, Stefan Bodewig wrote:
>> On 2017-12-10, Jaikiran Pai wrote:

>>> I'll investigate why this is failing (local tests pass for me) and fix it.

>> Target testCreateOverFile in the antunit test explicitly tries to
>> replace a file with a link, doing exactly what the bugzilla report says
>> is a bug. So the behavior seems to have been intentional.

>> We now need to figure out whether the bug report was genuine (and list
>> the change as breaking) or we want to revert part of your fix, change
>> the documentation and change the bugzilla issue's resolution to a
>> WONTFIX.

> The symlink task documentation[1] states this for the "overwrite" attribute:

> 
> Overwrite existing links or not.
> 

> It does explicitly mention that it's meant for overwriting links. The
> test here, like you note, tries to overwrite a non-symlink file and
> IMO it should error out, like it does with this change. After all, the
> entire symlink task is meant to just deal with symlinks and
> overwriting non-symlinks doesn't seem right. Having said that, I do
> agree that this is a change in behaviour and we should list this as
> such, if we do decide to let this change stay.

> The reason why that existing test was introduced in first place and
> the feature to let the symlink task overwrite a non-symlink file goes
> back to this issue
> https://bz.apache.org/bugzilla/show_bug.cgi?id=43426. The rationale in
> that description seems to be that the Unix ln -sf apparently allows
> overwriting non-symlink file with a symlink. Given that context, I'm
> not really sure how we should proceed. Should we make this breaking
> change or should we let the prior behaviour continue?

> I'm in favour of this breaking change, but I won't mind switching back
> to the prior behaviour if you and others think that's a better thing
> to do.

Thank you for digging into the history, Jaikiran.

43426 is explicitly listed as a fixed bug (in 1.8.0) so I'm leaning
towards keeping and documenting the behavior of allowing  to
replace regular files.

Stefan

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

Potential breaking change to symlink task [ was Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977]

[Jaikiran Pai]

On 10/12/17 3:09 PM, Stefan Bodewig wrote:

On 2017-12-10, Jaikiran Pai wrote:


I'll investigate why this is failing (local tests pass for me) and fix it.


Target testCreateOverFile in the antunit test explicitly tries to
replace a file with a link, doing exactly what the bugzilla report says
is a bug. So the behavior seems to have been intentional.

We now need to figure out whether the bug report was genuine (and list
the change as breaking) or we want to revert part of your fix, change
the documentation and change the bugzilla issue's resolution to a
WONTFIX.


The symlink task documentation[1] states this for the "overwrite" attribute:


Overwrite existing links or not.


It does explicitly mention that it's meant for overwriting links. The 
test here, like you note, tries to overwrite a non-symlink file and IMO 
it should error out, like it does with this change. After all, the 
entire symlink task is meant to just deal with symlinks and overwriting 
non-symlinks doesn't seem right. Having said that, I do agree that this 
is a change in behaviour and we should list this as such, if we do 
decide to let this change stay.



The reason why that existing test was introduced in first place and the 
feature to let the symlink task overwrite a non-symlink file goes back 
to this issue https://bz.apache.org/bugzilla/show_bug.cgi?id=43426. The 
rationale in that description seems to be that the Unix ln -sf 
apparently allows overwriting non-symlink file with a symlink. Given 
that context, I'm not really sure how we should proceed. Should we make 
this breaking change or should we let the prior behaviour continue?


I'm in favour of this breaking change, but I won't mind switching back 
to the prior behaviour if you and others think that's a better thing to do.



[1] https://ant.apache.org/manual/Tasks/symlink.html

-Jaikiran

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

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Jaikiran Pai]

You are right, that indeed was the issue (for one of that failing test). 
I have pushed a commit with this change to fix that one.


-Jaikiran


On 10/12/17 3:13 PM, Stefan Bodewig wrote:

On 2017-12-10, Stefan Bodewig wrote:


testCreateDoubleHanging is related to
https://bz.apache.org/bugzilla/show_bug.cgi?id=38199 judging from the
history. Here the link points to a non-existent file and Files.exists
returns false in Java8.

fixed by

@@ -37,6 +37,7 @@ import java.io.IOException;
  import java.io.InputStream;
  import java.io.PrintStream;
  import java.nio.file.Files;
+import java.nio.file.LinkOption;
  import java.nio.file.Path;
  import java.nio.file.Paths;
  import java.util.ArrayList;
@@ -440,7 +441,7 @@ public class Symlink extends DispatchTask {
  private void doLink(String res, String lnk) throws BuildException {
  final Path link = Paths.get(lnk);
  final Path target = Paths.get(res);
-final boolean alreadyExists = Files.exists(link);
+final boolean alreadyExists = Files.exists(link, 
LinkOption.NOFOLLOW_LINKS);
  if (!alreadyExists) {
  // if the path (at which the link is expected to be created) 
isn't already present
  // then we just go ahead and attempt to symlink


-
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 build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Stefan Bodewig]

On 2017-12-10, Stefan Bodewig wrote:

> testCreateDoubleHanging is related to
> https://bz.apache.org/bugzilla/show_bug.cgi?id=38199 judging from the
> history. Here the link points to a non-existent file and Files.exists
> returns false in Java8.

fixed by

@@ -37,6 +37,7 @@ import java.io.IOException;
 import java.io.InputStream;
 import java.io.PrintStream;
 import java.nio.file.Files;
+import java.nio.file.LinkOption;
 import java.nio.file.Path;
 import java.nio.file.Paths;
 import java.util.ArrayList;
@@ -440,7 +441,7 @@ public class Symlink extends DispatchTask {
 private void doLink(String res, String lnk) throws BuildException {
 final Path link = Paths.get(lnk);
 final Path target = Paths.get(res);
-final boolean alreadyExists = Files.exists(link);
+final boolean alreadyExists = Files.exists(link, 
LinkOption.NOFOLLOW_LINKS);
 if (!alreadyExists) {
 // if the path (at which the link is expected to be created) isn't 
already present
 // then we just go ahead and attempt to symlink


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

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Stefan Bodewig]

On 2017-12-10, Jaikiran Pai wrote:

> I'll investigate why this is failing (local tests pass for me) and fix it.

Are you using Java9 locally? The test only fail for Java8 in Jenkins,
this could explain the difference. The antunit tests fail for me with
Java 8 as well, while the JUnit test passes.

testCreateDoubleHanging is related to
https://bz.apache.org/bugzilla/show_bug.cgi?id=38199 judging from the
history. Here the link points to a non-existent file and Files.exists
returns false in Java8.

Target testCreateOverFile in the antunit test explicitly tries to
replace a file with a link, doing exactly what the bugzilla report says
is a bug. So the behavior seems to have been intentional.

We now need to figure out whether the bug report was genuine (and list
the change as breaking) or we want to revert part of your fix, change
the documentation and change the bugzilla issue's resolution to a
WONTFIX.

Stefan

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

Re: Jenkins build became unstable: Ant-Build-Matrix-master-Linux » JDK 1.8 (latest) #977

[Jaikiran Pai]

I'll investigate why this is failing (local tests pass for me) and fix it.

-Jaikiran


On 10/12/17 2:29 PM, Apache Jenkins Server wrote:

See 
<https://builds.apache.org/job/Ant-Build-Matrix-master-Linux/jdk=JDK%201.8%20(latest)/977/display/redirect?page=changes>




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

Re: Disk shortage in Jenkins server

[Gintautas Grigelionis]

I opened https://issues.apache.org/jira/browse/INFRA-15108 and BTLOI PR
builds work again.

Gintas

2017-09-17 21:53 GMT+02:00 Gintautas Grigelionis :

> PR builds are failing, how to report this?
>
> Thanks,
> Gintas
>

Disk shortage in Jenkins server

[Gintautas Grigelionis]

PR builds are failing, how to report this?

Thanks,
Gintas

Re: Ivy Jenkins jobs have been failing - infra issues

[Jaikiran Pai]

https://issues.apache.org/jira/browse/INFRA-14712

-Jaikiran
On 26/07/17 6:36 PM, Jaikiran Pai wrote:
More of a FYI than anything else - the past couple of days or so, we 
haven't had regular successful runs of our various Ivy Jenkins jobs. 
Each run failing with different errors, all pointing back to 
infrastructure issues at this moment. In fact, I see some other Apache 
project builds running into similar issues - as basic as DNS name 
resolution failures of git-wip-us.apache.org on the Jenkins nodes.


None of this is specific to our jobs, so I don't see anything that we 
can do to solve this at the moment, other than maybe raising it with 
Infra team. I haven't had the time to check the Infra team mailing 
list or their JIRA to see if this is already reported by other 
projects. I will see if I can find some time tonight to check that and 
report it, if it hasn't yet been.


-Jaikiran





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

Re: Build failed in Jenkins: Ivy #627

[Jaikiran Pai]

To avoid more such mails, I'm going to disable this job for a few hours 
till we get the infra issues sorted out.


-Jaikiran


On 26/07/17 10:44 PM, Apache Jenkins Server wrote:

See <https://builds.apache.org/job/Ivy/627/display/redirect>

--
Started by an SCM change
Running as hibou
[EnvInject] - Loading node environment variables.
Building remotely on cassandra15 (cassandra ubuntu) in workspace 
<https://builds.apache.org/job/Ivy/ws/>
  > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
  > git config remote.origin.url 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git # timeout=10
Cleaning workspace
  > git rev-parse --verify HEAD # timeout=10
Resetting working tree
  > git reset --hard # timeout=10
  > git clean -fdx # timeout=10
  > git submodule foreach --recursive git reset --hard # timeout=10
  > git submodule foreach --recursive git clean -fdx # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git
  > git --version # timeout=10
  > git fetch --tags --progress 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git 
+refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:812)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1079)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1110)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:560)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:485)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: fatal: unable to access 
'https://git-wip-us.apache.org/repos/asf/ant-ivy.git/': Could not resolve host: 
git-wip-us.apache.org

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1903)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1622)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:71)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:348)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
at ..remote call to cassandra15(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:830)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor864.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy104.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810)
... 11 more
ERROR: Error fetching remote repo 'origin'
Retrying after 10 seconds
  > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
  > git config remote.origin.url 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git # timeout=10
Cleaning workspace
  > git r

Ivy Jenkins jobs have been failing - infra issues

[Jaikiran Pai]

More of a FYI than anything else - the past couple of days or so, we 
haven't had regular successful runs of our various Ivy Jenkins jobs. 
Each run failing with different errors, all pointing back to 
infrastructure issues at this moment. In fact, I see some other Apache 
project builds running into similar issues - as basic as DNS name 
resolution failures of git-wip-us.apache.org on the Jenkins nodes.


None of this is specific to our jobs, so I don't see anything that we 
can do to solve this at the moment, other than maybe raising it with 
Infra team. I haven't had the time to check the Infra team mailing list 
or their JIRA to see if this is already reported by other projects. I 
will see if I can find some time tonight to check that and report it, if 
it hasn't yet been.


-Jaikiran



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

Re: Build failed in Jenkins: IvyDE #320

[Nicolas Lalevée]

Indeed, with the proper urls it builds, thank both of you.

Nicolas

> Le 11 juil. 2017 à 07:29, Jaikiran Pai  a écrit :
> 
> 
> On 11/07/17 3:26 AM, Nicolas Lalevée wrote:
>> I don’t understand what is going on. The files are there and then they 
>> disappear… I have been able to download this file, and now it is gone. It 
>> happens several times for different files locally… I though I had finally 
>> have found a stable set of zip to download, but it seems actually not...
>> 
>> Nicolas
>> 
>>> 
>>> eclipse-check-download-gef:
>>> 
>>> eclipse-get-gef:
>>>  [get] Getting: 
>>> http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip_id=1
>>>  [get] To: 
>>> 
>>> *[get] 
>>> http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip_id=1
>>>  moved to 
>>> http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip
>>>  *  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] 
>>>  [get] .
>>> 
>>> eclipse-check-download-zest:
>>> 
>>> eclipse-get-zest:
>>>  [get] Getting: 
>>> http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip_id=1
>>>  [get] To: 
>>> 
>>>  [*get] 
>>> http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip_id=1
>>>  moved to 
>>> http://download.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip*
> 
> From those logs it appears that whoever setup the HTTP (302) redirects for 
> these downloads at eclipse.org, set it up correctly for gef-sdk to point to 
> archive.eclipse.org whereas for get-zest it has been setup to point to an 
> incorrect URL at download.eclipse.org which just presents a generic 404 page.
> 
> I think for us, at this point, it's a matter of changing our build file to 
> just point directly to the relevant specific links listed on 
> archive.eclipse.org here 
> http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/
> 
> -Jaikiran
> 


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

Re: Build failed in Jenkins: IvyDE #320

[Jaikiran Pai]

On 11/07/17 3:26 AM, Nicolas Lalevée wrote:

I don’t understand what is going on. The files are there and then they 
disappear… I have been able to download this file, and now it is gone. It 
happens several times for different files locally… I though I had finally have 
found a stable set of zip to download, but it seems actually not...

Nicolas



eclipse-check-download-gef:

eclipse-get-gef:
  [get] Getting: 
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip_id=1
  [get] To: 

*[get] 
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip_id=1 
moved to 
http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-SDK-3.9.100.zip 
*  [get] 

  [get] 
  [get] 
  [get] 
  [get] 
  [get] 
  [get] 
  [get] 
  [get] 
  [get] 
  [get] .

eclipse-check-download-zest:

eclipse-get-zest:
  [get] Getting: 
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip_id=1
  [get] To: 

  [*get] 
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip_id=1 
moved to 
http://download.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/GEF-zest-3.9.100.zip*


From those logs it appears that whoever setup the HTTP (302) redirects 
for these downloads at eclipse.org, set it up correctly for gef-sdk to 
point to archive.eclipse.org whereas for get-zest it has been setup to 
point to an incorrect URL at download.eclipse.org which just presents a 
generic 404 page.


I think for us, at this point, it's a matter of changing our build file 
to just point directly to the relevant specific links listed on 
archive.eclipse.org here 
http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/


-Jaikiran

Re: Build failed in Jenkins: IvyDE #320

[Gintautas Grigelionis]

Looks like GEF3 was archived, see
http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/

Gintas

2017-07-10 23:56 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

> I don’t understand what is going on. The files are there and then they
> disappear… I have been able to download this file, and now it is gone. It
> happens several times for different files locally… I though I had finally
> have found a stable set of zip to download, but it seems actually not...
>
> Nicolas
>
> > Le 10 juil. 2017 à 23:37, Apache Jenkins Server <
> jenk...@builds.apache.org> a écrit :
> >
> > See <https://builds.apache.org/job/IvyDE/320/display/
> redirect?page=changes>
> >
> > Changes:
> >
> > [nicolas.lalevee] update build dependencies, and reenable the build of
> the resolve
> >
> > --
> > [...truncated 29.75 KB...]
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] 
> >  [get] ..

Re: Build failed in Jenkins: IvyDE #320

[Nicolas Lalevée]

I don’t understand what is going on. The files are there and then they 
disappear… I have been able to download this file, and now it is gone. It 
happens several times for different files locally… I though I had finally have 
found a stable set of zip to download, but it seems actually not...

Nicolas

> Le 10 juil. 2017 à 23:37, Apache Jenkins Server <jenk...@builds.apache.org> a 
> écrit :
> 
> See <https://builds.apache.org/job/IvyDE/320/display/redirect?page=changes>
> 
> Changes:
> 
> [nicolas.lalevee] update build dependencies, and reenable the build of the 
> resolve
> 
> --
> [...truncated 29.75 KB...]
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 
>  [get] 

Re: Jenkins build is back to normal : IvyDE #319

[Nicolas Lalevée]

Finally.

But the build of resolve visualizer has been deactivated, the Zest plugins are 
not properly resolved by the build.

Nicolas

> Le 2 juil. 2017 à 12:01, Apache Jenkins Server <jenk...@builds.apache.org> a 
> écrit :
> 
> See <https://builds.apache.org/job/IvyDE/319/display/redirect?page=changes>
> 


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

Re: Jenkins Jobs of Ivy/IvyDE

[Jaikiran Pai]

I have now disabled the nightly job[1] and added a note to the job's 
description stating that the latest binaries can be obtained from the other Ivy 
job[2]. 


[1] https://builds.apache.org/job/Ivy-NightlyDistribution/
[2] https://builds.apache.org/job/Ivy/lastSuccessfulBuild/

-Jaikiran
On 29-Jun-2017, at 11:18 AM, Jaikiran Pai  wrote:


On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée  wrote:

> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
> now the nightly is redundant.


I think yes, the nightly job is now probably redundant - which is fine, we can 
always direct users to this new job for the latest snapshots. The only way this 
job differs from the nightly one now is that the nightly one currently 
publishes the latest (site) docs too. I guess that’s not a big thing since we 
will soon be publishing the latest site docs live on the Ant site (under the 
“master” section).

-Jaikiran


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

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Le 29 juin 2017 à 07:48, Jaikiran Pai  a écrit :
> 
> 
> On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée  
> wrote:
> 
>> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
>> now the nightly is redundant.
> 
> 
> I think yes, the nightly job is now probably redundant - which is fine, we 
> can always direct users to this new job for the latest snapshots. The only 
> way this job differs from the nightly one now is that the nightly one 
> currently publishes the latest (site) docs too. I guess that’s not a big 
> thing since we will soon be publishing the latest site docs live on the Ant 
> site (under the “master” section).

I have done that. For some reason it took a very long time to get actually 
published, but it is there now:
http://ant.apache.org/ivy/history/master/index.html 


I have also update the doc about the site:
http://svn.apache.org/repos/asf/ant/site/README.txt 


Nicolas

Re: Jenkins Jobs of Ivy/IvyDE

[Jaikiran Pai]

On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée  wrote:

> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
> now the nightly is redundant.


I think yes, the nightly job is now probably redundant - which is fine, we can 
always direct users to this new job for the latest snapshots. The only way this 
job differs from the nightly one now is that the nightly one currently 
publishes the latest (site) docs too. I guess that’s not a big thing since we 
will soon be publishing the latest site docs live on the Ant site (under the 
“master” section).

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

Re: Jenkins Jobs of Ivy/IvyDE

[Jaikiran Pai]

I pushed a fix for this a few days back and the job is now functioning 
correctly.

-Jaikiran
On 26-Jun-2017, at 8:15 AM, Jaikiran Pai <jai.forums2...@gmail.com> wrote:

The retrieve failure looks like a genuine bug which might be related to one of 
the changes I had done in one of the PRs a while back. I’ll take a look at this 
today.

-Jaikiran
On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> wrote:

Hi,

I worked on the Jenkins jobs to make them work.

There was some issues with job dependencies. Following the instructions there 
[1] worked.
I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
now the nightly is redundant.
I made the Ivy-checks build work, some https changed in favor of http.
The test matrix is now separated into two builds now, since no Ant installation 
is common for both Windows and Ubuntu. They are both testing JDK7 and JDK8.
The IvyDE job is no longer downloading Ivy’s jar via a hard coded http url. It 
is relying now on a plugin which copies artifacts around.

There are still some error though, most probably not related to the Jenkins 
configuration:
- the Windows build of Ivy is broken, the retrieve doesn’t work [2].
- the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is 
reproductible locally.

I’ll look at the IvyDE updatesite job when the build of IvyDE will be fixed.

Nicolas

[1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization 
<https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>
[2] 
https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console
 
<https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
[3] https://builds.apache.org/job/IvyDE/315/console 
<https://builds.apache.org/job/IvyDE/315/console>




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

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Dropins (or "drops" as they're called in the distributions) is what IvyDE
> builds were based on all the time. I am still confounded why it worked
> before and stopped working now. Yet, reading the documentation I became
> convinced that the dropins must be unpacked in another location. So I just
> wanted to apologize for an erroneous suggestion and share some information
> in order for it to be independently confirmed. I may open a PR, but since
> you're working on this, I assumed that you could move faster than me.

Actually I am not looking into it at the present time. I’ll get into it at some 
point, if it is not fixed before. So if you think you can solve this, I’ll 
welcome your help.

On the side note, I am now an Intellij user, I only start Eclipse to build 
IvyDE. And I haven’t done Eclipse plugin development in years, so I am not 
fast. :)

> There's another issue to be resolved for local builds to work hassle-free
> -- currently, they need an environment variable BUILD_NUMBER set up by
> Jenkins.

Is it required ? This env variable is only needed when calling the jenkins 
target. In a dev environment we shouldn't call them.

I think in this mailing list we told to run some jenkins target to make easier 
the setup of the dev environment. But it as actually to call the targets which 
download and setup Eclipse. That’s why I renamed them, so we should continue to 
make the proper distinction to the tweaks for Jenkins, and the dev targets.

Nicolas

Re: Jenkins Jobs of Ivy/IvyDE

[Gintautas Grigelionis]

2017-06-26 13:54 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

>
> > Le 26 juin 2017 à 07:46, Gintautas Grigelionis <g.grigelio...@gmail.com>
> a écrit :
> >
> > If I understand the process correctly, Jenkins executes "ant
> > prepare-jenkins" first, which does not work locally any more, because the
> > property used to figure out where to get Ivy jar from is set to an empty
> > string. I wondered what was the reason for that change. Actually, when I
> > look at it again, the change is even more drastic. Previously,
> > "hudson-install-ivy" would depend on both "hudson-install-ivy-jar"
> (setting
> > "ivy.jar.url") and "hudson-install-ivy-release" (setting "ivy.version" if
> > "hudson.ivy.jar.url" was not available). In addition, "baseLocation" was
> > set. The new target "jenkins-install-ivy" does not make sense to me.
>
> This is because of the change in the configuration of Jenkins Job, as I
> briefly explained in the first mail. Now the Ivy artifact is not downloaded
> via an url, there is a Jenkins plugin, a build step, which handle the copy
> of the artifacts. Relying on this internal copy of artifact seems more
> stable that relying on a http/https url. The jenkins-install-ivy target is
> then calling install-ivy with a path rather than an url.
>

Sorry, I misunderstood the brief description. In my world,
"prepare-eclipse" should also download Ivy and add it to PDE.


> Now the jenkins-* targets are really dedicated to being ran on jenkins and
> are not suited for a local environment. That is why I renamed the targets
> to download and setup an eclipse, removing the jenkins- prefix: these can
> be used in a dev environment.
> If you do that: ant prepare-eclipse
> And do the install: ant install-ivy -Divy.jar.url=https://builds.
> apache.org/view/A/view/Ant/job/Ivy/lastSuccessfulBuild/
> artifact/build/artifact/jars/ivy.jar
> Then you will be able to reproduce the issue. At least I can.
>

Thanks, now I get the idea.

> In the next step, Jenkins executes "ant dist checkstyle rat" which fails
> > because of "missing" Eclipse plugins. That is apparently caused by
> dropins
> > being unpacked in the wrong place in the first build stage
> > ("prepare-jenkins"). In my first suggestion, I was obviously wrong about
> > what that place should be. I do recall using getting Eclipse to work
> > locally with an older IvyDE build.xml, but I did not document whether
> that
> > involved any extra steps. However, Eclipse is able to bootstrap itself
> > locally when dropins are unpacked in "dropins" directory, see Eclipse
> > documentation [1]. That's what the patch is for.
>
> I don’t have much experience with using dropins, so if you think this will
> help make the build more stable, you’re welcomed to open a PR.
>

Dropins (or "drops" as they're called in the distributions) is what IvyDE
builds were based on all the time. I am still confounded why it worked
before and stopped working now. Yet, reading the documentation I became
convinced that the dropins must be unpacked in another location. So I just
wanted to apologize for an erroneous suggestion and share some information
in order for it to be independently confirmed. I may open a PR, but since
you're working on this, I assumed that you could move faster than me.
There's another issue to be resolved for local builds to work hassle-free
-- currently, they need an environment variable BUILD_NUMBER set up by
Jenkins.

Gintas


> > [1] https://wiki.eclipse.org/Equinox/p2/Getting_Started#Dropins
> >
> >
> > 2017-06-25 22:27 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:
> >
> >>
> >>> I am sorry, my memory of what I was doing back in December is
> incorrect.
> >>> I guess I somehow updated
> >>> configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or
> did
> >>> something else.
> >>> Luckily, there's a simpler way, the dropins should go into their own
> >>> special directory, which needs the following change
> >>>
> >>> --- a/build.xml
> >>> +++ b/build.xml
> >>> @@ -555,11 +555,11 @@ You have to specify the Ivy to install with one
> of
> >>> the following property:
> >>> >> failonerror="false"
> >>> />
> >>> >>> failonerror="false" />
> >>> >>> dest="${basedir}/dependencies/" />
> >>> - >>> dest="${basedir}/dependencies/&q

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Le 26 juin 2017 à 07:46, Gintautas Grigelionis <g.grigelio...@gmail.com> a 
> écrit :
> 
> If I understand the process correctly, Jenkins executes "ant
> prepare-jenkins" first, which does not work locally any more, because the
> property used to figure out where to get Ivy jar from is set to an empty
> string. I wondered what was the reason for that change. Actually, when I
> look at it again, the change is even more drastic. Previously,
> "hudson-install-ivy" would depend on both "hudson-install-ivy-jar" (setting
> "ivy.jar.url") and "hudson-install-ivy-release" (setting "ivy.version" if
> "hudson.ivy.jar.url" was not available). In addition, "baseLocation" was
> set. The new target "jenkins-install-ivy" does not make sense to me.

This is because of the change in the configuration of Jenkins Job, as I briefly 
explained in the first mail. Now the Ivy artifact is not downloaded via an url, 
there is a Jenkins plugin, a build step, which handle the copy of the 
artifacts. Relying on this internal copy of artifact seems more stable that 
relying on a http/https url. The jenkins-install-ivy target is then calling 
install-ivy with a path rather than an url.

Now the jenkins-* targets are really dedicated to being ran on jenkins and are 
not suited for a local environment. That is why I renamed the targets to 
download and setup an eclipse, removing the jenkins- prefix: these can be used 
in a dev environment.
If you do that: ant prepare-eclipse
And do the install: ant install-ivy 
-Divy.jar.url=https://builds.apache.org/view/A/view/Ant/job/Ivy/lastSuccessfulBuild/artifact/build/artifact/jars/ivy.jar
Then you will be able to reproduce the issue. At least I can.

> In the next step, Jenkins executes "ant dist checkstyle rat" which fails
> because of "missing" Eclipse plugins. That is apparently caused by dropins
> being unpacked in the wrong place in the first build stage
> ("prepare-jenkins"). In my first suggestion, I was obviously wrong about
> what that place should be. I do recall using getting Eclipse to work
> locally with an older IvyDE build.xml, but I did not document whether that
> involved any extra steps. However, Eclipse is able to bootstrap itself
> locally when dropins are unpacked in "dropins" directory, see Eclipse
> documentation [1]. That's what the patch is for.

I don’t have much experience with using dropins, so if you think this will help 
make the build more stable, you’re welcomed to open a PR.

Nicolas

> 
> Gintas
> 
> [1] https://wiki.eclipse.org/Equinox/p2/Getting_Started#Dropins
> 
> 
> 2017-06-25 22:27 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:
> 
>> 
>>> I am sorry, my memory of what I was doing back in December is incorrect.
>>> I guess I somehow updated
>>> configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or did
>>> something else.
>>> Luckily, there's a simpler way, the dropins should go into their own
>>> special directory, which needs the following change
>>> 
>>> --- a/build.xml
>>> +++ b/build.xml
>>> @@ -555,11 +555,11 @@ You have to specify the Ivy to install with one of
>>> the following property:
>>>> failonerror="false"
>>> />
>>>>> failonerror="false" />
>>>>> dest="${basedir}/dependencies/" />
>>> ->> dest="${basedir}/dependencies/" />
>>> ->> dest="${basedir}/dependencies/" />
>>> ->> dest="${basedir}/dependencies/" />
>>> ->> dest="${basedir}/dependencies/" />
>>> ->> dest="${basedir}/dependencies/" />
>>> +>> dest="${basedir}/dependencies/eclipse/dropins" />
>>> +>> dest="${basedir}/dependencies/eclipse/dropins" />
>>> +>> dest="${basedir}/dependencies/eclipse/dropins" />
>>> +>> dest="${basedir}/dependencies/eclipse/dropins" />
>>> +>> dest="${basedir}/dependencies/eclipse/dropins" />
>>>>> tofile="${basedir}/dependencies/${eclipse.download.sdk.name}" />
>>>
>> 
>> I don’t understand what you are suggesting. The issue at hand is resolving
>> the Ivy jar. The suggested patch is about installing eclipse plugins in
>> dropins. But the build is still not finding the ivy plugin.
>> 
>>> I don't understand why "jenkins-prepare" (neé "hudson-prepare") would
>> skip
>>> "download-ivy" (because "jenkins-install-ivy" sets ivy.jar.url to ""
>> rather
>>> than ${hudson.ivy.jar.url}) and fail?
>> 
>> Again, sorry, but I don’t understand what you are talking about. Are you
>> seing the same error as the one Jenkins is showing ? The error is occurring
>> with the eclipse build started, way later.
>> 
>> Nicolas
>> 
>> 
>> -
>> 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 Jobs of Ivy/IvyDE

[Gintautas Grigelionis]

If I understand the process correctly, Jenkins executes "ant
prepare-jenkins" first, which does not work locally any more, because the
property used to figure out where to get Ivy jar from is set to an empty
string. I wondered what was the reason for that change. Actually, when I
look at it again, the change is even more drastic. Previously,
"hudson-install-ivy" would depend on both "hudson-install-ivy-jar" (setting
"ivy.jar.url") and "hudson-install-ivy-release" (setting "ivy.version" if
"hudson.ivy.jar.url" was not available). In addition, "baseLocation" was
set. The new target "jenkins-install-ivy" does not make sense to me.

In the next step, Jenkins executes "ant dist checkstyle rat" which fails
because of "missing" Eclipse plugins. That is apparently caused by dropins
being unpacked in the wrong place in the first build stage
("prepare-jenkins"). In my first suggestion, I was obviously wrong about
what that place should be. I do recall using getting Eclipse to work
locally with an older IvyDE build.xml, but I did not document whether that
involved any extra steps. However, Eclipse is able to bootstrap itself
locally when dropins are unpacked in "dropins" directory, see Eclipse
documentation [1]. That's what the patch is for.

Gintas

[1] https://wiki.eclipse.org/Equinox/p2/Getting_Started#Dropins


2017-06-25 22:27 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

>
> > I am sorry, my memory of what I was doing back in December is incorrect.
> > I guess I somehow updated
> > configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or did
> > something else.
> > Luckily, there's a simpler way, the dropins should go into their own
> > special directory, which needs the following change
> >
> > --- a/build.xml
> > +++ b/build.xml
> > @@ -555,11 +555,11 @@ You have to specify the Ivy to install with one of
> > the following property:
> >  failonerror="false"
> > />
> >  > failonerror="false" />
> >  > dest="${basedir}/dependencies/" />
> > - > dest="${basedir}/dependencies/" />
> > - > dest="${basedir}/dependencies/" />
> > - > dest="${basedir}/dependencies/" />
> > - > dest="${basedir}/dependencies/" />
> > - > dest="${basedir}/dependencies/" />
> > + > dest="${basedir}/dependencies/eclipse/dropins" />
> > + > dest="${basedir}/dependencies/eclipse/dropins" />
> > + > dest="${basedir}/dependencies/eclipse/dropins" />
> > + > dest="${basedir}/dependencies/eclipse/dropins" />
> > +     > dest="${basedir}/dependencies/eclipse/dropins" />
> >  > tofile="${basedir}/dependencies/${eclipse.download.sdk.name}" />
> > 
>
> I don’t understand what you are suggesting. The issue at hand is resolving
> the Ivy jar. The suggested patch is about installing eclipse plugins in
> dropins. But the build is still not finding the ivy plugin.
>
> > I don't understand why "jenkins-prepare" (neé "hudson-prepare") would
> skip
> > "download-ivy" (because "jenkins-install-ivy" sets ivy.jar.url to ""
> rather
> > than ${hudson.ivy.jar.url}) and fail?
>
> Again, sorry, but I don’t understand what you are talking about. Are you
> seing the same error as the one Jenkins is showing ? The error is occurring
> with the eclipse build started, way later.
>
> Nicolas
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins Jobs of Ivy/IvyDE

[Jaikiran Pai]

The retrieve failure looks like a genuine bug which might be related to one of 
the changes I had done in one of the PRs a while back. I’ll take a look at this 
today.

-Jaikiran
On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> wrote:

Hi,

I worked on the Jenkins jobs to make them work.

There was some issues with job dependencies. Following the instructions there 
[1] worked.
I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
now the nightly is redundant.
I made the Ivy-checks build work, some https changed in favor of http.
The test matrix is now separated into two builds now, since no Ant installation 
is common for both Windows and Ubuntu. They are both testing JDK7 and JDK8.
The IvyDE job is no longer downloading Ivy’s jar via a hard coded http url. It 
is relying now on a plugin which copies artifacts around.

There are still some error though, most probably not related to the Jenkins 
configuration:
- the Windows build of Ivy is broken, the retrieve doesn’t work [2].
- the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is 
reproductible locally.

I’ll look at the IvyDE updatesite job when the build of IvyDE will be fixed.

Nicolas

[1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization 
<https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>
[2] 
https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console
 
<https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
[3] https://builds.apache.org/job/IvyDE/315/console 
<https://builds.apache.org/job/IvyDE/315/console>



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

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> I am sorry, my memory of what I was doing back in December is incorrect.
> I guess I somehow updated
> configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or did
> something else.
> Luckily, there's a simpler way, the dropins should go into their own
> special directory, which needs the following change
> 
> --- a/build.xml
> +++ b/build.xml
> @@ -555,11 +555,11 @@ You have to specify the Ivy to install with one of
> the following property:
>  />
>  failonerror="false" />
>  dest="${basedir}/dependencies/" />
> - dest="${basedir}/dependencies/" />
> - dest="${basedir}/dependencies/" />
> - dest="${basedir}/dependencies/" />
> - dest="${basedir}/dependencies/" />
> - src="${basedir}/dependencies/${eclipse.download.zest.name}.zip"
> dest="${basedir}/dependencies/" />
> + dest="${basedir}/dependencies/eclipse/dropins" />
> + dest="${basedir}/dependencies/eclipse/dropins" />
> + dest="${basedir}/dependencies/eclipse/dropins" />
> + dest="${basedir}/dependencies/eclipse/dropins" />
> + src="${basedir}/dependencies/${eclipse.download.zest.name}.zip"
> dest="${basedir}/dependencies/eclipse/dropins" />
>  tofile="${basedir}/dependencies/${eclipse.download.sdk.name}" />
> 

I don’t understand what you are suggesting. The issue at hand is resolving the 
Ivy jar. The suggested patch is about installing eclipse plugins in dropins. 
But the build is still not finding the ivy plugin.

> I don't understand why "jenkins-prepare" (neé "hudson-prepare") would skip
> "download-ivy" (because "jenkins-install-ivy" sets ivy.jar.url to "" rather
> than ${hudson.ivy.jar.url}) and fail?

Again, sorry, but I don’t understand what you are talking about. Are you seing 
the same error as the one Jenkins is showing ? The error is occurring with the 
eclipse build started, way later.

Nicolas


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

Re: Jenkins Jobs of Ivy/IvyDE

[Gintautas Grigelionis]

2017-06-25 18:23 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

> > [2]: please check that unpacking of drops puts files into the correct
> > places (the contents should go into "features" and "plugins" directories
> of
> > PDE).
>
> I have done that already. I even checked that the placed in the plugins
> directory have the proper OSGi metadata. It is reproductible locally if you
> wish to debug and suggest a fix.
>
> Nicolas
>

I am sorry, my memory of what I was doing back in December is incorrect.
I guess I somehow updated
configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or did
something else.
Luckily, there's a simpler way, the dropins should go into their own
special directory, which needs the following change

--- a/build.xml
+++ b/build.xml
@@ -555,11 +555,11 @@ You have to specify the Ivy to install with one of
the following property:
 
 
 
-
-
-
-
-
+
+
+    
+
+
 
 

I don't understand why "jenkins-prepare" (neé "hudson-prepare") would skip
"download-ivy" (because "jenkins-install-ivy" sets ivy.jar.url to "" rather
than ${hudson.ivy.jar.url}) and fail?

Gintas

> 2017-06-25 16:57 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org
> <mailto:nicolas.lale...@hibnet.org>>:
> >
> >> Hi,
> >>
> >> I worked on the Jenkins jobs to make them work.
> >>
> >> There was some issues with job dependencies. Following the instructions
> >> there [1] worked.
> >> I have made the Ivy Job also build the snapshot-bin, like the nightly.
> >> Maybe now the nightly is redundant.
> >> I made the Ivy-checks build work, some https changed in favor of http.
> >> The test matrix is now separated into two builds now, since no Ant
> >> installation is common for both Windows and Ubuntu. They are both
> testing
> >> JDK7 and JDK8.
> >> The IvyDE job is no longer downloading Ivy’s jar via a hard coded http
> >> url. It is relying now on a plugin which copies artifacts around.
> >>
> >> There are still some error though, most probably not related to the
> >> Jenkins configuration:
> >> - the Windows build of Ivy is broken, the retrieve doesn’t work [2].
> >> - the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is
> >> reproductible locally.
> >>
> >> I’ll look at the IvyDE updatesite job when the build of IvyDE will be
> >> fixed.
> >>
> >> Nicolas
> >>
> >> [1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization
> <
> >> https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization <
> https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>>
> >> [2] https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows <
> https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows>,
> >> jdk=JDK%201.7%20(latest)/2/console <https://builds.apache.org/ <
> https://builds.apache.org/>
> >> job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
> >> [3] https://builds.apache.org/job/IvyDE/315/console <
> https://builds.apache.org/job/IvyDE/315/console> <
> >> https://builds.apache.org/job/IvyDE/315/console <
> https://builds.apache.org/job/IvyDE/315/console>>
>
>

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Le 25 juin 2017 à 16:57, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit 
> :
> 
> Hi,
> 
> I worked on the Jenkins jobs to make them work.
> 
> There was some issues with job dependencies. Following the instructions there 
> [1] worked.

Then didn’t worked…
Setting the Authorization to « Run as User who Triggered Build » seems to only 
works when triggered manually, not by the cron. So now I have set « Run as 
Specific User », me, « hibou ». It now works with the cron. Most probably for 
me manually too. But maybe not for anybody else…

Nicolas


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

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Le 25 juin 2017 à 17:50, Gintautas Grigelionis <g.grigelio...@gmail.com> a 
> écrit :
> 
> [3]: the path looks wrong, it starts with "\:\:\ »

I have seen that too.

> [2]: please check that unpacking of drops puts files into the correct
> places (the contents should go into "features" and "plugins" directories of
> PDE).

I have done that already. I even checked that the placed in the plugins 
directory have the proper OSGi metadata. It is reproductible locally if you 
wish to debug and suggest a fix.

Nicolas

> 
> Gintas
> 
> 2017-06-25 16:57 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org 
> <mailto:nicolas.lale...@hibnet.org>>:
> 
>> Hi,
>> 
>> I worked on the Jenkins jobs to make them work.
>> 
>> There was some issues with job dependencies. Following the instructions
>> there [1] worked.
>> I have made the Ivy Job also build the snapshot-bin, like the nightly.
>> Maybe now the nightly is redundant.
>> I made the Ivy-checks build work, some https changed in favor of http.
>> The test matrix is now separated into two builds now, since no Ant
>> installation is common for both Windows and Ubuntu. They are both testing
>> JDK7 and JDK8.
>> The IvyDE job is no longer downloading Ivy’s jar via a hard coded http
>> url. It is relying now on a plugin which copies artifacts around.
>> 
>> There are still some error though, most probably not related to the
>> Jenkins configuration:
>> - the Windows build of Ivy is broken, the retrieve doesn’t work [2].
>> - the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is
>> reproductible locally.
>> 
>> I’ll look at the IvyDE updatesite job when the build of IvyDE will be
>> fixed.
>> 
>> Nicolas
>> 
>> [1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization <
>> https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization 
>> <https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>>
>> [2] https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows 
>> <https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows>,
>> jdk=JDK%201.7%20(latest)/2/console <https://builds.apache.org/ 
>> <https://builds.apache.org/>
>> job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
>> [3] https://builds.apache.org/job/IvyDE/315/console 
>> <https://builds.apache.org/job/IvyDE/315/console> <
>> https://builds.apache.org/job/IvyDE/315/console 
>> <https://builds.apache.org/job/IvyDE/315/console>>

Re: Jenkins Jobs of Ivy/IvyDE

[Gintautas Grigelionis]

[3]: the path looks wrong, it starts with "\:\:\"
[2]: please check that unpacking of drops puts files into the correct
places (the contents should go into "features" and "plugins" directories of
PDE).

Gintas

2017-06-25 16:57 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

> Hi,
>
> I worked on the Jenkins jobs to make them work.
>
> There was some issues with job dependencies. Following the instructions
> there [1] worked.
> I have made the Ivy Job also build the snapshot-bin, like the nightly.
> Maybe now the nightly is redundant.
> I made the Ivy-checks build work, some https changed in favor of http.
> The test matrix is now separated into two builds now, since no Ant
> installation is common for both Windows and Ubuntu. They are both testing
> JDK7 and JDK8.
> The IvyDE job is no longer downloading Ivy’s jar via a hard coded http
> url. It is relying now on a plugin which copies artifacts around.
>
> There are still some error though, most probably not related to the
> Jenkins configuration:
> - the Windows build of Ivy is broken, the retrieve doesn’t work [2].
> - the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is
> reproductible locally.
>
> I’ll look at the IvyDE updatesite job when the build of IvyDE will be
> fixed.
>
> Nicolas
>
> [1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization <
> https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>
> [2] https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,
> jdk=JDK%201.7%20(latest)/2/console <https://builds.apache.org/
> job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
> [3] https://builds.apache.org/job/IvyDE/315/console <
> https://builds.apache.org/job/IvyDE/315/console>
>
>

Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

Hi,

I worked on the Jenkins jobs to make them work.

There was some issues with job dependencies. Following the instructions there 
[1] worked.
I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
now the nightly is redundant.
I made the Ivy-checks build work, some https changed in favor of http.
The test matrix is now separated into two builds now, since no Ant installation 
is common for both Windows and Ubuntu. They are both testing JDK7 and JDK8.
The IvyDE job is no longer downloading Ivy’s jar via a hard coded http url. It 
is relying now on a plugin which copies artifacts around.

There are still some error though, most probably not related to the Jenkins 
configuration:
- the Windows build of Ivy is broken, the retrieve doesn’t work [2].
- the IvyDE is failing to resolve the OSGi metadata of Ivy [3]. It is 
reproductible locally.

I’ll look at the IvyDE updatesite job when the build of IvyDE will be fixed.

Nicolas

[1] https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization 
<https://cwiki.apache.org/confluence/display/INFRA/Job+Authorization>
[2] 
https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console
 
<https://builds.apache.org/job/Ivy-tests-Windows/OS=Windows,jdk=JDK%201.7%20(latest)/2/console>
[3] https://builds.apache.org/job/IvyDE/315/console 
<https://builds.apache.org/job/IvyDE/315/console>

Re: Jenkins build is back to normal : IvyDE-updatesite #787

[Gintautas Grigelionis]

Great! Still, the build still uses the pretty old Eclipse 3.7.1, and AFAICS
the newer releases do not include drops, so some other dependency
resolution mechanism will be necessary should for example we start
discussing GEF 4+.

2017-05-17 20:48 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>:

> The build was broken because Ant was requiring a JDK 8. So I have setup
> the build to use the latest JDK 8.
>
> > Le 17 mai 2017 à 20:31, Apache Jenkins Server <jenk...@builds.apache.org>
> a écrit :
> >
> > See <https://builds.apache.org/job/IvyDE-updatesite/787/display/redirect
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins build is back to normal : IvyDE-updatesite #787

[Nicolas Lalevée]

The build was broken because Ant was requiring a JDK 8. So I have setup the 
build to use the latest JDK 8.

> Le 17 mai 2017 à 20:31, Apache Jenkins Server <jenk...@builds.apache.org> a 
> écrit :
> 
> See <https://builds.apache.org/job/IvyDE-updatesite/787/display/redirect>
> 


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

Jenkins Builds

[Stefan Bodewig]

Hi all

build.apache.org has been reconfigured to use Ant 1.10.1 as "Ant
(latest)", this is why the 1.9.x builds running on JDK < 1.8
failed. I've just changed the jobos to explicitly use Ant 1.9.9.

Stefan

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

AW: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157

[jhm]

I dont have any idea why this build doesnt work.
Have tried changing the label from (each) ubuntu to every ubuntu without H12 
(where the last builds were).

Finally I "copied" the job (without email-notification)
https://builds.apache.org/job/Ivy-tests-matrix
https://builds.apache.org/job/Ivy-tests-matrix/jdk=JDK%201.5%20(latest)/lastBuild/console

Build runs now ...


The original matrix job had 2 axes:
- JDK: JDK 1.5 (latest)
- Slaves: Name=label


I couldnt add the slaves-axes ...


Please check. :)

Jan


> -Ursprüngliche Nachricht-
> Von: Maarten Coene [mailto:maarten_co...@yahoo.com.INVALID]
> Gesendet: Mittwoch, 9. November 2016 09:19
> An: Ant Developers List
> Betreff: Fw: Build failed in Jenkins: Ivy-tests » JDK 1.5
> (latest),Windows #157
> 
> Anyone an idea why this is failing and can someone fix it?I would try
> to do this myself, but I don't have the necessary permissions on
> Jenkins.
> regards,Maarten
> 
> 
> 
> - Doorgestuurd bericht -
>  Van: Apache Jenkins Server <jenk...@builds.apache.org>
>  Aan: notificati...@ant.apache.org
>  Verzonden: woensdag 9 november 2:11 2016
>  Onderwerp: Build failed in Jenkins: Ivy-tests » JDK 1.5
> (latest),Windows #157
> 
> See <https://builds.apache.org/job/Ivy-
> tests/jdk=JDK%201.5%20(latest),label=Windows/157/changes>
> 
> Changes:
> 
> [maartenc] Fix NullPointerException in dependencytree with no
> dependencies
> 
> --
> Started by upstream project "Ivy-tests" build number 157 originally
> caused by:
>  Started by upstream project "Ivy" build number 527  originally caused
> by:
>   Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on windows-2012-2 (Windows) in workspace
> <https://builds.apache.org/job/Ivy-
> tests/jdk=JDK%201.5%20(latest),label=Windows/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes
> from the remote Git repository  > git config remote.origin.url
> https://git-wip-us.apache.org/repos/asf/ant-ivy.git # timeout=10
> Cleaning workspace  > git rev-parse --verify HEAD # timeout=10
> Resetting working tree  > git reset --hard # timeout=10  > git clean -
> fdx # timeout=10  > git submodule foreach --recursive git reset --hard
> # timeout=10  > git submodule foreach --recursive git clean -fdx #
> timeout=10 Fetching upstream changes from https://git-wip-
> us.apache.org/repos/asf/ant-ivy.git
>  > git --version # timeout=10
>  > git -c core.askpass=true fetch --tags --progress https://git-wip-
> us.apache.org/repos/asf/ant-ivy.git +refs/heads/*:refs/remotes/origin/*
> Checking out Revision 7217b9d270e31fe1e68803c8e25b0a03869f1556
> (refs/remotes/origin/master)  > git config core.sparsecheckout #
> timeout=10  > git checkout -f 7217b9d270e31fe1e68803c8e25b0a03869f1556
>  > git rev-list f463013f34a5c5c61b7dba22c9ed4096fbd3b218 # timeout=10
> > git remote # timeout=10  > git submodule init # timeout=10  > git
> submodule sync # timeout=10  > git config --get remote.origin.url #
> timeout=10  > git submodule update --init --recursive
> ERROR: Cannot find executable from the chosen Ant installation "Ant
> (latest)"
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> 
> 
> 


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

Fw: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157

[Maarten Coene]

Anyone an idea why this is failing and can someone fix it?I would try to do 
this myself, but I don't have the necessary permissions on Jenkins.
regards,Maarten


 
- Doorgestuurd bericht -
 Van: Apache Jenkins Server <jenk...@builds.apache.org>
 Aan: notificati...@ant.apache.org 
 Verzonden: woensdag 9 november 2:11 2016
 Onderwerp: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157
   
See 
<https://builds.apache.org/job/Ivy-tests/jdk=JDK%201.5%20(latest),label=Windows/157/changes>

Changes:

[maartenc] Fix NullPointerException in dependencytree with no dependencies

--
Started by upstream project "Ivy-tests" build number 157
originally caused by:
 Started by upstream project "Ivy" build number 527
 originally caused by:
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windows) in workspace 
<https://builds.apache.org/job/Ivy-tests/jdk=JDK%201.5%20(latest),label=Windows/ws/>
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/ant-ivy.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
 > git submodule foreach --recursive git reset --hard # timeout=10
 > git submodule foreach --recursive git clean -fdx # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/ant-ivy.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 7217b9d270e31fe1e68803c8e25b0a03869f1556 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 7217b9d270e31fe1e68803c8e25b0a03869f1556
 > git rev-list f463013f34a5c5c61b7dba22c9ed4096fbd3b218 # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule update --init --recursive
ERROR: Cannot find executable from the chosen Ant installation "Ant (latest)"
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?


   

Jenkins Matrix Builds

[Stefan Bodewig]

Hi all

it looks as if the configuration for Windows builds will now need a
different version of Ant - something with "Windows" in its name - which
can't be configured via the matrix setup at all.

Given the 1.9.x build already contains totally separate JDKs for Ubuntu
and Windows I'll go ahead and split the two Matrix builds we've got into
four.

Stefan

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

Trying to get saner Jenkins setup

[Stefan Bodewig]

Hi

the failing builds you've see today come from me trying to console our
Matrix build with
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix

I'm starting with the jobs for 1.9.x and will modify master once/iff I
get it working for 1.9.x.

We are now using the "JDK 1.X (latest)" entries on Ubuntu and the
"Windows only" JDKs on Windows. Unfortuantely only 1.5 seems to work on
Windows. I'll try to get this figured out with the help of the builds
list. I also added jdk9 but removed it again after it ran into some sort
of configuration hiccup as well.

Stefan

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