On 24 February 2012 09:19, Olivier Lamy <ol...@apache.org> wrote: > 2012/2/24 sebb <seb...@gmail.com>: >> On 24 February 2012 03:08, Benson Margulies <bimargul...@gmail.com> wrote: >>> On Thu, Feb 23, 2012 at 8:51 PM, sebb <seb...@gmail.com> wrote: >>>> Do any of the build systems support deployment of Maven snapshots? >>>> >>> >>> yes. >>> >>>> If so, how can this be added to a build? >>> >>> In Jenkins by ticking the box in the job config or adding 'deploy' to >>> the list of maven goals. >> >> Which box is that? >> If it is "Publish artifacts to SCP Repository" then there does not >> seem to be an SCP site; also it's not clear what the target path >> should be. >> >> [The build does not use Maven] > > In such case, you must use ant (if your build is ant based) maven > tasks to deploy snapshots to > https://repository.apache.org/content/repositories/snapshots (server > id to use: apache.snapshots.https ). > Jenkins nodes have the necessary ~/.m2/settings.xml (normally :-) ).
The build uses Ant, but does not use the ant maven tasks - are those installed on Jenkins nodes? Alternatively, is there a standard location or env variable that points to the Maven installation on Jenkins nodes? The script currently uses Java to run Maven as per [1] This relies on finding the maven home directory via the M2_HOME variable, which does not seem to be set on Jenkins. [1] http://maven.apache.org/ant-tasks/examples/mvn.html#Using_the_Java_Task > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy
