On Sun, Apr 8, 2012 at 4:18 PM, Graham Binns <[email protected]> wrote: > It occurred to me that I've not actually sent anything out the script > to automate test runs, so here's something:
> Further things we could do with the script: > > - Make it monitor the build, capture the final output > and tear down the environment when it's finished > (I tried this, but of course destroy-environment > is interactive, and piping `yes` to it caused it to > eat the CPU. That's curious. I have a script that pipes "yes" into destroy-environment and it works. > - ??? Suggestions welcome. The juju command really needs a --config argument so you don't have to modify the user's config. -- Benji York -- Mailing list: https://launchpad.net/~yellow Post to : [email protected] Unsubscribe : https://launchpad.net/~yellow More help : https://help.launchpad.net/ListHelp
