Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Objects: Wait on jobs instead of datasets #171

Open
jmchilton opened this issue Nov 1, 2015 · 4 comments
Open

Objects: Wait on jobs instead of datasets #171

jmchilton opened this issue Nov 1, 2015 · 4 comments

Comments

@jmchilton
Copy link
Member

In general it is better to wait on jobs instead of datasets when running tools and workflows - in case tools don't have any dataset outputs and to ensure all extra files have been captured at the end of the execution (I think Galaxy may mark the dataset as complete before extra files have been collected, jobs are marked as complete only at the very end).

@nsoranzo
Copy link
Member

nsoranzo commented Nov 2, 2015

Would be good, but how can we get the job id from the run tool/workflow API calls?

@jmchilton
Copy link
Member Author

Running a tool returns a list of jobs corresponding to the execution, workflow execution returns a workflow invocation - once the invocation has reached a state of scheduled - all the invocation steps corresponding to actual jobs should have a job_id. So workflows really need wait on both the invocation to be fully scheduled and then each job to be complete - this invocation step information is exposed as part of #170.

@nsoranzo
Copy link
Member

nsoranzo commented Nov 2, 2015

So this can be done only for Galaxy release_15.03 or later, correct?

@jmchilton
Copy link
Member Author

I'm not exactly sure, something in that time frame though yes. May be able to make 15.01 or 14.10 work also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants