... per my discretion as BDFN (see Project Goverance for more information https://github.com/galaxyproject/pulsar/blob/master/docs/organization.rst).

Thanks for the continued awesome work on all things Galaxy @mvdbeek, your contributions rock.

Use managers defined in job destination parameters

Fix for locating cli shell/job plugins

The path to the CLI job/shell plugins was build based on the current working
directory, but this would not work if pulsar had been installed into a
virtualenv. Instead we infer the package path with inspect.getsourcefile().

and log a warning.

See https://pypi.python.org/pypi/pulsar-galaxy-lib.

Allow per-manager job directories.

Update: Rebased on to the latest master and documentation for this feature in docs/job_managers.rst and linked to this general manager configuration information from app.yml.sample (per excellent request of @mvdbeek).

If manager name was specified in the destination parameters, include the
managers/<manager_name> route in the url.

Ensure destination directories exist when copying files

Fail jobs that error during job submission

Previously jobs that failed to submit (bad resource requests, malformed
scripts, no qsub available, staging problems) would remain in waiting status
until pulsar was restarted.

for the queued_cli manager.

Fix PBS status reporting

Without this commit only very short jobs completed successfully, because the
status was always set to complete. This was because the status returned by
qstat contains leading spaces before the `job_state = Q` part, so I'm adding a
`.strip()`.

More Progress on an Embedded Pulsar Runner

Pulsar has to be a little smarter than I assumed in 09f7ec3e because it writes out job metrics on the server.

Working directory is below metadata directory in Galaxy 16.04 - so need to handle that.

 - When client uploads files, log them.

[WIP] Metadata directory