[rules-users] continuous integration of rule assets via jenkins to guvnor?

I'd like to get a quick sanity check on best practices... I'm working on a project where, by policy, all assets (including drl's, bpmn files, etc) must be built, tested and packaged by a Jenkins server. Rule assets are structured within a project that also includes non-rule assets. As is quite common, the primary system of record for these assets is an SCM like svn or git, and that's what our Jenkins box talks to. However, for the rule stuff specifically, we're also using Guvnor's drools-repository to package the assets into a knowledge base, which is referenced jBPM's process engine in the runtime. The plan is to have several Guvnor environments running with parity to development, QA, UAT and production setups. However, we're having a very hard time figuring out how best to sync our rule assets to these various repositories as part of an automated release. To the best of my understanding, rule assets are deployed to a Guvnor instance file-by-file via WebDAV. One can also upload JARs for POJOs, but DRLs, BPMN, DSL files need to be synced individually. Is this the case? And, if so, how do other groups handle continuous integration and deployment of assets coming from external SCMs? Btw, I came across aware of a Maven plugin which seems to do this sort of piece-by-piece deployment: https://github.com/awaterma/drools-guvnor-plugin So we could certainly port this sort of functionality to our own build toolchain, but it seems like a lot of work so I'm hoping for a better way. -- View this message in context: http://drools.46999.n3.nabble.com/continuous-integration-of-rule-assets-v... Sent from the Drools: User forum mailing list archive at Nabble.com.