provisionr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <>
Subject [jira] [Resolved] (PROVISIONR-46) Fix Jenkins Build
Date Wed, 10 Jul 2013 08:59:48 GMT


Andrei Savu resolved PROVISIONR-46.

       Resolution: Fixed
    Fix Version/s: 0.5.0-incubating

Seems to be working fine now:

Thanks again Rahul for investigating this one! 
> Fix Jenkins Build 
> ------------------
>                 Key: PROVISIONR-46
>                 URL:
>             Project: Provisionr
>          Issue Type: Improvement
>            Reporter: Rahul Sharma
>            Assignee: Rahul Sharma
>             Fix For: 0.5.0-incubating
>         Attachments: PROVISIONR-46-Fix-Jenkins.patch
> The failing build is due to the non-standard maven repository. The build is made on a
ubuntu-slave which has its own local repository at a custom location. This setting is passed
in the build eg  in d build 45 the local repos was set as :
>        -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1
> We need to pass this setting to pax exam which is responsible for determining maven artifact.
The way to do this is to pass this *maven.repo.local* variable to *org.ops4j.pax.url.mvn.localRepository*.
This should be done in the profile that builds on jenkins.
> Karaf has the similar situation the have a test case [1] which looks for artifact using
pax. Thus they build a profile in their pom.xml [2] which can pick the local repo location
and set the required varibale. Also it is easy to reproduce on local just enable the <localRepositry>
tag in maven/conf/settings.xml.
> [1]
> [2]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message