![[Jenkins]](https://ci.hibernate.org/static/41c7dad2/images/svgs/logo.svg){kind=logo}
Nodes
| S | Name | Architecture | Response Time | Clock Difference | |
|---|---|---|---|---|---|
[online] | Built-In Node | Linux (amd64) | 0ms | In sync | |
[offline] | TiDB | N/A | N/A | ||
[online] | cockroach-01 | Linux (amd64) | 2ms | In sync | |
[online] | s390x | Linux (s390x) | 27ms | In sync | |
| Data obtained | 20 min | 20 min | 20 min |
Status
- The agent is online and will accept tasks for execution when it has free executors.
- The agent has been put offline due to the configured retention strategy. It will be brought back online when needed (e.g. a new task requests it).
- The agent has been explicitly set to temporarily offline by a user. If the agent is still connected any running tasks will finish. No new tasks will start until the agent is put online again by a user.
- The agent is not accepting tasks for execution. This usually means that the agents availability settings prevent task execution, e.g. when using
Bring this agent online according to a scheduleand being outside the time window. The agent might still execute tasks that have started while it was accepting tasks. Cloud agents that are intended to run only a single task might also use this.
Agents will be shown assuspendedin theBuild Executor Statuswidgets. - None of the above conditions applies. The agent is not connected or it is still connected but a node monitor decided that the agent is not in a healthy state. An agent in this state should be investigated.