English
Workspaces
Why this exists
Many actions in PDM do not happen instantly. Applying stand settings, building a service, rolling out a release, refreshing cluster data — each of these is a chain of several steps that runs for minutes, sometimes longer. While it runs, you want to know whether it made it to the end, which stage the system is at right now and, if something broke, exactly where.
That is what a workspace is for: a visual map of one long-running operation broken down into individual steps. Every step on the map is a node, and the arrows between nodes show what runs after what. Each node carries a state: waiting its turn, running right now, finished successfully or failed.
How to read it
A workspace is not a setting and not a request form — it is the execution history of one operation. You do not fill it in, you watch it.
Where workspaces come from
You cannot create a workspace by hand. The system assembles one for you the moment you start a long-running operation:
| What you did | What appears |
|---|---|
| Pressed Deploy changes on the stand's “Services” tab | A workspace for applying that stand's settings |
| Started a release on the last step of the wizard | A workspace for the release rollout |
| Started a service build on the “CI Builds” page | A build workspace |
| Refreshed the platform data with Refresh on the dashboard | A synchronisation workspace |
Names are generated by the system and usually make it clear what the operation relates to — for applying settings, for instance, the name contains the stand name.
The trigger button returns immediately: the operation itself goes off to run in the background and the interface hands control straight back to you. So “command accepted” does not mean “everything is done” — for the outcome you go to the workspace.
The workspace list
The Workspaces menu entry opens the “Workspaces” page, where operations are listed newest first. What is worth knowing about the columns:
| Column | What it shows |
|---|---|
| Stand | The stand the operation concerns; a dash means it is not tied to a stand |
| Changes | How many steps the operation has — this counts steps, not changed values |
| Status | The overall state: “Pending”, “Running”, “Completed”, “Failed”, “Cancelled” |
The list keeps itself up to date: status and progress change on screen without a page reload.
What the overall status means
The status of the whole workspace is derived from the states of its nodes: if at least one node failed, the whole operation counts as failed; if at least one is running, it is running; it only becomes completed once every node has been through.
What you see and what you do not
By default the list shows the operations you started yourself. The right to see other people's workspaces is granted separately by an administrator. So an empty list means “you have not started anything”, not “nothing is happening in the system”.
A shared link is a special case: a link a colleague sent you opens that one workspace even if your regular permissions would not show it. See Running and watching for details.
What's next
- Graph editor — what a node shows and where to find its data and logs.
- Running and watching — how to read node states, where to find errors and results.
- Stand configuration — the most common operation that produces a workspace.