Release branch and Dependancies

[CPretorius1986]

Afternoon All,

We are using a long term service branch, and need to do a pull request build.

When the system is pulling dependancies it is pulling from the main branch or latest version

I have changed to force the release to look in the Release/26.8 branch for releases.

I have also tried specifying a version

However having no success.

Any advice would be appreciated

[mazhelez]

Hi @CPretorius1986

A couple of clarifying questions:

• Is your PR targeting main or release/26.8?
• Are you looking for setting up PR incremental builds: only the changed apps (and their dependants) are rebuilt, the rest is taken from the latest successful CICD build on the target branch of the PR?

[CPretorius1986]

The first app, is building

Second app that depends on the first is not because the version being found to build is not correct finding a v27 instead of a v26

[mazhelez]

@CPretorius1986 Can you please provide a full log? It'll be easier to get the full picture.

[CPretorius1986]

logs_54959170856.zip
attached

[mazhelez]

It seems you have three AL-Go projects in the repo, that depend on each other but useProjectDependencies is set to false. That way AL-Go would build them in parallel. Try setting useProjectDependencies to true. Alternatively, you can try to place all the apps in a single AL-Go project. That way AL-Go would figure out the build order of the apps based on the dependencies in app.json.