GitHub PushEvent at 2014-05-13 15:45:41
Repository: galaxy-central
Actor: jmchilton
Payload: {"shas":[["6e5a241db7a5fb0379c2b2b09cc5cb3e1a881532","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Implement serializable class that can describe full dependency context for remote dependency resolution.\nPreviously LWR jut serialized tool requirements, by transitioning to this class LWR should be able to resolve tool shed installed packages as well - requiring the additional repository and tool dependency context.","John Chilton",true],["13d417f81dc2f98d1feedc6dff38d0590244feb2","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Update LWR client through LWR changeset 9fb7fcb.\nAmong other smaller fixes, this update causes the LWR client/runner to pass more tool dependency context through to the remote LWR server when `dependency_resolution` is set to `remote`. This additional context allows tool shed packages to be resolved remotely (i.e. allows proper use of ToolShedPackageDependencyResolver on the remote LWR server).\n\nIt remains the responsibility of the deployer to ensure identical versions of tool shed packages are installed on the remote LWR server and the local Galaxy instance.","John Chilton",true],["f2c173bb10f267ace5581b6822d11752042e6e4e","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Improvements to LWR documentation.\nAdd separate examples for MQ driven stuff - this should clear up things and make it clear which new parameters are required when using message queue and which are no longer required. Add more documentation for remote dependency resolution. Document rewrite_parameters.","John Chilton",true],["882054a168617c94cc629141b969a8eb8cf29579","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Ensure new_file_path exists before set_metadata.py generates metadata.\nThis directory is required to exist but usually unneeded because Galaxy creates this directory on startup. However, when setting metadata remotely with the LWR that remote Galaxy instance may have never been started and this directory may not exist.","John Chilton",true],["c2722ef02eea4fd3783a35142c22b46054b5e652","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Remove no longer valid log message.","John Chilton",true],["121dc981fe49a1bde47948025e58397959fe2229","e361bfc8c8526c02f5efd3e71aa466615402f28f@gmail.com","Optimize/correct LWR remote metadata generation for working directory outputs.\nPreviously I was attempting to mimic Galaxy's behavior of copying these files to a fixed output location after execution on the remote server before setting metadata. This was an un-needed copy since it appears to easier to just send the metadata generation code the expected path on the working directory.","John Chilton",true]],"size":6,"ref":"refs/heads/master","head":"121dc981fe49a1bde47948025e58397959fe2229"}