Users can select the versions of an application they would like to use in the deployment from the list of their applications they currently are hosting in Bluemix. This included those built with Cloud Foundry, IBM Containers, or IBM Virtual Machines. They can also set the amount of time that they would like to allow for the ramp, testing, and ramp down phases, as well as if they will be allowing the move between each of the phases to be automatic or manual.
After creating a deployment, users can always come back to check on it and see the current state. From the deployment details screen, they can pause the deployment, move it to the next phase, or roll it back. They have visual indicators of the progress through the phases, as well as how much traffic is routed to each version. They can also view the logs for each version side-by-side, allowing them to keep an eye out for any errors that may be occurring.
Active Deployments and Deployment History
Users can see all the deployments that they currently have, take action on them, and check their status from the service homepage. They can also see a history of the deployments that have been completed, rolled back, or failed.
IBM Active Deploy Service
Lead UX/Visual Designer
2 designers, 1 product manager, 3 developers
The IBM Active Deploy service was a devops service made for IBM Bluemix, used to perform red/black deployments of application versions: ramping up a new version of their application and ramping down the old to allow for a smooth transition and time to run tests on the 2 versions before committing to the newest one.
Our challenge was to create an experience that allowed users to create and run these deployments for any application on Bluemix, regardless of infrastructure type, with the option of using either a GUI or CLI.