To give the developers and testers additional faith that their proposed changes work successfully, it is advisable to build and test their code changes in the Pull Request before it is approved and merged into the Master branch.
If you use a GitHub Pages Site and want to run it locally for testing and development. You’ve come to the right place to learn how to get it up and running in a matter of minutes. Running Jekyll Locally on Windows
With the release of Octopus 3.5 you can now utilise Azure AD authentication. This document is an overview of how I have implemented this.
On a frequent basis I am being requested to recreate / move AX databases between environments.
DEV to UAT. PROD to UAT. GOLD to LOCAL. PROD to LOCAL etc.
This is not officially supported by MS, they recommended that the DB’s never move because there are so many references to settings on a per environment basis that you are likely to cause problems. Hence we never ever move a DB to PROD, we can move from and to any other platform for testing and development, but never to PROD. In most cases, this is not a problem but there are circumstances that need to be considered to get the restored database functioning.
To set up Release Management for AX 2012 I will be utilizing the Build and Release functions of Visual Studio Online. Below image is an overview of the process for releasing the code into our AX platform.
When I first started to implement AX 2012 R3, I had been told that I have to manage users inside AX as well as manage users within Active Directory. I was not happy about this, so found the following method to support an AD based AX authentication process. The basic process for doing so is to query all AX Security Roles and export to CSV. Create AD Groups reflecting the Roles. Create AX User Groups reflecting the AD Groups. Finally add into the AX User Groups the AD Groups which reflect the AX Security Roles. First I needed to query AX for all the built in Roles