Releases

When Releases are enabled for your organisation, Duku records each build as a release on the environment it was deployed to, and every exploration and test result is tied to the release it ran on. Contact Duku to enable Releases.

What changes in the app

The tabs become Overview, Issues, Releases, Exploration, Tests (Beta) and Schedules. Runs and the target menu are hidden. On the Exploration and Tests pages the run buttons carry an on {environment} picker, so you choose which environment a run goes to.

Record your first release

1

1. Set up your environments

An environment is a name and URL that your product is deployed to, such as production or staging. New products start with a production environment. An org admin opens Product settings (the cog next to the product menu) and scrolls to Environments

Each environment has Credentials, to choose the credential set runs on it log in with, and Set default, to make it the environment runs and schedules use when you don't pick one.

2

2. Add an environment

Select Add environment, enter a name and the URL it serves, and select Create.

3

3. Record a release

Select Record release on the Overview or Releases page. In Record a release, choose the environment, enter the version (for example 1.2.2), and select Record & explore. Duku records the release and starts exploring it. Recording the same release on the same environment twice records one release, and the exploration always runs against whatever that environment currently serves.

From CI, you don't need to record releases by hand. The environment action records one on every deploy - see Keeping Duku in step with your releases. From any other CI, see Record a release after each deploy.

The Releases page

Live now shows the release each environment is serving, with a shortcut to its tests. Release history lists every release By environment, with a Live marker on the one each environment serves now.

Switch to By lineage to group releases by the branch they were built from.

Release detail

Open a release to see the release it was built on, where it is live, and the pull request it was explored on.

Below that, Environments lists every environment the release was deployed to - Live where it is serving now, Redeployed when the same release was deployed there again, and Superseded where a newer release has replaced it - followed by its Test results and Exploration runs.

Rename a release

Org admins can select Rename release on the release detail page, edit the name in place and select Save. Only the name changes - the commit stays the same.

Run tests on an environment

On the Tests page, Run on {environment} replays your tests on the environment you pick. The Exploration page has the same picker for explorations.