Eido Build updates itself when an admin tells it to. Nothing updates on its own.
See what is available#
Admin → Updates shows the version you are running and the release available to you, with the notes of every release in between.
Eido Build learns about new releases when it checks in, every four hours. Check for updates asks straight away.
Admins also see a notice at the foot of the sidebar when an update is available.
Install an update#
- Go to Admin → Updates and read the release notes.
- Choose install now, or pick a time when a restart will not disturb anybody.
- Confirm.
Eido Build then downloads the release, checks it against its published SHA-256 hash, deploys it over itself, and restarts. Any change to the database is applied as the new version starts.
Everybody who is signed in sees a notice at the foot of the sidebar when an update is coming and while it is running.
What an update interrupts#
While Eido Build restarts, nobody can use it. Choose a quiet time, particularly if agent stages are running.
After an update#
- The new version confirms that it started and can reach its database.
- If you use Foundry workbenches, press Deploy on each one in Admin → Workbenches to move it to the new version’s worker. See Workbenches.
Channels#
| Channel | What you get |
|---|---|
| GA | Releases that have proved themselves on the Preview channel. The default. |
| Preview | Releases earlier, before they are promoted to GA. |
Change channel on Admin → Updates. A release promoted from Preview to GA is the same build, not a rebuilt one.
If an update goes wrong#
If Eido Build does not come back after an update, or comes back with a problem, contact support with your install id and the version you were updating to. Do not restore the database yourself: every release is built so that the previous version still works against the updated database, which lets us put the previous version back.
Turning updates off#
If you need to stop Eido Build offering updates, for example during a change freeze, set Updates__Enabled to false in the App Service’s application settings.