What's New: AL-Go for GitHub on Delivery and Deployment (2025 release wave 1)
AL-Go for GitHub delivery and deployment changes in 2025 release wave 1: a dependency install mode setting, deployment of test apps to sandboxes, and deployment of pull request artifacts to an online environment. Covers the settings, the limits (manual trigger, one-day artifact expiry) and demos of each.
- Dependency Install Mode Feature
- Dependency Install Mode Demo and Configuration
- Test Apps Deployment Feature
- Test Apps Deployment Demo
- Pull Request Artifact Deployment
- Pull Request Deployment Demo and Artifact Expiration
Overview
The video walks through three changes to delivery and deployment in AL-Go for GitHub. The first is a dependency install mode setting that controls how dependencies are handled at deploy time, including installing or upgrading dependencies from AppSource when they are not part of the app being deployed. The second is deployment of test apps to sandbox environments, with the option to exclude apps by ID.
The third is deploying artifacts from a pull request directly to an online environment for quick testing before merging. It is currently started manually through a workflow with a pull request ID. The video demos each feature, including how artifacts behave with incremental builds and when they expire.
Key points
- Dependency install mode is a setting that decides how dependencies are handled at deploy time; set to upgrade, apps already installed in the environment are upgraded.
- It can install or upgrade dependencies from AppSource when they are not included in the app being deployed.
- Test apps are deployed only to sandbox environments, and specific apps can be excluded by ID.
- Test apps that depend on test libraries not available as AppSource apps, such as performance test apps, are excluded automatically.
- Pull request artifacts can be deployed to an online environment for testing before merge. For now this is a manual run of the publish to environment workflow with a pull request ID.
- Pull request artifacts expire after one day by default, and the presenter encourages keeping that setting.
- With incremental builds, only apps built in that pull request are published as artifacts; the remaining apps come from the last known good build.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Dependency Install Mode | 0:25 |
| Test Apps Deployment | 2:35 |
| Pull Request Artifact Deployment | 5:05 |
| Incremental Builds with PR Artifacts | 7:06 |
| Automatic Test App Exclusion by Dependencies | 4:45 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
Quotes
- 1:00 “if you were trying to deploy an app and the dependencies were not there”
- 1:43 “dependencies to upgrade the upgrade here comes from the dependency install mode set to upgrade meaning that if these apps are installed in a”
- 2:55 “for this presentation we have implemented the first version um and all you have to do is prepare your online environment which should be”
- 5:25 “we now have a new option for deploying pool request changes directly to an online environment this is useful for quick testing”
- 5:45 “for now this is a manual process where you will use the published to environment workflow give it a pool request ID instead of”
- 7:46 “artifacts will expire after one day using normal settings and we encourage you to keep settings this way”
Disclaimers in the video
- 5:45 coming-later: later on we want to investigate how we can do this automatically in such a way that every time you push a new change to a PR then those changes will automatically flow into your online environment
Presenters (as heard): Freddy Christensen, Sebastian.