Sync the self-hosting stack
This commit is contained in:
@@ -9,6 +9,21 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
|
||||
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
|
||||
cannot be published without its entry.
|
||||
|
||||
## 2026-10-26 — The agent can run the script library's jobs `agent 0.53.0`
|
||||
|
||||
**The agent learns to run the script library's jobs.** A job survives an agent restart or a lost
|
||||
connection, and its result is handed back when the machine is reachable again. Until the library
|
||||
ships, the server sends none. The agent keeps its jobs in `C:\ProgramData\Jarvis Agent\jobs` on
|
||||
Windows, `/var/lib/jarvis-agent/jobs` on Linux and `/var/db/jarvis-agent/jobs` on macOS, and runs
|
||||
them in `C:\ProgramData\JarvisJobs`, `/var/lib/jarvis-agent/work` or `/var/db/jarvis-agent/work`.
|
||||
Uninstalling the agent stops any job it is running.
|
||||
|
||||
**An agent update waits for a running job.** The update is applied once the job has ended, never in
|
||||
the middle of it.
|
||||
|
||||
Update the api and web images first (api 2.1.7, web 2.1.11), then the agent release image; enrolled
|
||||
machines take the new build under their update policy.
|
||||
|
||||
## 2026-10-26 — The script library, reviewed, still hidden `api 2.1.7` `web 2.1.11`
|
||||
|
||||
**Nothing changes on screen.** These builds correct what a review of the unfinished script library
|
||||
|
||||
Reference in New Issue
Block a user