[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536492#comment-14536492 ] Andrea Del Bene commented on BUILDS-71: --- Great! Well done Martin! > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536494#comment-14536494 ] Martin Grigorov commented on BUILDS-71: --- I've worked it around by setting manually M2_HOME/bin in the PATH. Works fine now for us but there is definitely something wrong with the Maven setup at that machine. > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536496#comment-14536496 ] Andrea Del Bene commented on BUILDS-71: --- Yes indeed. I agree. > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536504#comment-14536504 ] Gavin commented on BUILDS-71: - The default maven installed is 2.2.1 so you have to explicitly set your MAVEN OPTS for choosing another one , there are plenty all stored in:- gmcdonald@hemera:~$ ls -al /home/buildslave18/slave18/tools/maven/ total 56 drwxr-xr-x 14 buildslave18 buildslave18 4096 Apr 26 20:25 . drwxr-xr-x 22 buildslave18 buildslave18 4096 Apr 29 2012 .. drwxr-xr-x 6 buildslave18 buildslave18 4096 Aug 31 2009 apache-maven-2.0.10 drwxr-xr-x 6 buildslave18 buildslave18 4096 Nov 22 2007 apache-maven-2.0.8 drwxr-xr-x 6 buildslave18 buildslave18 4096 Jan 30 2009 apache-maven-2.0.9 drwxr-xr-x 6 buildslave18 buildslave18 4096 Feb 1 2011 apache-maven-2.2.1 drwxr-xr-x 6 buildslave18 buildslave18 4096 Aug 26 2011 apache-maven-3.0.2 drwxr-xr-x 6 buildslave18 buildslave18 4096 Feb 4 2013 apache-maven-3.0.3 drwxr-xr-x 6 buildslave18 buildslave18 4096 Dec 31 2012 apache-maven-3.0.4 drwxr-xr-x 6 buildslave18 buildslave18 4096 Sep 17 2013 apache-maven-3.1.1 drwxr-xr-x 6 buildslave18 buildslave18 4096 Feb 14 2014 apache-maven-3.2.1 drwxr-xr-x 6 buildslave18 buildslave18 4096 Apr 26 20:24 apache-maven-3.2.5 drwxr-xr-x 6 buildslave18 buildslave18 4096 Apr 26 20:24 apache-maven-3.3.1 lrwxrwxrwx 1 buildslave18 buildslave18 18 Apr 26 20:25 latest -> apache-maven-3.2.5 lrwxrwxrwx 1 buildslave18 buildslave18 18 Oct 30 2011 latest2 -> apache-maven-2.2.1 lrwxrwxrwx 1 buildslave18 buildslave18 18 Apr 26 20:25 latest3 -> apache-maven-3.2.5 drwxr-xr-x 5 buildslave18 buildslave18 4096 Jun 25 2007 maven-1.1 > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536505#comment-14536505 ] Gavin commented on BUILDS-71: - Would you say this issue is resolved now? > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536516#comment-14536516 ] Tobias Soloschenko commented on BUILDS-71: -- So my presumption where right about the maven path. Thanks a lot [~martin-g] that you found out a workaround! :-) > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536517#comment-14536517 ] Tobias Soloschenko commented on BUILDS-71: -- I think this ticket can considered as resolved, because maven 3.1.0 is used by the wicket master branch and it is building, now. > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (BUILDS-79) Please make latest Gradle (2.4) available on Jenkins builds slavs
Roman Shaposhnik created BUILDS-79: -- Summary: Please make latest Gradle (2.4) available on Jenkins builds slavs Key: BUILDS-79 URL: https://issues.apache.org/jira/browse/BUILDS-79 Project: Infra Build Platform Issue Type: Improvement Components: Jenkins Reporter: Roman Shaposhnik Given that some of the Incubating gradle plugins have requirements for latest gradle it would be nice to have it available. While it is true that gradlew can be used as a workaround to dynamically load the latest release the Jenkins gradle integration provides a few nice capabilities that are not available with gradlew -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-71) Update maven version to 3.1.0 or highier
[ https://issues.apache.org/jira/browse/BUILDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536836#comment-14536836 ] Martin Grigorov commented on BUILDS-71: --- [~ipv6guru] I think there is 'mvn' in the PATH that led to this problem. You can check with: $ ls -la `which mvn` I think it is a link to some of the listed above. I'd suggest to remove it from there and update PATH to be: $M2_HOME/bin:$PATH Please close the ticket. > Update maven version to 3.1.0 or highier > > > Key: BUILDS-71 > URL: https://issues.apache.org/jira/browse/BUILDS-71 > Project: Infra Build Platform > Issue Type: Bug >Reporter: Andrea Del Bene >Assignee: Gavin > > I'm having a problem with CI and my project, Apache Wicket. The build is > failing do to Maven version available on the build machine. Wicket master > branch requires a version >= 3.1.0 in order to build successfully. At the > moment CI can not work due to this limitation : > http://ci.apache.org/builders/wicket-master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-77) install shellcheck on jenkins slaves
[ https://issues.apache.org/jira/browse/BUILDS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536993#comment-14536993 ] Allen Wittenauer commented on BUILDS-77: Our test bits are seeing it, so yes, it appears to be there. Thanks! > install shellcheck on jenkins slaves > > > Key: BUILDS-77 > URL: https://issues.apache.org/jira/browse/BUILDS-77 > Project: Infra Build Platform > Issue Type: New Feature > Components: Jenkins >Reporter: Allen Wittenauer >Assignee: Andrew Bayer > > Would it be possible to get shellcheck installed on the Hadoop jenkins boxes > so that we can use it as part of patch testing? > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Gradle-based projects -SNAPSHOT artifact publishing
After some sleuthing around I finally figured out a way to automate it so that Gradle can push from our Jenkins slaves as easy as Maven builds. Here's the patch: https://issues.apache.org/jira/browse/GEODE-19 that now honors settings.xml because of a combination of two plugins: maven-publish and maven-publish-auth Shall we add this to publishing FAQ around Maven artifacts? Thanks, Roman. On Thu, May 7, 2015 at 9:19 PM, Giridharan Kesavan wrote: > Roman, > > To my knowledge gradle doesn’t honor settings.xml. Most of the gradle > projects that I work on > I use the username and plain txt password by implementing the > MavenDeployer interface. > > http://gradle.org/docs/current/javadoc/org/gradle/api/artifacts/maven/Maven > Deployer.html > > I would be more than happy to learn, if someone knows a better/easier way > of doing it. > > > > > > > On 5/7/15, 1:25 PM, "Roman Shaposhnik" wrote: > >>Hi! >> >>I'm used to the Maven projects just inhering from >>top level ASF pom and automagically getting all >>the right things in place to be able to do mvn publish >>on any of our Jenkins slaves. >> >>What's the easiest way to achieve that same level >>of integration for gradle-based projects? >> >>Thanks, >>Roman.
