You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/pipelines.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ Click **Copy ID** ({{% icon name="copy" %}}) on a pipeline design to copy the de
92
92
93
93
Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Edit** on a pipeline design to go to its **Details** page. From there, you can view and edit the pipeline details, as described in the [Editing a Pipeline](#edit-pipeline) section below.
94
94
95
-
Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Delete** to delete a pipeline design.
95
+
Click **More Options** ({{% icon name="three-dots-menu-horizontal-filled" %}}) > **Delete** to delete a pipeline design. You cannot delete a pipeline design if it is used in any currently running pipelines. Instead, you must wait for the run to finish before you delete the design.
96
96
97
97
{{% alert color="warning" %}}
98
98
If you delete a pipeline design in the **Designs** tab, any run history associated with that pipeline design is deleted from the **Runs** tab.
@@ -121,6 +121,8 @@ From your pipeline design's **Details** page, you can add, remove, and configure
For pipelines that are currently running, the page shows the current state of the steps (finished, running, or not started).
125
+
124
126
Active pipelines cannot be edited; if you want to edit an existing pipeline, make sure it is deactivated.
125
127
{{% /alert %}}
126
128
@@ -140,6 +142,8 @@ This is a mandatory step for each pipeline; you cannot delete this step. This st
140
142
141
143
{{% alert color="info" %}}
142
144
The Teamserver push (Git) command requires a Git repository. Customers using an SVN repository for their Mendix app cannot use this trigger.
145
+
146
+
Ensure that you only create one pipeline per app with the Teamserver push (Git) trigger and the same [branch expression](#branch-expression). If you create multiple pipelines with the Teamserver push (Git) trigger and the same expression, only the pipeline that you created first is executed.
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/deployment/mendix-cloud.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,15 @@ For information on the current status of deployment to Mendix Cloud and any plan
16
16
17
17
## 2025
18
18
19
+
### February 27, 2025
20
+
21
+
#### Improvements
22
+
23
+
* We have added a validation mechanism for pipeline designs, which prevents users from deleting a design if any pipelines using that design are currently running. For more information, see [Pipelines: Editing a Pipeline Design](/developerportal/deploy/pipelines/#edit-pipeline).
24
+
* You can now access the **Details** page of a pipeline at any point, also while the pipeline is running. For more information, see [Pipelines: Run Results](/developerportal/deploy/pipelines/#run-results).
25
+
26
+
## 2025
27
+
19
28
### February 20, 2025
20
29
21
30
#### Improvements
@@ -35,7 +44,7 @@ For information on the current status of deployment to Mendix Cloud and any plan
35
44
36
45
#### Improvements
37
46
38
-
*Also as part of the new UI we made improved the experience of using the **Environments Overview** page for paid apps – this is based on your feedback, thanks.
47
+
*Based on user feedback, the [new UI](/developerportal/deploy/environments-redesign/) now also contains UX improvements to the **Environments Overview** page for paid apps.
0 commit comments