diff --git a/content/en/docs/private-platform/_index.md b/content/en/docs/private-platform/_index.md index 846b7223b71..09941515608 100644 --- a/content/en/docs/private-platform/_index.md +++ b/content/en/docs/private-platform/_index.md @@ -35,7 +35,7 @@ The integration with Studio Pro does not currently support using the [Integratio * Mendix developer experience hosted entirely within any virtual private cloud * Support for SSO authentication for Private Mendix Platform and Studio Pro through your own identity provider (IdP) * A private version of the Mendix Marketplace, with all contents hosted entirely within your Private Mendix Platform, accessible in-browser and directly from Studio Pro -* SCM repository support for GitLab, GitHub, Bitbucket and Azure DevOps Services, to be used as source code repository for your projects +* SCM repository support for GitLab, GitHub, Bitbucket, Azure DevOps Services and Azure DevOps Server, to be used as source code repository for your projects * CI/CD capabilities out-of-the-box, with additional support for integrations with Jenkins, Kubernetes, and Azure DevOps; leverage our predefined templates or implement your own custom templates * Operational capabilities such as basic log browsing and metrics through integrations with Loki and Grafana * Governance features like application landscape management, marketplace administration, user group management, as well as various developer platform feature settings and action logs diff --git a/content/en/docs/private-platform/configuration/pmp-configure-azure.md b/content/en/docs/private-platform/configuration/pmp-configure-azure.md index ca100116bf9..79531c61510 100644 --- a/content/en/docs/private-platform/configuration/pmp-configure-azure.md +++ b/content/en/docs/private-platform/configuration/pmp-configure-azure.md @@ -15,7 +15,7 @@ This document explains the configuration options available when configuring a Co To configure the CI/CD pipeline, prepare the following: -* An Azure organization where you want to build your Mendix app. +* An Azure DevOps Services organization where you want to build your Mendix app. The Azure DevOps CI build utility runs on Microsoft-hosted agents and works with Azure DevOps Services only; with Azure DevOps Server (on-premises), use the Kubernetes build method, see [Azure DevOps Server Builds](/private-mendix-platform/configure-k8s/#azure-devops-server). * An Azure blob or an AWS S3 endpoint where you can store the built MDA files. ## Configuring the CI/CD Pipeline diff --git a/content/en/docs/private-platform/configuration/pmp-configure-k8s.md b/content/en/docs/private-platform/configuration/pmp-configure-k8s.md index 1c9f61c9b65..fd4caf6ff86 100644 --- a/content/en/docs/private-platform/configuration/pmp-configure-k8s.md +++ b/content/en/docs/private-platform/configuration/pmp-configure-k8s.md @@ -441,6 +441,52 @@ Before creating any environments, you must register your Kubernetes clusters by 6. After the cluster is registered, create environments with the cluster, namespace and plans. +### Azure DevOps Server Builds {#azure-devops-server} + +When the version control system is Azure DevOps Server (on-premises), the build pods clone the app from your server with the PAT of the user who starts the build. They need the following: + +1. **DNS** - The build cluster resolves the server host name. A hosts entry on a single machine is not visible to the cluster. +2. **Network** - TCP 443 (or the server port) is open from the cluster's outbound addresses to the server. +3. **Build image** - pmp-pipeline-tools 0.11.1 or above. Earlier images fail with *Authentication failed* when the server offers Windows authentication (NTLM), which is the default for Azure DevOps Server. +4. **Certificate trust** - If the server certificate is not issued by a public CA, use a build image that trusts your CA (see below). Do not use **Skip SSL Verification** in production: it also switches off the certificate checks for the storage and registry calls. +5. **Secrets** - The build pod receives the user's Git token. Restrict read access to the build namespace. + +#### Building an Image That Trusts Your CA + +The build image trusts public CAs only and ignores `CACertificates` and the Operator custom CA secret. Build a derived image that adds your CA to its system trust store. You need one image per CA, and you rebuild it for every pmp-pipeline-tools release and every CA change. To build the image, follow these steps: + +1. Find the image in **Admin Mode** > **Settings** > **Build** > **Build Utility** > **Build Pipeline Image** and pin a version tag. +2. Create a Dockerfile next to `customer-ca.crt`: + + ```text + ARG BASE=private-cloud.registry.mendix.com/privateplatform/pmp-pipeline-tools: + FROM ${BASE} + USER root + COPY customer-ca.crt /etc/pki/ca-trust/source/anchors/customer-ca.crt + RUN update-ca-trust extract + USER mendix + ``` + +3. Build and test it: + + ```text + docker build -t /pmp-pipeline-tools-ca: . + docker run --rm --entrypoint sh /pmp-pipeline-tools-ca: -c 'git ls-remote https://///_git/ 2>&1 | head -3' + ``` + + The output must not contain *unable to get local issuer certificate*; an authentication message is fine here. + +4. Push the image. If the registry needs credentials, create an image pull secret in the build namespace and enter it as **Pull Secret**. +5. In **Build Utility**, set **Build Pipeline Image** to the new image and **Skip SSL Verification** to off. +6. Run a build. The Git step must clone without a certificate error. + +| Build Log | Cause | +| --- | --- | +| *Could not resolve host* | DNS | +| *unable to get local issuer certificate* | The image does not trust the CA, or the old image is still selected | +| *certificate is valid for ..., not ...* | The server certificate has no SAN for the host name | +| *Authentication failed* | Build image older than 0.11.1, or an invalid PAT | + ## Architecture of the CI/CD Pipeline The diagram in this section presents the architecture and components of the pipeline. For more information, see [Build Images Setting](#build-images) above. diff --git a/content/en/docs/private-platform/configuration/pmp-version-control.md b/content/en/docs/private-platform/configuration/pmp-version-control.md index 1d5596438d1..3b55f56f24a 100644 --- a/content/en/docs/private-platform/configuration/pmp-version-control.md +++ b/content/en/docs/private-platform/configuration/pmp-version-control.md @@ -15,7 +15,8 @@ Private Mendix Platform supports the following types of Git repositories as the * GitHub Enterprise Server * GitHub Enterprise Cloud * Bitbucket -* Azure DevOps Services (cloud, `dev.azure.com`). Azure DevOps Server (on-premises) is not supported. +* Azure DevOps Services (cloud, `dev.azure.com`) +* Azure DevOps Server (on-premises), version 2022.1 or above To select the repository type, perform the following steps: @@ -161,24 +162,32 @@ This user needs to be invited into the project with the **Create repository** pe {{< figure src="/attachments/private-platform/pmp-vc4.png" alt="Version Control Settings for Bitbucket" class="no-border" >}} -## AzureDevOps +## Azure DevOps -This section describes the configuration of an Azure DevOps repository for use with the Private Mendix Platform. +This section describes the configuration of an Azure DevOps repository for use with the Private Mendix Platform. Private Mendix Platform supports two deployment types: -### Prerequisites +| Deployment Type | Use For | Authentication | +| --- | --- | --- | +| **Azure DevOps Services (cloud)** | `dev.azure.com` | Microsoft Entra ID OAuth, which creates the users' Personal Access Tokens (PATs), plus an organization admin PAT | +| **Azure DevOps Server (on-premises)** | Your own Azure DevOps Server, version 2022.1 or above | PATs only. Private Mendix Platform does not call Microsoft Entra ID or `dev.azure.com` | + +Select the type in **Settings** > **Version Control** > **Azure DevOps** > **Deployment Type**. Existing configurations and settings exports from earlier versions use **Azure DevOps Services (cloud)**. + +### Azure DevOps Services (Cloud) -Before configuring Azure DevOps for Private Mendix Platform, ensure that you fulfill the following prerequisites: +#### Prerequisites + +Before configuring Azure DevOps Services for Private Mendix Platform, ensure that you fulfill the following prerequisites: -* You use Azure DevOps Services (cloud). Azure DevOps Server (on-premises) is not supported, because Private Mendix Platform requires the Azure DevOps cloud PAT API to generate your Azure PAT. * You have access to an Azure DevOps organization. * An Azure DevOps project exists to host applications created by the Private Mendix Platform. * You can generate Personal Access Tokens (PATs) in Azure DevOps. * A Microsoft Entra ID (Azure AD) application can be registered. * Your Azure DevOps organization must be connected to the same Microsoft Entra ID tenant as the app registration used for Azure OAuth. -### Microsoft Entra ID Configuration +#### Microsoft Entra ID Configuration -To use AzureDevOps as the repository, you must first register an application in [Microsoft Entra ID](https://learn.microsoft.com/en-us/azure/healthcare-apis/register-application), and take note of the following information: +To use Azure DevOps Services as the repository, you must first register an application in [Microsoft Entra ID](https://learn.microsoft.com/en-us/azure/healthcare-apis/register-application), and take note of the following information: * Application ID (client ID) * Directory ID (tenant ID) @@ -188,7 +197,7 @@ For the API permissions, select **user_impersonation**. For the web callback URL, enter a URL in the following format: `YOUR_APP_ROOT/oauth-callback/`. -### Azure DevOps Configuration +#### Azure DevOps Configuration In Azure DevOps, perform the following tasks: @@ -197,13 +206,14 @@ In Azure DevOps, perform the following tasks: 3. Create users who will work with Private Mendix Platform. 4. Assign those users the Basic access level. -### Private Mendix Platform Configuration +#### Private Mendix Platform Configuration -* **Host URL** - The Azure DevOps Services URL, `https://dev.azure.com`. Azure DevOps Server (on-premises) is not supported. +* **Deployment Type** - Select **Azure DevOps Services (cloud)**. +* **Host URL** - The Azure DevOps Services URL, `https://dev.azure.com`. * **Organization** – Enter the name of the Azure DevOps organization that you created. * **Organization Admin PAT** – Enter the Personal Access Token of the Azure DevOps organization admin user. -#### Azure OAuth Config +##### Azure OAuth Config 1. Click **New**. 2. Fill out the following information: @@ -217,7 +227,7 @@ In Azure DevOps, perform the following tasks: * **Default config** - Set to **Yes**. * **Active** - Set to **Yes**. -#### Normal User Credentials +##### Normal User Credentials Users must generate their own PAT to work with Azure DevOps by doing the following steps: @@ -227,4 +237,189 @@ Users must generate their own PAT to work with Azure DevOps by doing the followi 4. On the Microsoft login screen, input you Azure user credentials to verify and authorize the app. 5. Wait for the PAT and Azure user email to be displayed on the **Service Credentials** page in Private Mendix Platform. -{{< figure src="/attachments/private-platform/pmp-vc5.png" alt="Version Control Settings for Azure DevOps" class="no-border" >}} +{{< figure src="/attachments/private-platform/pmp-vc5.png" alt="Version Control Settings for Azure DevOps Services" class="no-border" >}} + +### Azure DevOps Server (On-Premises) {#azure-devops-server} + +With Azure DevOps Server, Private Mendix Platform creates one project with one Git repository for every app in a project collection of your server, manages the members of that project, shows branches and commits, and builds apps with the Kubernetes build method. All calls use PATs over HTTPS and go to your server only. + +#### Prerequisites + +Before configuring Azure DevOps Server for Private Mendix Platform, ensure that you fulfill the following prerequisites: + +* Azure DevOps Server 2022.1 or above (REST API 7.1). Versions 2022.1 and 2022.2 are tested. Earlier versions are not supported. +* A project collection that hosts the apps created by Private Mendix Platform. Each app gets its own project. +* A dedicated service account (not a personal account) that is a member of **Project Collection Administrators** of that collection, with a PAT (see [Personal Access Tokens](#ado-server-pats)). +* Private Mendix Platform can reach the server over HTTPS. The server certificate contains the host name of the Host URL in its Subject Alternative Name (SAN). +* If the server certificate is not issued by a public certificate authority (CA): the issuing CA certificate in PEM format (see [Certificates](#ado-server-certificates)). +* For Kubernetes builds: the requirements in [Azure DevOps Server Builds](/private-mendix-platform/configure-k8s/#azure-devops-server). + +#### Private Mendix Platform Configuration + +* **Deployment Type** - Select **Azure DevOps Server (on-premises)**. +* **Host URL** - The server URL without the collection, in the format `https://`, optionally with a port and a virtual directory, for example `https://ado.example.com` or `https://ado.example.com/tfs`. There is no slash at the end. +* **Collection** - The name of the project collection, for example `DefaultCollection`. +* **Organization Admin PAT** - The PAT of the service account. You can also store it in an external secret store (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault). + +When you save, Private Mendix Platform checks the connection, the server type and the PAT, and shows an error code if the check fails (see [Troubleshooting](#ado-server-troubleshooting)). The **Azure OAuth Config** section is not used for Azure DevOps Server and is hidden. + +{{% alert color="warning" %}} +Use HTTPS. An `http://` Host URL is accepted, but the PATs are then sent unencrypted; Private Mendix Platform logs a warning. +{{% /alert %}} + +{{< figure src="/attachments/private-platform/pmp-vc6.png" alt="Version Control Settings for Azure DevOps Server" class="no-border" >}} + +#### Personal Access Tokens {#ado-server-pats} + +| PAT | Owner | Scopes | +| --- | --- | --- | +| Organization Admin PAT | The service account | Project and Team (Read, write & manage); Code (Read, write & manage); Identity (Read & manage) | +| Users' PAT | Each user, their own account | Code (Read & write); Project and Team (Read) | + +A PAT works only in the collection where it was created. A PAT is checked when it is saved; if it expires or is revoked later, Git actions and builds fail with an authentication error (AZ003) until a new PAT is entered. + +Recommended PAT policy: + +* Create the Organization Admin PAT for a dedicated service account that is a member of **Project Collection Administrators** only. Grant exactly the scopes in the table, never full access. Choose the longest lifetime your policy allows, at most one year, and replace the PAT in Private Mendix Platform before it expires. Azure DevOps adds the account that creates a project to that project's default team, so this account appears as a member of every app project that Private Mendix Platform creates; with a personal account, that person appears in every project and the PAT stops working when they leave. +* Users' PATs need the scopes Code (Read & write) and Project and Team (Read) only. When a user's PAT expires, Git actions and builds of that user fail with AZ003 until the user enters a new PAT. +* Private Mendix Platform never exports PATs and never writes them to logs. + +#### Normal User Credentials + +Each user creates a PAT of their own account in Azure DevOps Server (**User settings** > **Personal access tokens**, on the collection used by Private Mendix Platform) and enters it in Private Mendix Platform: + +1. Log in to Private Mendix Platform. On the first login, enter the PAT on the welcome page; later, click **Manage My Account** > **Service Credentials** > **Register New Credentials** > **Azure DevOps**. +2. Enter the **Personal Access Token** and save. + +Private Mendix Platform validates the PAT and stores the account name that the server reports for it. This account name is what Private Mendix Platform adds to the project groups when the user gets a role on an app. The **Get My Azure PAT** button is not available for Azure DevOps Server. + +#### Certificates {#ado-server-certificates} + +If the server certificate is issued by a private or internal CA, add the CA certificate to the trust of Private Mendix Platform, using the Mendix runtime setting `CACertificates` or the Mendix Operator custom CA secret. The certificate must contain the host name of the Host URL in its SAN. Without trust, saving fails with AZ005. + +On Kubernetes with the Mendix Operator, follow these steps: + +1. Save the CA certificate (PEM) of the Azure DevOps Server as `ado-ca.crt`. +2. If a custom CA secret is already configured (`spec.trust.customCASecretName` in the Operator configuration), append the new certificate to the existing bundle, so that the CAs already in it stay trusted. Replace `NAMESPACE` with the namespace of Private Mendix Platform, and the secret name if yours differs: + + ```text + kubectl -n NAMESPACE get secret mendix-custom-ca -o jsonpath='{.data.custom\.crt}' | base64 -d > bundle.crt + printf '\n' >> bundle.crt + cat ado-ca.crt >> bundle.crt + kubectl -n NAMESPACE create secret generic mendix-custom-ca --from-file=custom.crt=bundle.crt --dry-run=client -o yaml | kubectl -n NAMESPACE apply -f - + ``` + +3. If no custom CA is configured yet, create the secret and set `spec.trust.customCASecretName` as described in [Obtaining and Configuring the CA Certificate](/private-mendix-platform/configure-k8s/#ca-certificate). +4. Restart Private Mendix Platform (`kubectl -n NAMESPACE rollout restart deployment/mxplatform-master`) and save the Version Control settings again. + +The build pods do not read this secret; see [Azure DevOps Server Builds](/private-mendix-platform/configure-k8s/#azure-devops-server). + +#### Studio Pro and Windows Authentication {#ado-server-studio-pro} + +Developers open an app with **Edit in Studio Pro**. Private Mendix Platform gives Studio Pro the repository URL and the user's PAT; Studio Pro then does all Git work itself, directly against Azure DevOps Server. Studio Pro uses two Git clients, LibGit2Sharp (inside Studio Pro) and Git for Windows. Both must trust the server certificate, and both follow the setting **Edit** > **Preferences** > **Version control** > **Git** > **Enable Current Windows User Authentication for git**. The setting is off by default and must match what your server offers. + +To find out what your server offers, request the collection URL without credentials and read the `WWW-Authenticate` header: + +```text +curl.exe -k -sS -o NUL -D - https://YOUR-SERVER/YOUR-COLLECTION/_apis/projects | findstr /i www-authenticate +``` + +| The Server Offers | Enable Current Windows User Authentication for git | Git Setting on the Windows Machine | What Signs In to Git | +| --- | --- | --- | --- | +| Negotiate and NTLM (Windows authentication on, the default) | **On** | `git config --global http.emptyAuth true` | The signed-in Windows user. The machine must be joined to the domain, and the Windows account must be the account of the PAT saved in Private Mendix Platform. The PAT is not sent to the server. | +| Bearer and Basic only (Windows authentication off) | **Off** | None | The PAT from the user's Private Mendix Platform profile | + +{{< figure src="/attachments/private-platform/pmp-vc7.png" alt="Studio Pro preferences, Version control, Git" class="no-border" >}} + +To set up a Windows machine (once per Windows user, or by group policy), follow these steps: + +1. Trust the server certificate in Windows. Skip this step if the certificate is from a public CA or your company CA is distributed by group policy. Otherwise, import the CA certificate (or the self-signed server certificate) into **Trusted Root Certification Authorities** of the current user; no administrator rights are needed: + + ```text + Import-Certificate -FilePath .\ado-ca.cer -CertStoreLocation Cert:\CurrentUser\Root + ``` + +2. Let Git for Windows use the Windows certificate store. Git for Windows has its own CA list and rejects your CA even after step 1: + + ```text + git config --global http.sslBackend schannel + ``` + +3. For Windows authentication only: let Git use the signed-in Windows user, and select the **Enable Current Windows User Authentication for git** checkbox in Studio Pro. Studio Pro gives Git no credential in this mode; without this setting Git asks its credential helper, which cannot prompt inside Studio Pro, and fails with exit code 128: + + ```text + git config --global http.emptyAuth true + ``` + +4. For Basic only: leave the checkbox cleared and do not set `http.emptyAuth`. +5. Restart Studio Pro and open an app from the app list. + +{{< figure src="/attachments/private-platform/pmp-vc8.png" alt="Studio Pro setting per server type and the messages for mismatches" class="no-border" >}} + +If opening the app fails, check the following messages. The Git output of Studio Pro is in `%LOCALAPPDATA%\Mendix\log\\git\git.log.txt`. + +| Message | Cause | What to Do | +| --- | --- | --- | +| *user cancelled certificate check* | Windows does not trust the server certificate | Step 1 | +| *SSL certificate problem: self-signed certificate* (in the Git log) | Git for Windows uses its own CA list | Step 2 | +| *Git command line client has exited with code 128*, with *terminal prompts disabled* in the Git log | Git got a 401 and no credential | Windows authentication server: step 3. Basic-only server: clear the checkbox | +| *too many redirects or authentication replays* | The checkbox is cleared and the server offers NTLM, so the PAT was answered with NTLM | Select the checkbox and set `http.emptyAuth true` | +| *Git command line client has exited with code 128*, with *couldn't find remote ref refs/notes/mx_metadata* in the Git log | The repository was pushed with plain Git and has no Studio Pro notes yet; not an authentication error | Commit and push once from Studio Pro | +| 401 or 403 after a successful connection | The Windows account is not the account of the PAT saved in Private Mendix Platform, or the user has no role with Git access on the app | Save a PAT of the Windows account; check the app role | + +{{% alert color="info" %}} +A PAT cannot be used against a server that offers NTLM: Studio Pro's Git library answers NTLM and the PAT fails. Use Windows authentication in that case. Windows authentication uses Kerberos when the client can obtain a ticket and NTLM otherwise; the settings above are the same for both. Kerberos needs a service principal name (SPN) for the host name that users type, registered for the identity of the Azure DevOps application pool. +{{% /alert %}} + +For the Azure DevOps Server administrator: Windows authentication is a setting of the IIS site and, on servers with the `/tfs` virtual directory, also of that application; the application setting wins. If you change it, check both levels and confirm the result with the `curl` command above. Private Mendix Platform itself does not need Windows authentication; it signs in with PATs. + +#### Repository Membership + +Private Mendix Platform manages access to each app's project with the Organization Admin PAT: + +* Access follows the app roles in Private Mendix Platform. A user gets repository access through a role that includes Git access, either given directly on the app (creator, invite, ownership transfer) or inherited from the group that owns the app when that group has auto-invite enabled. Group changes are synchronized in the background. +* An app Owner or a company administrator becomes a member of **Project Administrators**; every other role with Git access becomes a member of **Contributors**. **Readers** is not used. Changing the role moves the user to the new group and removes the old one. +* Removing a member removes the user from these groups and from the project's default team. Access that the user gets through other groups you set up in Azure DevOps stays. +* To open and push in Studio Pro, a user needs Read and Contribute on the repository, which **Contributors** gives. No project or collection administrator role is needed. +* Only Mendix app projects are changed: projects that Private Mendix Platform created, and existing projects that hold exactly one repository with an `.mpr` file (apps added with Import Apps). Other projects are never changed. +* Azure DevOps Server can only find users it already knows, that is, users who signed in or used a PAT before, or who are members of a group in the collection (for example an Active Directory group). For other users, Private Mendix Platform logs a warning and changes nothing; a direct invite is cancelled. +* A user must have saved their own PAT in Private Mendix Platform before they can be added to a project, because the saved PAT provides the account name. The account forms `DOMAIN\user`, the plain account name and the email address are accepted; a name that matches more than one person is refused. + +To manage project access only in Azure DevOps, set the constant `AzureDevopsIntegration.ServerManageMembership` to `false`. Private Mendix Platform then changes no groups and logs each skipped change. + +#### Settings Export and Import + +The settings export contains the deployment type, the Host URL and the collection. PATs are never exported; enter them again after the import. + +#### Advanced Settings + +| Constant | Default | Use | +| --- | --- | --- | +| `AzureDevopsIntegration.HttpConnectTimeoutMs` | 10000 | Time to open a connection to the server, in milliseconds (at most 600000) | +| `AzureDevopsIntegration.HttpRequestTimeoutMs` | 30000 | Time to wait for an answer, in milliseconds (at most 600000) | +| `AzureDevopsIntegration.ServerManageMembership` | true | `false` = do not change project groups (see Repository Membership) | + +Outbound proxy: only the Java proxy properties (`https.proxyHost`, `https.proxyPort`, `http.nonProxyHosts`) are used; proxy authentication is not supported. Redirects are not followed; use the final URL as the Host URL. + +#### Troubleshooting {#ado-server-troubleshooting} + +| Code | Meaning | What to Do | +| --- | --- | --- | +| AZ003 | Authentication failed | Check that the PAT is valid, not expired, created on this collection, and has the required scopes | +| AZ004 | Server unreachable or no answer in time | Check the Host URL, port, firewall and proxy; raise the timeouts for a slow server. The first request after a server restart can be slow; retry once | +| AZ005 | Certificate not trusted | Add the issuing CA (see [Certificates](#ado-server-certificates)); check the SAN | +| AZ006 | The URL is Azure DevOps Services, but Azure DevOps Server is selected | Select the matching deployment type | +| AZ007 | The server answered with a redirect | Use the final URL (for example `https`) as the Host URL | +| AZ008 | Collection, project or repository not found | Check the Host URL and the collection | +| AZ009 | Request not supported | Use Azure DevOps Server 2022.1 or above | +| AZ010 | Server error, or the configuration could not be read | Check the server and the Private Mendix Platform log, then retry | +| AZ011 | Invalid value | Check the Host URL and the collection | + +#### Limitations + +* The **Azure DevOps** CI build utility is not supported with Azure DevOps Server; use the Kubernetes build method (see [Azure DevOps Server Builds](/private-mendix-platform/configure-k8s/#azure-devops-server)). +* An outbound proxy that requires authentication is not supported. +* Studio Pro cannot use a PAT against a server that offers NTLM; use Windows authentication. +* As with the other version control systems, repository access is not removed when a Private Mendix Platform user is deactivated, blocked or deleted, or when an identity provider group claim is removed. Remove the user from the app or group in Private Mendix Platform first, or remove the user from the Azure DevOps project by hand. +* Kubernetes builds clone the repository with the PAT of the user who starts the build (Basic authentication); that user needs read access to the repository. +* One Azure DevOps configuration per Private Mendix Platform instance: all apps of the instance use the same server and collection. diff --git a/content/en/docs/private-platform/pmp-prerequisites.md b/content/en/docs/private-platform/pmp-prerequisites.md index 1875123a39e..4c86862416a 100644 --- a/content/en/docs/private-platform/pmp-prerequisites.md +++ b/content/en/docs/private-platform/pmp-prerequisites.md @@ -396,6 +396,7 @@ Private Mendix Platform must connect to services within your premises. Mandatory | Version control | GitHub Enterprise Server | 3.6 or higher | Required for projects and collaboration | | Version control | Bitbucket | Latest | Required for projects and collaboration | | Version control | Azure DevOps Services | Cloud | Required for projects and collaboration | +| Version control | Azure DevOps Server (on-premises) | 2022.1 or higher | Required for projects and collaboration | | CI/CD | Kubernetes | See See [Supported Cluster Types](#supported-clusters) | Default for CI/CD | | CI/CD | Jenkins | 2.346.1 or newer, with support for the Docker agent | Required for CI/CD | | CI/CD | Azure DevOps | Latest | Required for CI/CD | diff --git a/content/en/docs/private-platform/pmp-user-guide.md b/content/en/docs/private-platform/pmp-user-guide.md index be3f300b636..25ae23c6271 100644 --- a/content/en/docs/private-platform/pmp-user-guide.md +++ b/content/en/docs/private-platform/pmp-user-guide.md @@ -48,7 +48,7 @@ For more information about Personal Access Tokens, as well as creating and using In the **Service Credentials** tab, you can view and manage the credentials for various external systems that Private Mendix Platform can connect with. These services include GitHub, GitLab, Bitbucket, and AzureDevOps, used for managing your app projects. -To create or work on app projects in Private Mendix Platform, you must create an access token in GitHub, GitLab, AzureDevOps, or Bitbucket, and then add it in the **Service Credentials** tab. The token must have read and write access to a repository where the app project is stored. +To create or work on app projects in Private Mendix Platform, you must create an access token in GitHub, GitLab, AzureDevOps, or Bitbucket, and then add it in the **Service Credentials** tab. The token must have read and write access to a repository where the app project is stored. For Azure DevOps Server, the token is a Personal Access Token of your own account with the scopes Code (Read & write) and Project and Team (Read); the **Get My Azure PAT** button is available for Azure DevOps Services only. ## Installing Mendix Studio Pro diff --git a/content/en/docs/private-platform/reference/admin/pmp-ref-admin-manage.md b/content/en/docs/private-platform/reference/admin/pmp-ref-admin-manage.md index 6dc06702274..4da089387b6 100644 --- a/content/en/docs/private-platform/reference/admin/pmp-ref-admin-manage.md +++ b/content/en/docs/private-platform/reference/admin/pmp-ref-admin-manage.md @@ -162,7 +162,8 @@ On the **Import Apps** page, administrators can import existing Mendix apps that * GitLab * GitHub * Bitbucket -* Azure DevOps Services (cloud, `dev.azure.com`). Azure DevOps Server (on-premises) is not supported. +* Azure DevOps Services (cloud, `dev.azure.com`) +* Azure DevOps Server (on-premises). A project is listed when it has exactly one repository (the default repository, named like the project) with an `.mpr` file in its root, that your Personal Access Token can read, and that is not yet linked to an app. After the import, the app behaves like an app created in Private Mendix Platform; deleting the app deletes the Azure DevOps project. {{< figure src="/attachments/private-platform/pmp-admin6.png" class="no-border" >}} diff --git a/content/en/docs/private-platform/reference/admin/pmp-ref-admin-system.md b/content/en/docs/private-platform/reference/admin/pmp-ref-admin-system.md index 165bda2d0d9..865afe65b96 100644 --- a/content/en/docs/private-platform/reference/admin/pmp-ref-admin-system.md +++ b/content/en/docs/private-platform/reference/admin/pmp-ref-admin-system.md @@ -180,7 +180,7 @@ To enable the connection, click **Connect Jira**, and then provide the following #### Version Control -To create applications and collaborate, configure the connection to your version control repository. GitHub, GitLab, Azure DevOps Services, and Bitbucket are supported as version control systems. For more information, see [Configuring the Version Control System for Private Mendix Platform](/private-mendix-platform-version-control/). +To create applications and collaborate, configure the connection to your version control repository. GitHub, GitLab, Azure DevOps Services, Azure DevOps Server, and Bitbucket are supported as version control systems. For more information, see [Configuring the Version Control System for Private Mendix Platform](/private-mendix-platform/version-control/). #### Build diff --git a/content/en/docs/releasenotes/private-platform/2/2.8.md b/content/en/docs/releasenotes/private-platform/2/2.8.md index dc9ab307365..7b514964e90 100644 --- a/content/en/docs/releasenotes/private-platform/2/2.8.md +++ b/content/en/docs/releasenotes/private-platform/2/2.8.md @@ -12,6 +12,16 @@ These release notes cover changes made to the [Private Mendix Platform](/private This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version release. Customers are encouraged to upgrade to this version. [Previous MTS versions](/releasenotes/private-platform/1-13/) of Private Mendix Platform are no longer supported. {{% /alert %}} +## 2.8.2 + +### Release date: To be announced + +#### New Features + +##### Azure DevOps Server (On-Premises) Support + +You can now use Azure DevOps Server 2022.1 or above as the version control system. Select **Azure DevOps Server (on-premises)** as the deployment type and enter the host URL, the collection and an admin Personal Access Token (PAT). Users enter their own PATs. Private Mendix Platform creates, renames and deletes app repositories, manages project membership, and builds apps with the Kubernetes build method. Azure DevOps Services (cloud) works as before, with one change: a failed project delete is now reported and the app is kept, as with GitHub and Bitbucket. For more information, see [Azure DevOps Server (On-Premises)](/private-mendix-platform/version-control/#azure-devops-server). + ## 2.8.1 ### Release date: September 25, 2026 diff --git a/static/attachments/private-platform/pmp-vc6.png b/static/attachments/private-platform/pmp-vc6.png new file mode 100644 index 00000000000..7745dbae4ad Binary files /dev/null and b/static/attachments/private-platform/pmp-vc6.png differ diff --git a/static/attachments/private-platform/pmp-vc7.png b/static/attachments/private-platform/pmp-vc7.png new file mode 100644 index 00000000000..1e6762b5902 Binary files /dev/null and b/static/attachments/private-platform/pmp-vc7.png differ diff --git a/static/attachments/private-platform/pmp-vc8.png b/static/attachments/private-platform/pmp-vc8.png new file mode 100644 index 00000000000..7224b91b7b7 Binary files /dev/null and b/static/attachments/private-platform/pmp-vc8.png differ