Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Last few days I have been working on running automated builds for Business Central on our self-hosted server using Azure DevOps.
There are already few articles in the Internet where you can read about it. You can find the good series of posts on https://freddysblog.com/ or https://jpearson.blog/. Lately also DevOps for AL extension had been released. More information here: http://www.waldo.be/2019/06/18/devops-for-al-alops-is-alive/
Despite those blogs I decided to share all of my findings and scripts with you.
In the next few articles, starting from this one, you will be able to get more info about:
First of all, I should say that in all my examples, which I will present, I am using NAVContainerHelper. I really like them and fully support the idea. The library is easy to use and really useful. I know that there are some inconvenience using them, but I decided to base my workflow on using them anyway.
Second of all, to start you need to have few things ready:
In fact, after series of my articles you will have information how to build one of 4 options.
This is the simplest option. It will have below steps:
This is the extension to the previous workflow. After publishing the extension, next steps will be processed:
This is the more complex example. After following this path, you will be able to build your whole project if it contains more than one extension. It is quite common approach for products which have modules. The workflow for this example looks as follows:
After those steps there are few more which are going in the loop for each extension:
This is the extension to the previous workflow again. After publishing all required extensions, next steps will be done related to the test applications:
Hope you will enjoy the series on the blog.
Business Applications communities