Change the way galaxy does when a job is running

[FredericBGA]

I think that my users are impatient peoples :)

Right now, when a job is not finished, clicking of the eye icon will display a blank page.

Do you think it could be possible to do something like that:

• I would like to know if galaxy could catch this (job is still running) and then, clicking on the eye icon could launch another action (a user defined python script?)
• In my mind this script could: displays the result of a qstat command, display a tail -n of the output dataset etc.
• If the script is not present (or if a new option in galaxy.ini is not set), the current behaviour doesn't change.

It would be perfect if the script could access the name of the output dataset, the tool name and even the id of the job launched through the scheduler!

thank you for sharing your comments and ideas.

[osallou]

My 2 cents.... As jobs can be executed on very different subsystems (sge, slum, docker, ...) the "user" script would have to be executed on a remote server (not a good idea to execute anything on galaxy server itself but for dev/demo), so it would not be easy to do so, once job is scheduled by the configured system on a remote node. And user script would need to know what to do depending on scheduler/executor. Furthermore, executing a user defined script would definitly be a security issue/problem...