Project

General

Profile

Idea #3188

Updated by Tom Clegg over 9 years ago

Structural: Summary: 
 * Showing a job should look (nearly) the same as showing a pipeline instance with a single component. Some fields aren't applicable, like component name. Future work may change the CLI tools so jobs never even get submitted except as part of pipelines. 
 * On the pipeline instance page, instead of linking to "job details", make all the details available on the pipeline page. 

 Job summary: 
 * script name 
 * current state (queued, running, finished, failed) 
 * when last changed state 
 * who submitted 
 * progress bar (if running) 
 * live log messages (if running) 
 * number of tasks (total = done + running + todo) 
 * number of task failures (if any) 
 * link to output collection 

 Job details: Details: 
 * repository 
 * script version 
 * parameters (with preview of collections?) 
 * runtime parameters 
 * docker image 
 * timestamps (submit, start, finish, cancel) 
 * elapsed time between submit and cancel/start (or now) 
 * elapsed time between start and cancel/finish (or now) 

Back