Hi Danushka,

You have to set the "class" attribute of the "localRepository" element of
the job config to
"org.wso2.carbon.appfactory.jenkins.extentions.AFLocalRepositoryLocator" to
use the tenant specific m2 Repo as in [1]. Then when a build is triggered,
"locate"[2][3] method of the AFLocalRepositoryLocator will be invoked and
it will choose the .m2 repo location accordingly

[1]
https://github.com/wso2/product-af/blob/master/modules/components/org.wso2.carbon.appfactory.core/src/main/resources/jenkins-config.xml#L104
[2]
https://github.com/wso2/product-af/blob/master/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/extentions/AFLocalRepositoryLocator.java#L49
[3]
http://buddycode.blogspot.com/2015/06/jenkins-deployment-in-wso2-appfactory.html

Regards,
Samith

On Sat, Jul 18, 2015 at 6:30 PM, Danushka Fernando <[email protected]>
wrote:

> Hi All
>
> Currently I am working on [1]. While working on it I faced $subject.
>
> In AF we are using jenkins as the default build server and for each tenant
> we point to a custom repository (maven repository) location so all tenant
> artifacts are installed their own repository. But when I build the
> Resources Project with these settings it install the artifacts to the basic
> .m2 folder of the afpuppet user (owner of the jenkins process). I guess
> this is a bug in some plugin we developed. Can some one shed some light on
> this since I am stuck on this.
>
>
> [1] [Architecture] [AF] Adding CAR application type to App Factory
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards

Samith Dassanayake
Software Engineer | Cloud TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +947 76207351
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to