On 24 February 2012 15:09, sebb <[email protected]> wrote: > On 24 February 2012 14:37, Olivier Lamy <[email protected]> wrote: >> 2012/2/24 sebb <[email protected]>: >>> On 24 February 2012 09:19, Olivier Lamy <[email protected]> wrote: >>>> 2012/2/24 sebb <[email protected]>: >>>>> On 24 February 2012 03:08, Benson Margulies <[email protected]> wrote: >>>>>> On Thu, Feb 23, 2012 at 8:51 PM, sebb <[email protected]> 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? >> AFAIK nope. (as you use ant what about storing the jar in your project ? ) > > Could do, but was hoping to avoid that, as it's yet another dependenccy. > Also will need to change the build file to use it instead of java. > > However, it might be better in the long run.
If only ... I've been trying to use it to deploy from my PC to the Nexus snapshot repo. However, the first problem is that the plugin seems to treat encrypted passwords as if they were normal passwords. [Looks like http://jira.codehaus.org/browse/MANTTASKS-177 which has yet to be addressed after 2 years] That's a blocker as far as I'm concerned. I did try using plain text password, but that failed with error code 400 - not sure what is going on there. [Bad password gives 401, so I know it is not that] So basically no go unless I can find a way to determine the location of maven home so I can use the real maven. >>> >>> 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. >> Jenkins doesn't set this env var. As users are free to use different >> maven versions. >> So it's define when you choose a maven version for your build. > > Which of course is not done for Maven builds. > >>> >>> [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
