Feature Request

What challenge are you facing?

We have developers and Concourse admins that would like to have more details about their/any pipeline executions. Specifically, information about what tasks are currently executing for each job, where they are executing (which worker), when they started/finished executing, their last duration, what they are doing if they are not executing (the things that happen between the time one task executes and the next task executes), some information about their current inputs/outputs are, etc

A Modest Proposal

Expand fly -t <target> jobs -p <pipeline> to take a -j <job> flag that will show these sorts of details for a specific job. Possibly even a -verbose flag to go with -p <pipeline> to show these details for all the pipeline's jobs at the same time. Additionally allow for a -t <task> option for -j <job> which will drill down even further and just show the details for a particular task.

Bug Report

Bug reports are pretty free-form; just replace this with whatever. You can also help us triage the issue by including steps to reproduce, expected results, and the actual result. Help us help you!

The following can also be handy:

• Concourse version:
• Deployment type (BOSH/Docker/binary):
• Infrastructure/IaaS:
• Browser (if applicable):
• Did this used to work?