# Rolling deployments and rolling groups

Source: https://www.jawsdeploy.net/changelog/rolling-deployments

Take one machine out of service, finish with it, put it back, and only then move to the next.

## What's new

**Rolling deployments.** A step can now be rolled across the fleet in a deliberate order, and a **rolling group** rolls several consecutive steps across it: `web01` stops, deploys, starts and smoke-tests before `web02` begins any of them.

Groups and their settings are snapshotted into a release, so changing a group means creating a new release.

Over the REST API you can list, create, update and dissolve groups on `/api/project/rolling-group`, and move a step in or out with `PUT /api/project/step/rolling-group`. MCP adds `create_rolling_group`, `configure_rolling_group`, `delete_rolling_group` and `move_step_to_rolling_group`.

See the [Rolling Deployments feature page](https://www.jawsdeploy.net/features/rolling-deployments) and the [rolling deployments guide](https://www.jawsdeploy.net/guides/rolling-deployments).

## Also in this release

Environment colours, carried by environment and tag badges across the app, and fixes to project, lifecycle and lifecycle phase deletion.