Retry pipeline run in Mendix Pipelines
It would be useful to retry a pipeline run in Mendix without needing to commit a superficial change—such as moving an activity—just to trigger a build, deploy, and test of the latest app state. This would save time, avoids cluttering commit history, and improves workflow efficiency for developers.
When a step, e.g. publish step, fails outside of our control. We cannot retry the run to automatically run the unit tests and get the insights they give us.
To retry a failed run it would be ideal an option to rerun the failed pipeline run again. Or alternatively, the option to also have the option to manually trigger a pipeline (even though it is configured to trigger on a push).
You are right, it is essential to be able to run against the exact same snapshot! When you associate the branch and commit hash to each run you can ensure this and leverage this information in the git checkout command when you retry the run.
This is a very practical suggestion Arjen It would definitely streamline the CI CD process in Mendix Pipelines Allowing a retry without needing a new commit would reduce unnecessary version noise and save time especially in cases where failures are unrelated to the code itself like network or deployment issues
However one potential challenge could be ensuring that the pipeline always runs against the exact same snapshot of the app state Without a new commit it might be harder to guarantee consistency especially if other changes are happening in parallel in the repository Still with proper version locking or tagging this can be managed and the benefits would likely outweigh the risks
Hope the Mendix team considers this enhancement