[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Best practices for deploying to a remote virgo instance
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Mon, 2 Jul 2012 10:50:47 +0100
- Delivered-to: firstname.lastname@example.org
I suggest you ask this on the Virgo community forum as that's where most users hang out and you'll be able to compare notes with more people there.
There is some info in the User Guide about configuring a Virgo repository to use a directory in Maven layout. The only experience we've had of that is a bit negative - if you include a large number of Spring's optional dependencies in such a repository, Virgo tries to download and install them all.
But your requirement sounds a bit different as it requires automatic deployment to Virgo when one of your bundles changes. You could adopt the pull approach by placing your bundles in a watched repository and installing them using the deployer mbean and the repository: URL scheme. Clearly you could automate some of this with p2, but only for installing bundles into the kernel as p2 will only do initial provisioning of user region bundles.
On 1 Jul 2012, at 21:44, Anthony Bargnesi wrote:
> I'm interested in automating deployment of bundles into virgo instances. For instance I would like to run a testing container that I will continuously deploy to when bundles are updated. My build environment uses maven/artifactory and not the eclipse p2 repository.
> I would be happy either deploying bundles from maven to virgo or pulling bundles into virgo from maven. Is this possible or do I need to switch to p2?
> Are there best practices followed by others in a maven/virgo situation?
> Thanks for the help,
> Anthony Bargnesi
> virgo-dev mailing list