Operations, Deployment, Release
Table of contents
- How Does Mendix Support Staging & Deployment?
- How Do I Deploy My Apps as Part of the Release Process?
- How Can I Trace Released Changes Back to Requirements?
- How Many Environments Can I Provision for My Apps?
- What Controls Are Available to Secure the Production Environments of My Apps?
- How Does Mendix Support Staging & Deployment to Other Platforms?
How Does Mendix Support Staging & Deployment?
Staging and deployment is an essential part of the DevOps process, and having proper governance and control in place allows developers to release new versions of their code rapidly. Building this process can often be complicated, as it requires many moving parts. The Mendix Platform provides integrated tooling to support the staging and deployment of applications, both into the Mendix Cloud but also into other PaaS providers such as SAP Cloud Platform, AWS, Azure, and IBM Cloud.
How Do I Deploy My Apps as Part of the Release Process?
Before deploying an application, a deployment package is required. Using the Mendix Build Server, applications are automatically built and packaged in the cloud. The Build Server generates a Mendix Deployment Archive (MDA), which contains all the relevant assets to deploy your application.
Once a revision of the application is created in the Deployment Package Repository, it can be staged into one of the available environments. The Mendix Developer Portal allows you to do this with just a few clicks.
All deployment activities on the Mendix Platform are logged and visible in the Developer Portal. You can review the Activity log for each environment to identify the user who executed the operations on your app’s environments.
How Can I Trace Released Changes Back to Requirements?
When you commit the changes you have made to your app model in Mendix Studio Pro to the Team Server, you can mark the relevant user story from your active Sprint. This cross-referencing metadata is stored in the Mendix Team Server, so you can trace the changes back to the requirements later in the development process. For more details, see Version Control.
How Many Environments Can I Provision for My Apps?
In the Mendix Cloud, environments are provisioned to allow for staged deployment. Most application nodes come with either two environments (acceptance and production) or three environments (test, acceptance, and production). The Mendix Platform supports adding further environments to fit with your DevOps process.
Staging and deployment to each of these environments can be automated with the Deploy API so that development teams can set up fully automated CI/CD pipelines for their Mendix apps.
What Controls Are Available to Secure the Production Environments of My Apps?
In the Mendix Cloud, access controls are in place to only allow certain users access in order to view, deploy, and manage different environments. This enables the segregation of responsibilities when deploying to different staged environments.
To deploy an application into a production environment, users must authenticate using two-factor authentication, either by Google Authenticator or SMS. The token changes every 30 seconds. Once authenticated, you will be able to perform operations in production for up to 8 hours, after which you will be required to authenticate again.
How Does Mendix Support Staging & Deployment to Other Platforms?
Besides the Mendix Cloud, Mendix supports deployments on many different platforms, such as SAP Cloud Platform, IBM Cloud, Azure, AWS, VPC, and on-premises scenarios. For details on all the deployment capabilities of the Mendix Platform, see Multi-Cloud Overview.