Closed lvanvugt closed 3 years ago
Yes, we noticed this. The entire testtoolkit is a big mess on Microsoft's side. Depending on the versions of BC, they handle this differently. We're revising this - and this pipeline helps to mitigate the problem. So .. a solution is in the works!
Hey, @waldo1001, good to know it's no me. Have been spending some hours trying to get this right. Is ALOps not making use of the BcContainerHelper? I am asking as that handles it right for any version, afaik.
Would be great if your solution comes fast as this is blocking part of my work right now.
O, and BTW, why is the ALOpsDockerCreate step not failing on this? I would expect it to do, so it's clearly marked in my pipeline. Now it fails on the ALOpsAppCompiler step as it dependant apps are missing in the database.
FYI: having my mind run I tried this workaround, which was successful. But of course it's a workaround as I would like the original issue to be solved so my image will contain the test apps saving a lot of time in my pipeline (approx. 5 minutes) as this workaround every time again will install the apps.
- task: ALOpsAppPublish@1
displayName: 'ALOPS - Install AL TestTool' # install necessary dependent apps for testability
inputs:
usedocker: true
installaltesttool: true
skip_verification: true
install_al_app_names: |
Any
Tests-Bank
Tests-Cash Flow
Tests-Cost Accounting
Tests-CRM integration
Tests-Data Exchange
Tests-Dimension
Tests-ERM
Tests-Fixed Asset
Tests-General Journal
Tests-Graph
Tests-Integration
Tests-Invoicing
Tests-Job
Tests-Local
Tests-Marketing
Tests-Misc
Tests-Monitor Sensitive Fields
Tests-Permissions
Tests-Physical Inventory
Tests-Prepayment
Tests-Rapid Start
Tests-Report
Tests-Resource
Tests-Reverse
Tests-SCM
Tests-SINGLESERVER
Tests-SMB
Tests-SMTP
Tests-TestLibraries
Tests-Upgrade
Tests-User
Tests-VAT
Tests-Workflow
Test Runner
Library Assert
Library Variable Storage
System Application Test
System Application Test Library
Note This workaround enabled the pipeline to continue, but it failed on the ALOpsAppTest step. Another issue has been created for this: #309.
I see you're working with a dev-version of BcContainerVersion ... could you please install a released version - just to be sure?
(latest, if possible)
I see you're working with a dev-version of BcContainerVersion ... could you please install a released version - just to be sure?
Sure.
The workaround pipeline is still running. Will check whether this fixed the original issue.
Update 20210207 @waldo1001: no difference.
Hm,
Can you try to remove all images on your docker server with docker image prune --force
? So that everything is clean again?
I copied your pipeline to my evironment, and I'm not getting your issues .. that's why I ask ..
Busy right now.
Seems to be working. Great.
Great. You see what our challenge is with ALOps? A lot of issues are not even ALOps related ;-).
The above is also a reason why our DevOps agents are dedicated machines: it shouldn't be used for anything else then DevOps tasks .. and should be cleaned (pruned) regularly ..
Right. The prune however did not clean up any of the images. Had to do them one by one. (Admitted: not a lot of experience with pruning so far)
I need to have the full standard test toolkit in my pipeline, so I have set includetesttoolkit for ALOpsDockerCreate to true (see below). But the ALOpsDockerCreate step does not do the job fully (see the full output below):
As can seen below the ALOpsDockerCreate step does stop installing (but does not throw an error. Consequence is that the major part of the test toolkit is not installed and the ALOpsAppCompiler task fails as it does not find the various test (library) apps it depends on. Have been trying various things (f.e. setting
forcecreateimage: $(forceCreateImage)
with$(forceCreateImage)
set to true), but so far to no avail.the used yaml
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
expected behavior All standard test (library) apps installed in the image/container.