Skip to main content

Notifications

Announcements

Community Forum Filters
News and Announcements icon
Dynamics 365 Community / Blogs / Insiders tips on development and customization ... / First Azure DevOps Task Rel...

First Azure DevOps Task Released!

Joris dG Profile Picture Joris dG 17,775

We are happy to announce our first release of an Azure DevOps task in the Visual Studio Marketplace to support Dynamics 365 for Finance and Operations ALM processes. We have more tasks and features planned, and we will continue to publish updates and features as well as new tasks as they become available.

This first release contains a single task that can be used in a Release pipeline to upload your software deployable package to a project's asset library in Dynamics Lifecycle Services (LCS). As this task is being released, the team is hard at work to create the next task which will allow customers and partners to deploy a specific asset from the asset library into their environment, which will complete a set of two tasks to allow continuous deployment for X++ developers!

We realize documentation is needed so we are also working on adding detailed documentation for these tasks on our docs website. For those who can't wait, the only detail that may not be intuitive and requires some specifics is the need for an application registration in Azure Active Directory for your Azure DevOps to connect to LCS. For the tenant used for the LCS project in question, you need to register a native application in Azure AD and give "Dynamics Lifecycle services" API permission as per this documentation (we recommend using the new preview app registration feature). Ensure the user you will use for the connection has access to the project, as well as granted consent for the application registration in Azure AD. Review the consent documentation to enable a specific user, or grant admin consent for the whole tenant.

Also note that the release task can execute on a hosted agent and doesn't require a build VM or otherwise private agent. When using hosted agents, make sure to use the latest host ("Host VS2017").

Comments

*This post is locked for comments

  • JustZM Profile Picture JustZM 948
    Posted at
    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
  • Martin Rasmussen Profile Picture Martin Rasmussen 15
    Posted at
    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.
  • Philippe REVEILLERE Profile Picture Philippe REVEILLERE
    Posted at
    @Fboller : Hi, I have the same issue as you had. Did you manage to find a solution ?
  • kgmadsen Profile Picture kgmadsen 30
    Posted at
    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
  • Anton Venter Profile Picture Anton Venter 5,058 Moderator
    Posted at
    Release pipeline link URL does not point a valid page anymore.
  • Martin Rasmussen Profile Picture Martin Rasmussen 15
    Posted at
    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
  • Fboller Profile Picture Fboller
    Posted at

    @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?

  • Rob Shore Profile Picture Rob Shore
    Posted at

    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!!!

  • Joris dG Profile Picture Joris dG 17,775
    Posted at

    @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 .

  • steen.rabol Profile Picture steen.rabol 95
    Posted at

    I'm facing the same issue as Dick Wenning, any suggestions ?