Given an agent setup for multiple pipelines
When I visit https://buildkite.com/organizations//a/ for the agent
Then I see the piplines that the agent is enrolled in whether or not the agent is currently running jobs for that pipeline
Given an agent setup for no pipelines
When I visit https://buildkite.com/organizations//a/ for the agent
Then “no pipelines for this agent currently” should be indicated somehow.
Which Agents are paused deliberately
Note: I think “stop” functionality is insufficient as it can’t restarted from the same central UI. Better rename that “kill”, and add pause-resume to the agent. I’m taking a wild guess that an service written in GoLang on Mac/Lin/Win that’s only waiting on a “resume” command and doing no other activity has a minimal overhead to the system.
Which agents are offline but previously eligible for jobs.
Apparent disconnects that are unintended and called out from a dashboard for agents.
This is actually something we’ve been looking into solving recently - unfortunately due to the structure of the data (or lack thereof) it’s tricky to strongly associate a pipeline with an agent without it being more or less speculative. We’re hoping that by introducing a better-structured solution we can give better visibility around this! Stay tuned
Which Agents are paused deliberately
Generally, issues helped by using the “stop” button wouldn’t be helped by the agent simply pausing - it’s generally that it’s started misbehaving or failing builds. An agent waiting for work would use the same resources as a “paused” agent so there’s not much of a case for the distinction.
Which agents are offline but previously eligible for jobs.
This is one I’ve personally wanted for a bit - we definitely still have the agent information (if you re-load an agent page for one which was previously connected, the information is still present) but haven’t had a good way to show off. I hope we do someday!
