Hello all, I'm looking at how to automatically script setting up a Galaxy instance with selected tools with dependencies as part of automated testing [*].
Can the Galaxy API be used to run the dependency instructions in a tool_dependencies.xml file (without using a Tool Shed)? Or more generally, can the Galaxy API be used to install a Tool Shed package from disk (i.e. point it at the files which would normally be uploaded to a Tool Shed)? Or, for an automated installation of local tools must I first setup a local Tool Shed and upload the tools there? Thanks, Peter [*] I'm using the TravisCI system for automated testing of my Galaxy tools now hosted on GitHub, which works by running the tests on a clean virtual machine: http://blastedbio.blogspot.com/2013/09/using-travis-ci-for-testing-galaxy-tools.html This means I need to automate the installation of Galaxy (easy), the tools I wish to test and their dependencies. This configuration would be less effort (and a more useful test) if it could mimic tool and dependency installation from the Tool Shed by reading my dependency XML files. ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
