On Fri, Dec 13, 2013 at 10:09:44AM -0600, Andy Doan wrote: > Public apology - I confused the dates for this. I have questions for > something next week: > > * developing/updating hooks > The most efficient process I have is a joke. I add a "raise > RuntimeError" to the end of the hook I want to work on. I then run > my juju-deployer. This causes the step I'm interested in to fail. I > log into the box and edit the hook on that system (keeping the hack > for the exception). I then run "juju resolved --retry <unit>" over > and over until the hook works how I want.
juju debug-hooks Might be helpful here if you're not already using it. You basically get dropped into a shell with the hook environment all set up. You just run: hooks/<cmd> to run the hook code. Hope this helps, Joe -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
