Yes - I am with Iyad - having more context would probably help :). You
can inject job_wrapper related stuff into tool execution in a very
round about way perhaps by creating a dynamic job destination that
consumes the job_wrapper and then creates a job destination with
enviornment variables set to whatever it is you job needs. But that
solution is not very portable or simple - I can try to walk through
the steps in more detail though if it would be useful.
On Mon, Oct 6, 2014 at 9:28 PM, Kandalaft, Iyad
Tell us what you are trying to do and maybe someone might know the
way to solve it. It could be easier, the same, or more difficult than you imagined.
Microbial Biodiversity Bioinformatics
Science & Technology Branch
Agriculture & Agri-Food Canada
Iyad.Kandalaft(a)agr.gc.ca | (613) 759-1228
From: galaxy-dev-bounces(a)lists.bx.psu.edu [galaxy-dev-bounces(a)lists.bx.psu.edu] on behalf
of Alexandre Defelicibus [adefelicibus(a)gmail.com]
Sent: October 6, 2014 4:50 PM
Subject: [galaxy-dev] Job wrapper object
I'm developing some tools on my Galaxy instance and I need to get some information
about the job that a tool creates.
The question is, how can I have a job_wrapper object in my tool wrapper? I tried to use
the reserved variable $__app__, but I got errors.
I couldn't import and use the galaxy lib in order to get the job information.
Could someone show me the correct way to do that, with some examples?
I appreciate all the help.
Mestrando em Bioengenharia
Programa de Pós-Graduação em Bioengenharia
Universidade de São Paulo - USP
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:
To search Galaxy mailing lists use the unified search at: