This might provide some useful information: <a href="https://community.jboss.org/wiki/PublishDroolsArtifactsFromAProductionEnvironment">https://community.jboss.org/wiki/PublishDroolsArtifactsFromAProductionEnvironment</a><br>
<br><div class="gmail_quote">On 28 June 2012 10:15, Stephen Masters <span dir="ltr"><<a href="mailto:stephen.masters@me.com" target="_blank">stephen.masters@me.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>One option:</div><div><br></div><div><ul><li>Point your production environment at a LIVE snapshot (or whatever you want to call it) instead of LATEST.</li><li>Point your CI build at LATEST.</li><li>On successful completion of the test suite, create a new LIVE snapshot.</li>
</ul></div><div>That way, you can always see the current live version of your rules in Guvnor, and diff them if you need to.</div><div><br></div><div>Steve</div><div><div class="h5"><div><br></div><div><br><br>On Jun 27, 2012, at 03:20 PM, Gustaf Cele <<a href="mailto:gustaf.cele@databyran.se" target="_blank">gustaf.cele@databyran.se</a>> wrote:<br>
<br></div><div><blockquote type="cite"><div><div>Hi Wolfgang!<br> <br> A staging area sounds like a good idea. Would something as simple as this work?<br> <br> KnowledgeAgent stagingAgent = connectToGuvnorAndStartPolling();<br>
KnowledgeBase productionKnowledgeBase = ...;<br> stagingAgent.addEventListener(new DefaultKnowledgeAgentEventListener() {<br> @Override<br> public void beforeChangeSetApplied(BeforeChangeSetAppliedEvent event) {<br> if (allTestsPass()) {<br>
// copy rules from stagingAgent to productionKnowledgeBase, somehow<br> }<br> });<br> <br> ... and in that case, how would I go about the copying part? Is it safe to just save the reference from stagingAgent.getKnowledgeBase() if the agent is configured with drools.agent.newInstance=true?<br>
<br> /g<br> <br> -----Original Message-----<br> From: Wolfgang Laun [mailto:<a href="mailto:wolfgang.laun@gmail.com" target="_blank">wolfgang.laun@gmail.com</a>] <br> Sent: den 27 juni 2012 15:45<br> To: Rules Users List<br>
Subject: Re: [rules-users] Continuous deployment of rules/vetoing changesets<br> <br> Have you considered using a "staged" approach?<br> <br> Rather than forwarding LATEST right into production, have one listener move it into the staging area or not - depending on the tests. The production side listener(s) are directed onto the staging area.<br>
<br> -W<br> <br> <br> <br> On 27/06/2012, Gustaf Cele <<a href="mailto:gustaf.cele@databyran.se" target="_blank">gustaf.cele@databyran.se</a>> wrote:<br> > Hi,<br> ><br> > I have a Guvnor server (5.4.0.Final) which provides rules to a client <br>
> (which itself is an EJB server app) using KnowledgeAgents to get hold <br> > of rule updates. The knowledge agents are started with changeset XMLs <br> > on the classpath which point at my Guvnor instance.<br>
><br> > The KnowledgeAgents are set up thus:<br> ><br> > ResourceFactory.getResourceChangeNotifierService().start();<br> > ResourceFactory.getResourceChangeScannerService().start();<br> > KnowledgeAgent knowledgeAgent =<br>
> KnowledgeAgentFactory.newKnowledgeAgent(agentName);<br> > knowledgeAgent.monitorResourceChangeEvents(true);<br> > Resource resource =<br> > ResourceFactory.newClassPathResource(changeSetResourcePath, getClass());<br>
> knowledgeAgent.applyChangeSet(resource);<br> > ResourceFactory.getResourceChangeNotifierService().start();<br> > ResourceFactory.getResourceChangeScannerService().start();<br> ><br> > And the changesets look like this (xsd stuff removed for brevity):<br>
><br> > <change-set><br> > <add><br> > <resource username="ruleclient" password="hunter2"<br> > basicAuthentication="enabled"<br> ><br> > source="<a href="http://guvnorhost/drools-guvnor/org.drools.guvnor.Guvnor/package/my.package/LATEST" target="_blank">http://guvnorhost/drools-guvnor/org.drools.guvnor.Guvnor/package/my.package/LATEST</a>"<br>
> type="PKG" /><br> > </add><br> > </change-set><br> ><br> > As you can see, we use LATEST because we want continuous deployment of <br> > our rules. Change a rule, build the package, and have the connected <br>
> KnowledgeAgents updated with the new rule. This works very well - a <br> > bit too well, unfortunately. We have a comprehensive test suite, and <br> > every now and then, you'll check in a rule that breaks a test. We want <br>
> to prevent any changes to our rules from being propagated to the <br> > clients until all the tests succeed, and this is where we're stuck.<br> ><br> > We've tried using a KnowledgeAgentEventListener which throws an <br>
> exception when it detects test failures:<br> ><br> > public class VetoListener extends DefaultKnowledgeAgentEventListener {<br> > @Override<br> > public void beforeChangeSetApplied(BeforeChangeSetAppliedEvent<br>
> event) {<br> > if (!allTestsPass()) {<br> > throw new RuntimeException("tests failed, not applying <br> > change set");<br> > }<br> > }<br> ><br> > boolean allTestsPass(){<br> > // Get test results from<br>
> ${guvnor_url}/org.drools.guvnor.Guvnor/package/my.package/LATEST/SCENARIOS<br> > // and check if there were any failures<br> > }<br> > }<br> > // Usage:<br> > knowledgeAgent.addEventListener(new VetoListener());<br>
><br> > This does prevent the new changeset from being applied, but it also <br> > seems to kill the thread polling for new changes entirely. Restarting <br> > the ResourceChange{Scanner,Notifier}Services doesn't help.<br>
><br> > I've also tried modifying the event's changeset (I know you <br> > shouldn't), but it doesn't stop the changes from being applied:<br> ><br> > public void beforeChangeSetApplied(BeforeChangeSetAppliedEvent event) {<br>
> if (!allTestsPass()) {<br> > event.getChangeSet().getResourcesModified().clear();<br> > // ... and clear all the other collections you can get <br> > from<br> > event.getChangeSet()<br> > }<br> > }<br>
><br> > So, what I wonder is if there is any way of preventing a changeset <br> > from being applied to a KnowledgeAgent's knowledge base when there are <br> > failing test scenarios, but which applies updates as soon as all tests <br>
> succeed? More generally, I'm looking for something with fewer manual <br> > steps than run tests-make snapshot-publish, and in particular I want <br> > to ensure you never publish a package when there are tests failing, <br>
> and it should preferably not require any changes outside of Guvnor to <br> > get out new rules to the client app. Any ideas?<br> ><br> > Thanks in advance,<br> ><br> > /g<br> ><br> ><br> _______________________________________________<br>
rules-users mailing list<br> <a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br> _______________________________________________<br> rules-users mailing list<br> <a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div></div></div></div><br>_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br></blockquote></div><br>