Structuring your AL-Go for GitHub repositories

When developing apps for Business Central, you very frequently will have more than one app. You might split one customer specific app into multiple smaller apps or you might have a common app, which contains common functionality for all your customer specific or AppSource apps.

This blog post describes the thinking behind AL-Go for GitHub and how we recommend you setup your GitHub repository structure and why…

Continue reading

Migrating to AL-Go for GitHub

As explained in the first blog post about AL-Go for GitHub the next post would be all about how to migrate your repository to AL-Go for GitHub.

Whether you have a setup based on the first CI/CD Hands-On-Lab or you have the latest generation, it should be fairly easy to migrate to AL-Go and get all the benefits with that, but it is a manual process.

The following scenarios are described in this post:

  1. From a CI/CD HOL based repo on GitHub
  2. From a CI/CD HOL based repo on Azure DevOps
  3. From GitHub (if you are “just” using it as a source code repository)
  4. From Azure DevOps (if you are “just” using it as a source code repository)
  5. From nothing (if you just have the source code on your laptop)
  6. From nothing (if you just have some .app files, but not the source code)

Last, but not least there are some common questions you need to consider when using any DevOps setup really.

Continue reading

AL-Go for GitHub

It has been a while since my last blog post and the reason behind this is quite simple: I have been busy. Busy creating AL-Go for GitHub.

AL-Go for GitHub is plug-and-play DevOps for Business Central PTEs or AppSource apps on GitHub. A tool, which does NOT require you to modify PowerShell scripts, change .yaml workflows or pipelines, but still allows you to setup and maintain full DevOps for your Business Central projects with a click of a button.

Continue reading