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").
Yes ;) thank you Joris for making this happening! Great job!
Suggestion to add "wildcard" support for the file names, We append a version number to the package files, and a date to the backup files....
But also I got stuck with the following error:
2019-01-19T21:17:43.3579846Z Authenticating with AAD on login.microsoftonline.com/.../oauth2 for API lcsapi.lcs.dynamics.com
2019-01-19T21:17:44.7067434Z ##[error]AADSTS70002: The request body must contain the following parameter: 'client_secret or client_assertion'
Trace ID: 276e7dbc-8fda-4090-9ea1-7ff8594d4300
I had the same error. While using the preview feature to create a Registered App, I was unable to create a Native one. I tried all the options I had available, without any luck. However using the "old" / current Registered App feature inside the Azure Portal helped me create the Native App itself. Afterwards I was able to utilize the preview feature to configure the policies and consent.
Looks that is the trick, first creating a native via the old portal and than make it work...
Upload to LCS is now working
Thnx @Motz Jensen for the trick!