English
Releases
What a release is
Settings are usually edited on a single stand: you open the stand, change a service version or a parameter value and apply it. But when the same change has to reach the whole platform at once — the default values and every working environment — editing stand by stand turns into slow manual work in which something is easily missed.
That is what a release is for in PDM: one agreed configuration change that is prepared as a whole and then rolled out to every stand at once. You pick the services and the new values, decide what to do with the stands that carry values of their own, and start the rollout with a single button.
| Stand settings | Release | |
|---|---|---|
| What it affects | one stand | the default values and every stand |
| Default values | unchanged | updated |
| Rollout | applied to that stand | mass-apply to production stands |
| Trace in history | progress is visible in workspaces | a record of the release and its contents is kept |
For more on base values and overrides, see Stand configuration.
When to use a release
- A service version has to go up across the whole platform, not on a single stand.
- A configuration parameter has changed and the new value should become the common one.
- Stands where someone previously set their own value have to return to the common one.
If the task is to check a build or experiment on one environment, you do not need a release: change the settings of that particular stand.
A release reaches production stands
Starting a release writes the changes to the shared config and runs a mass-apply across production stands. The operation cannot be undone from the interface. Make sure the change is agreed before you press Start release.
The “Release history” page
The Releases section keeps past platform releases and their results. The New release button is only visible if you have permission to create releases.
A release has no name — it is identified by its number, author and date. The Components column shows how many configuration fields the release changed; the Stands column is not populated yet.
Reading the statuses
| Status | What it means |
|---|---|
| Pending | The release has been created, the rollout has not started yet |
| Running | The rollout is in progress right now |
| Completed | Every step succeeded, the changes have been written and applied |
| Failed | One of the steps failed and the rollout stopped |
| Cancelled | Execution was interrupted |
The status comes from the rollout process attached to the release. One important detail: the release record is created before the work starts, so a failed attempt also stays in the history — with the status Failed. A row in the list does not mean the change reached the stands.
The list does not refresh itself
Unlike the process page, the release history is loaded once when you open it. To see the current status of a release you have just started, open its process or reload the page.
What is inside a row
The Component changes block is the contents of the release: for every changed field it shows the parameter, the service and the “before → after” transition.
If the release has a process attached, the same place shows an Open the processing pipeline → link to the page where you can see which steps the rollout consisted of and how each of them ended.
What's next
- Creating a release — a step-by-step walkthrough of the form.
- Rollout and outcome — what happens after the start and how to check it.
- Stand configuration — editing the settings of a single stand.