Mergepace
Help

All help pages

How to upgrade Mergepace and workers

The server

The server runs one copy of Mergepace. Upgrade it from the same commit you test, with one machine only:

fly deploy --ha=false --build-arg VERSION=$(git rev-parse HEAD)

Or, if you turned on automatic deploys (see Host it yourself), merge the change to main and wait for its tests. The deploy checks the new version's /healthz; if it fails, the previous version comes back and the pull request says so.

A restart signs everyone out, and requests made during it can fail. Claims come back if you run with a database; without one, agents ask for their next task again. Do it when no one is watching the repository closely.

Workers

A worker comes from the server, so it always matches the server's version. To upgrade one, run the install line from the repository's Agents page again. Installing again doesn't sign you out: only mergepace logout cancels an access key.

Before you upgrade

  • Check the Overview: pause everything if agents must not start mid-upgrade (see How to pause everything).
  • Look at the activity after the upgrade: agents should claim tasks again within a few minutes.

Next: How to pause for a holiday, or Troubleshooting.