A request from many partners have been to be able to automatically submit apps to AppSource Validation from their DevOps setup. The Ingestion API for Partner Center supports all offer types in AppSource and can be used to submit updates to Business Central apps to AppSource.Continue reading
Working with AL-Go for GitHub preview
If you want to have the latest updates of AL-Go for GitHub, you can update your repository and use https://github.com/microsoft/al-go-pte@preview or https://github.com/microsoft/al-go-appsource@preview as your template repository.
This means that you will get new updates before they are released. It also means that the actions you are using are instantly updated when we deploy a new version for preview and thus might be out of sync with your workflows.Continue reading
As mentioned in this blog post, the Invoke-ScriptInBcContainer has undergone some serious changes in BcContainerHelper 3.0.9, which just shipped.
This blog post will describe some details about how this function works.
The function takes a containerName, a scriptblock and an argument list as parameters and will execute this scriptblock inside the container.Continue reading
Major improvement when invoking scripts in Containers…
I recently learned that some partners have had had issues when running build pipelines on Azure DevOps with multiple DevOps agents on the same host using Containers with process isolation. 1-2 years ago, we did a number of fixes to support multiple agents on the same host, and I thought that had fixed things, but apparently this was not true.
Hopefully the fixes, which are going into BcContainerHelper today will fix this once and for good.Continue reading
Secrets in AL-Go for GitHub
This blog post will not reveal any secrets in AL-Go for GitHub:-)
Instead, it will explain ways for you to store secrets, which are used for AL-Go for GitHub. In almost every DevOps setup, you will have to store some keys, passwords, tokens or like. In GitHub, these are called secrets and AL-Go will look for a set of secrets by their name.
This blog post will also touch upon how you can use GitHub organizations and environments with your customer projects.Continue reading
Lately we have been seeing an increasing number of people having difficulties creating Docker containers on multiple host OS’. Since Thursday, I have been diving into error reports on GitHub, looking in Telemetry and had some partners helping out trying various tests to see what the result of various changes would be.Continue reading
Deployment strategies and AL-Go for GitHub
When you are done developing your app, it needs to be deployed to your customers if it is a PTE or to AppSource if it is an AppSource app.
Currently we don’t have any automated way of publishing your app to AppSource – that is something we are working on and some day in the future, when it becomes possible, you will get a workflow in AL-Go for GitHub which handles this automatically.
This blog post will talk about PTEs, and what features are available in AL-Go for GitHub to assist you deploying your PTEs to customers.Continue reading
Branching strategies for your AL-Go for GitHub repo
If you teach yourself to follow a fairly simple set of rules, you will see that the health of your project will increase dramatically, and you will be in a better place with your project development.
So, I will at the ripe age of 56 bestow upon you these 5 rules, which can be applied to any project, using any DevOps setup. In the following I will explain how to implement these rules using AL-Go for GitHub:
- Use Pull Requests
- Use Code Reviews
- Use automated testing
- Use Feature branches
- Use Releases and release branches
Preview of future AL-Go for GitHub functionality
Like everything else these days, AL-Go for GitHub now also is available in a preview version, which you can install/apply and remove as you like. This allows you to get advantage of a bugfix or new functionality faster.
NOTE that when using the AL-Go preview version, you will have to update the AL-Go system files when you are told to, changes to the AL-Go actions might cause your version of the workflows to fail if not updated.Continue reading
On May 1st, 2002, I walked through the doors of Navision in the Offices in Vedbæk for the first time. A few days earlier rumors had started that Microsoft was going to acquire Navision, but things weren’t settled yet.
The Acquisition was formally announced on May 7th and was finalized on July 11, 2002, so my 20-year anniversary as a Microsoft employee is on July 11th, but for me, May 1st will always be the date where I started working with ERP software.
I have worked with a lot of amazing people on a ton of amazing stuff, and I am still as passionate about what I do as I have ever been.
Steve Jobs once said that we’re here to put a dent in the universe. Well, I might not have put a dent in the universe, but I definitely put a dent in the way Business Central developers are working on a daily basis.
While the Microsoft mission is to empower every person and every organization on the planet to achieve more, I can safely say that I have and am empowering developers and partners on the planet to achieve more, trying to do my part…
There are a lot of memorable moments during the last 20 years, but the one that stands out is from Convergence in Munich 2006, where Bill Gates talked about Business Solutions and had a demo of a Shop Floor control performed on stage by our GM Darren Laybourn. After the keynote, the leader of Business Solutions, Satya Nadella, called Bill over to meet and greet. Humbled to have been in the company of these great people who both then and now has really transformed how people work and how people use IT.
Nobody knows what the future brings, but I will do my utmost to make the most out of it…
Thanks for all the fish