syntaqxA deploy that changes the runner's image or its container settings rolls every idle sandbox over at once (--containers-rollout=immediate), where Cloudflare's default rollout went in steps over wall-clock time and, with deploys often half an hour apart, never reached every sandbox: jobs kept starting on old images and old machine sizes. A change to the container settings alone, such as the instance type, now rolls out too; before, an unchanged image meant --containers-rollout none and the new settings were never applied. Busy sandboxes still get rollout_active_grace_period to finish.e277e3fHistory
- ..
- backup-restore-drill.mjs
- backup-restore-drill.test.mjs
- fork-storage-test.mjs
- gitstore-namespaces.mjs
- gitstore-namespaces.test.mjs
- gitstore-usage.mjs
- platform-usage.mjs
- platform-usage.test.mjs
- restore-to-gitstore.mjs
- restore-to-gitstore.test.mjs
- runner-errors.mjs
- runner-errors.test.mjs
- smoke.mjs
- smoke.test.mjs
- sudo.mjs
- vapid-keys.mjs