Fixed Issues in Aras DevOps Release 1.11
Copy
| Issue # | |
|---|---|
| F-008406 | The Continuous Integration pipeline now contains warnings when customizations may be incompatible with Aras Innovator Containerized Deployment, helping to proactively identify and resolve issues related to differences between Local Development Environment and Standard Development Environment. |
| F-008717 | The AML import process in Continuous Integration and Deploy pipelines now collects and displays all encountered errors instead of stopping at the first one. This change provides a more comprehensive error overview and eliminates the need to rerun pipelines multiple times to uncover subsequent issues. |
| F-008982 | CI pipeline now supports custom Build Validation rules for custom branches, enabling more flexible validation workflows. |
| F-008997 | Previously, updating an existing Aras Innovator instance on Local Development Environment required a full redeployment from scratch, which was inefficient. With the new parameters, specific customization types can now be updated independently, significantly improving the speed and flexibility of the development workflow. |
| F-009006 | The Continuous Integration and Deploy pipelines have been improved by transitioning from sequential to batch mode AML import. This enhancement streamlines the process, reducing the apply AML stage duration and improves overall pipeline efficiency. |
| I-073920 | Aras.DevOps PowerShell cmdlets no longer install .NET Core 2 and 3 modules when Aras Innovator release 27 or higher is used, reducing legacy dependencies and aligning with current platform standards. |
| I-074187 | The Continuous Integration pipeline no longer fails when “AuthenticateWithPasswordHash” setting is set to “false” in the appsettings.json transformation of the Innovator Server. |
| I-074361 | The problem led to incomplete or missing backup artifacts, and a broken deployment state. |