Check out the drools-ant jackrabbit migration task
http://blog.athico.com/2011/03/using-drools-ant-to-migrateback-up.html.
It migrates the entire repository and you would not loose your rule
assets version history, metadata, snapshots, existing user permissions
etc. You may also look into setting up a jackrabbit cluster
configuration for your different prod, dev, qa guvnor instances:
http://blog.athico.com/2011/01/configuring-multiple-guvnor-instances.html.
Overall there is no means to move only parts of your jcr repo currently
but you do have available built-in/custom selectors which can be used to
determine what rule assets are test/qa/prod assets.
Thanks.
Tihomir
On 3/31/11 9:32 AM, Dean Whisnant wrote:
Hello,
My Guvnor development environment has 2 servers, DEV and TEST. A typical lifecycle
includes Business Analysts and developers authoring rules on DEV in multiple packages and
then doing releases to the TEST server for our QA folks to verify our work. Eventually,
we will also bring our production server into the mix once QA is complete.
It is somewhat painful to move rules between servers as the only 100% successful method I
have is to use guvnor's export/import feature that exports the entire repository and
the restores it in my TEST environment. I dislike the opportunity that someone has
changed or is in the middle of changing a rule in package B on the DEV server and when I
deploy to TEST changes for package A, the package B rules move as well.
Does anyone have a reliable method of moving individual rules between servers? How about
moving just the contents of one package?
I downloaded and used a tool called Cyberduck and it seemed to do things well, but when
moving from one server to another we lose the categories on the individual rules.
Any thoughts are appreciated.
Thanks
Dean
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users