waldo1001
commented
1 year ago It is related, indeed...
Closed SorenKlemmensen closed 11 months ago
waldo1001
commented
1 year ago It is related, indeed...
DanielGoehler
commented
1 year ago We have the same problem:
- task: ALOpsDockerCreate@1
displayName: 'ALOps - Create Docker Image'
inputs:
artifacttype: 'Sandbox'
artifactcountry: 'de'
versionselect: 'NextMajor'
sastoken: '$(sasToken)'
- task: ALOpsDockerStart@1
displayName: 'ALOps - Start Docker Container'
- task: ALOpsDockerWait@1
displayName: 'ALOps - Wait for Docker Container to start'
inputs:
search_string: 'Ready for connections!'
- task: ALOpsAppPublish@1
displayName: 'ALOps - Install AL TestTool'
inputs:
usedocker: true
installaltesttool: true
install_al_app_names: |
Tests-TestLibraries
System Application Test
System Application Test Library
Any
Library Assert
Test Runner
Permissions Mock
Library Variable Storage
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-SMB
Tests-TestLibraries
Tests-Upgrade
Tests-User
Tests-VAT
Tests-Workflow
strictappnames: true##[section]Starting: ALOps - Install AL TestTool
==============================================================================
Task : ALOps App Publish
Description : Publish AL Extension to Business Central
Version : 1.454.3402
Author : Hodor
Help : Publish Business Central extension to service tier.
==============================================================================
*** Validate configuration
*** Task Inputs:
name value
---- -----
usedocker True
fixed_tag
installpublishedapps True
installaltesttool True
install_al_app_names Tests-TestLibraries...
strictappnames True
nav_serverinstance BC140
artifact_path
nav_artifact_app_filter *.app
skip_verification True
forceinstall False
forcesync False
publish_scope Global
tenant default
batch_publish_folder
publisherazureactivedirectorytenantid
blocksymbolsonly False
*** For documentation, please visit : https://www.alops.be/documentation
*** Importing required PS-Functions
*** Initiate Docker Session
*** Set Docker Container ErrorActionPreference = Stop
*** Install AL TestTool: True
*** Start AL-TestTool installation
*** Import NAV/BC Management DLL's
*** Loading assemblies for ServiceTier [BC].
*** Loading assemblies from: [C:\program files\microsoft dynamics nav\220\service]
##[error]AL-TestTool installation failed: Cannot find path 'C:\program files\microsoft dynamics nav\220\service\Microsoft.Dynamics.Nav.Apps.Management.dll' because it does not exist.
*** AL-TestTool installation finished.
*** Disconnect Docker session.
*** Remove Docker session.
*** Docker session removed.
*** AL-Extension Published to ALOps Repository
*** Cleanup VSTS Environment: True
##[section]Finishing: ALOps - Install AL TestTool
AdminHodor
commented
1 year ago Dear @DanielGoehler , @SorenKlemmensen,
Could you please try our latest release v1.455.3559 ?
Kind regards,
DanielGoehler
commented
1 year ago @AdminHodor Now different errors have been produced: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Do I need to install .NET Framework 6 on every build agent?
##[section]Starting: ALOps - Run TestSuite
==============================================================================
Task : ALOps App Test
Description : Run AL-TestSuite for Business Central
Version : 1.455.3559
Author : Hodor
Help : Run Business Central Test-Suite and collect results.
==============================================================================
*** Validate configuration
*** Task Inputs:
name value
---- -----
usedocker True
fixed_tag
nav_serverinstance BC140
tenant default
companyname
profile
bc_username
bc_password
bc_authentication NavUserPassword
bc_webclient_url
testfilter
disabledtests TestApp/DisabledTests.json
show_available_tests True
import_testtoolkit False
import_action Skip
testpage 130455
testsuite DEFAULT
extensionid
installaltesttool False
failed_test_action Ignore
override_finsql_path
resultfilename TestResults.xml
testrunnercodeunitid
*** For documentation, please visit : https://www.alops.be/documentation
*** ALOps License:
* Licensed To: prisma informatik GmbH (Organisation License)
*** Importing required PS-Functions
*** Working folder: C:\agent\_work\640\s
***
*** Load DisabledTests: C:\agent\_work\640\s\TestApp\DisabledTests.json
*** Prepare Docker Session
*** Connect Docker Session
*** Initiate Docker Session
*** Set Docker Container ErrorActionPreference = Stop
*** Copy Modules to Docker
*** Setup Docker Session
*** Checking for container-specific Test Assemblies
*** Using container-specific Test Assemblies
*** Import Modules in Docker Session
*** Import UI Client [C:\Run\DevOps\BCAppTest\bin\Microsoft.Dynamics.Framework.UI.Client.dll]
AUSFÜHRLICH: Loading module from path 'C:\Run\DevOps\BCAppTest\bin\Microsoft.Dynamics.Framework.UI.Client.dll'.
*** Import NewtonSoft JSON [C:\Program Files\Microsoft Dynamics NAV\220\Service\Newtonsoft.Json.dll]
##[error]Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
##[section]Finishing: ALOps - Run TestSuitePlease try our latest release v1.455.3571.
Kind regards,
DanielGoehler
commented
1 year ago @AdminHodor Now it works 👍 Thanks.
Describe the bug When installing the TestTool we get the error
[error]AL-TestTool installation failed: Cannot find path 'C:\program files\microsoft dynamics nav\220\service\Microsoft.Dynamics.Nav.Apps.Management.dll' because it does not exist.
I expect this is related to #608 already reported and the change Microsoft is doing to the dlls
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior That they install as in every other version :-)