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

One example of this is the preview, which was released yesterday (June 26th, 2022) to fix issue #168 will cause CI/CD workflows to stop publishing artifacts until you have run the Update AL-Go System Files.

Technically, the reason for this is that the RunPipeline action now published artifacts into a folder called .buildartifacts (instead of output) and the earlier CICD.yaml will look in the output folder:

After updating the AL-Go System Files, everything will work normally again.

Note that this problem will NOT occur for people using the released bits. They can safely update to the latest version after it is released, and they will get workflows and actions updated together.


Freddy Kristiansen
Technical Evangelist

4 thoughts on “Working with AL-Go for GitHub preview

  1. Hi Freddy. Could you please explain how work nextMajorSchedule, nextMinorSchedule, currentSchedule settings of the .github\AL-Go-Settings.json file? should I perform any additional actions to schedule Test Current/Test Next Minor/Test Next Major workflows?


    • AL-Go for GitHub does not run on Azure DevOps. In order to use AL-Go you will have to move your source to GitHub.
      Try it out and see if it is worth to move. You will save a lot of time, but the savings comes with some limitations in flexibility.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s