-
|
Hi, I have an app which is designed to be a helper for writing test apps. It is the only app contained in its repo. It depends on the test libraries and other test apps depend upon it. It has some generic methods for setting up blank companies, creating no. series etc. I'm not sure how I can configure this Test Helper repo with AL-Go. If I add it to appFolders then the build fails because the test libraries dependency cannot be resolved. If I add to testFolders then the CI/CD build succeeds but I can't get the dependency resolution for other apps to work. Maybe because I need to create a release of the Test-Helper app (sorry, still learning AL-Go)? I can't create a release of the app though (presumably because there is no app to release, only a test app?) Any help gratefully received. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Hi @jimmymcp Quite an interesting setup you have there. How do you set up the other test apps to point to your test library app? Do you use appDependencyProbingPaths? |
Beta Was this translation helpful? Give feedback.
-
|
The settings documentation is here: http://aka.ms/algosettings#appdependencyprobingpaths It is mentioned, not not very well described. |
Beta Was this translation helpful? Give feedback.
Alternatively, you can set
appDependencyProbingPaths.release_statustolatestBuild. That way you only need to have a successful CICD in the test-helper repo that contains all the needed artifacts.Using releases is recommended when you have to support multiple versions at the same time.