You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[releases/25.0@a4cd737] Update AL-Go System Files from microsoft/AL-Go-PTE@preview - a7e66c8 / Related to AB#539394 (#7379)
## preview
Note that when using the preview version of AL-Go for GitHub, we
recommend you Update your AL-Go system files, as soon as possible when
informed that an update is available.
### Added support for workspace compilation
With v28 of Business Central, the ALTool now also provides the ability
to compile workspaces of apps. This has the added advantage that the
ALTool can compute the dependency graph for the apps in the workspace
and compile apps in parallel (if possible). For AL-Go projects with
large amounts of apps that can save a lot of time. If you want to try
this out you can enable it via the following setting
```json
"workspaceCompilation": {
"enabled": true
}
```
By default apps are compiled sequentially but this can be changed via
the parallelism property. This allows you to configure the maximum
amount of parallel compilation processes. Set to 0 or -1 to use all
available processors.
```json
"workspaceCompilation": {
"enabled": true,
"parallelism": 4
}
```
### Test Projects — split builds and tests for faster feedback
AL-Go now supports **test projects**: a new project type that separates
test execution from compilation. A test project does not build any apps
itself — instead it depends on one or more regular projects, installs
the apps they produce, and runs tests against them.
This lets you re-run tests without waiting for a full recompilation, and
makes it easy to organize large repositories where builds and test
suites have different scopes or cadences.
**Getting started**
Add a `projectsToTest` setting to the project-level
`.AL-Go/settings.json` of an empty project (no `appFolders` or
`testFolders`):
```json
{
"projectsToTest": ["build/projects/MyProject"]
}
```
AL-Go will automatically:
- Resolve the dependency so the test project always builds after its
target project(s).
- Install the Test Runner, Test Framework, and Test Libraries into the
container.
- Run all tests from the installed test apps.
**Key rules**
- A test project must **not** contain buildable code (no `appFolders`,
`testFolders`, or `bcptTestFolders`). AL-Go will fail with a clear error
if it detects both `projectsToTest` and buildable folders.
- A test project cannot depend on another test project.
- You can target multiple projects: `"projectsToTest":
["build/projects/ProjectA", "build/projects/ProjectB"]`.
- Use full project paths as they appear in the repository.
### Improving error detection and build reliability when downloading
project dependencies
The `DownloadProjectDependencies` action now downloads app files from
URLs specified in the `installApps` and `installTestApps` settings
upfront, rather than validating URLs at build time. This change
provides:
- Earlier detection of inaccessible or misconfigured URLs
- Clearer error messages when secrets are missing or URLs are invalid
- Warnings for potential issues like duplicate filenames
### Improve overall performance by postponing projects with no
dependants
The time it takes to build projects can vary significantly depending on
factors such as whether you are using Linux or Windows, Containers or
CompilerFolders, and whether apps are being published or tests are being
run.
By default, projects are built according to their dependency order. As
soon as all dependencies for a project are satisfied, the project is
added to the next layer of jobs.
The new setting `postponeProjectInBuildOrder` allows you to delay long
running jobs (f.ex. test runs) with no dependants until the final layer
of the build order. This can improve overall build performance by
preventing subsequent layers from waiting on projects that take longer
to complete but are not required for further dependencies.
### Issues
- Attempt to start docker service in case it is not running
- NextMajor (v28) fails when downloading dependencies from NuGet-feed
- Issue 2084 Multiple artifacts failure if you re-run failed jobs after
flaky tests
- Issue 2085 Projects that doesn't contain both Apps and TestApps are
wrongly seen as not built.
- Issue 2086 Postpone jobs, which doesn't have any dependents to the end
of the build order.
- Rework input handling of workflow 'Update AL-Go System Files' for
trigger 'workflow_call'
### New Settings
- `postponeProjectInBuildOrder` is a new project setting, which will (if
set to true) cause the project to be postponed until the last build job
when possible. If set on test projects, then all tests can be deferred
until all builds have succeeded.
Related to
[AB#539394](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/539394)
Co-authored-by: business-central-bot <business-central-bot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: .github/RELEASENOTES.copy.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,25 @@
2
2
3
3
Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available.
4
4
5
+
### Added support for workspace compilation
6
+
7
+
With v28 of Business Central, the ALTool now also provides the ability to compile workspaces of apps. This has the added advantage that the ALTool can compute the dependency graph for the apps in the workspace and compile apps in parallel (if possible). For AL-Go projects with large amounts of apps that can save a lot of time. If you want to try this out you can enable it via the following setting
8
+
9
+
```json
10
+
"workspaceCompilation": {
11
+
"enabled": true
12
+
}
13
+
```
14
+
15
+
By default apps are compiled sequentially but this can be changed via the parallelism property. This allows you to configure the maximum amount of parallel compilation processes. Set to 0 or -1 to use all available processors.
16
+
17
+
```json
18
+
"workspaceCompilation": {
19
+
"enabled": true,
20
+
"parallelism": 4
21
+
}
22
+
```
23
+
5
24
### Test Projects — split builds and tests for faster feedback
6
25
7
26
AL-Go now supports **test projects**: a new project type that separates test execution from compilation. A test project does not build any apps itself — instead it depends on one or more regular projects, installs the apps they produce, and runs tests against them.
@@ -54,6 +73,7 @@ The new setting `postponeProjectInBuildOrder` allows you to delay long running j
54
73
- Issue 2084 Multiple artifacts failure if you re-run failed jobs after flaky tests
55
74
- Issue 2085 Projects that doesn't contain both Apps and TestApps are wrongly seen as not built.
56
75
- Issue 2086 Postpone jobs, which doesn't have any dependents to the end of the build order.
76
+
- Rework input handling of workflow 'Update AL-Go System Files' for trigger 'workflow_call'
![business-central-bot[bot]](https://avatars.githubusercontent.com/in/1194178?v=4&size=40){kind=avatar}
0 commit comments