Comments
-
Hi Joris dG Might I have steps for how to set details. So when I run build pipeline, the deploy package can be saved to LCS' Asset library. I do not why when I run build pipeline, the package deploy to the test environment immediately. Best Regards, JustZM
-
There is currently no solution to my problem. The challenge is that the hosted agents in DevOps has a hardcoded timeout on 60 minutes. However, you can configure your own agents and make it work again.
-
-
You can't make a 'Native application' when you create a new App Registration because the Azure Team has changed it. You must enable the 'Default Client Type' to Yes and use the "">login.microsoftonline.com/.../nativeclient" - Then it will work as before
-
-
Thanks for a nice tool, simplifying the release process to various environments. I have started to receive this error in some of the environments I deploy to: 2019-08-23T11:29:12.4224106Z Status: InProgress 2019-08-23T11:34:13.4501400Z Status: InProgress 2019-08-23T11:37:43.1466208Z ##[error]The operation was canceled. The deployment is running, the package is deployed and seems alright in LCS. But in DevOps, it end with an error. From what I have monitored, it seems like it's getting a wrong signal from LCS or translating the signal wrong, when the deployment is done in LCS. i.imgur.com/8TLT6vO.jpg
-
@The Deployer, i am getting the "Leaf path not found" error even when the release pipeline is configured with the following Dynamic path : $(System.DefaultWorkingDirectory)/_Build AWMS - Development/Packages/AXDeployableRuntime_7.0.5286.41360_$(Build.BuildNumber).zip. The root issue here is the Dynamics version so the release works until the environment its updated/upgraded. Is there a way that we can go around the Dynamics' version number in the package name (in my case: 7.0.5286.41360)? is there a token/wildcard that can be used to get the latest package generated?
-
It seems that over the weekend the Preview Mode became GA (I was in 'legacy' version fine last week).
You can however still access the old version within the App Registration screen - 'Still want to use App registrations (Legacy)? Go back and tell us why' just above the list of applications.
You have to do this as the app has to be a true legacy version Native app - the replacement, 'Public client Mobile & Desktop' is completely different, but is the only option other than Web in the new App Registration. Worked straight away when created this way for us having already done the other config as per the instructions.
Oh and this is AMAZING. Thankyou!!!
-
@Kasthu: Looks like you have an issue with the AAD setup. Make sure the client app ID is created as "native".
@steen.rabol/Dick Wenning: you should tie your release pipeline to your build. Picking up the package from a folder from a previously run build is not a good idea. See docs.microsoft.com/.../artifacts .
-
*This post is locked for comments