When a job is scheduled, it shows as waiting for agent, as above. It shows as a yellow lozenge in the pipeline.
Our context
We auto-scale our agent queues up and down with demand. This means at any point, there might not be an agent available for a job, but there shortly will beif configuration is correct and an agent ever existed that could satisfy the job in the past.
Improvement possibilities
Show how many agents exist right now that could run this job
Set the expectation that the job can be run, just not right now - user-be-patient
If no agents exist right now that could run this job and no agents have ever in the past existed that could run this job, show some icon/note to that effect.
Set the expectation that the job will block until agents become available or configuration is fixed - user-fix-thing
These features would be a fantastic improvement for new users/those coming from platforms where there is more tight-coupling between a "master" and a "worker". +1 all around.
What happens now
When a job is scheduled, it shows as waiting for agent, as above. It shows as a yellow lozenge in the pipeline.
Our context
We auto-scale our agent queues up and down with demand. This means at any point, there might not be an agent available for a job, but there shortly will be if configuration is correct and an agent ever existed that could satisfy the job in the past.
Improvement possibilities