Forum Discussion
Thank you for the information and screenshot.
Alas, it did not work for me with the same error about missed task.
Our pipeline is in YAML. Did you do anything else except specifying task as in your example? Do you have administrative permissions in DevOps/for your pipeline?
I noted that you have installExecutor property set to false... Did you uninstalled Adapter before running the pipeline or the task handled roll-back itself?
As some background, hopefully the below helps, the YAML example further down is effectively what we're using as a workaround, to use the prior DevOps task version and latest TestExecute version.
We're running the pipeline on a Windows build agent pool (a VMSS in Azure), those VMs are built using a VM image with TestExecute preinstalled (v15.53.2 in this case), hence our installExecutor and updateExecutor being set to false.
This pool is setup in DevOps with the interactive tests option enabled, this option forces the need to preinstall TestExecute, as the build agent user runs unelevated so can't install/update - https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/scale-set-agents?view=azure-devops#create-the-scale-set-agent-pool
Anonymised example of one of the stages in the pipeline, I've added comments where tasks removed or info randomised.
stages:
- stage: SmokeTests
displayName: 'Smoke Tests (PROJECTNAME)'
jobs:
- deployment: 'SmokeTests'
environment: AutomatedTests
variables:
- group: AutomatedTest-PROJECTNAME-VariableGroup
pool:
name: 'UITestPool'
displayName: 'Smoke Tests (PROJECTNAME)'
strategy:
runOnce:
deploy:
steps:
- checkout: self ## Checks out our TestComplete project/tests
- task: DownloadBuildArtifacts@1
displayName: 'Download Artifact 1'
inputs:
buildType: 'specific'
project: '61b13bb3-6ba0-44a0-9d67-753c0a63752b' ## GUID replaced in this example
pipeline: '1' ## The Build definition ID where published artifact is
buildVersionToDownload: 'latest'
downloadType: 'specific'
itemPattern: '**'
downloadPath: '$(System.DefaultWorkingDirectory)\_Licensing'
## Download build artifact 2, same as task above
## Powershell task modifying Licensing installer name
- task: SmartBearSoftware.install-testcomplete-adapter-task.install-testcomplete-adapter-task.InstallTestCompleteAdapter@1.15040.421
displayName: 'TestComplete test adapter installer'
inputs:
installExecutor: false
updateExecutor: false
accessKey: '$(TestExecuteAccessKey)'
logsLevel: 0
- task: ms-autotest.screen-resolution-utility-task.screen-resolution-utlity-task.ScreenResolutionUtility@1
displayName: 'Set Screen Resolution'
inputs:
displaySettings: specific
width: 1920
height: 1080
## Installation and Licensing tests, same task as below, running different tests
- task: VSTest@2
displayName: 'Smoke Tests'
inputs:
testAssemblyVer2: '**\<PROJECTNAME>.pjs'
testFiltercriteria: 'Group=SmokeTests'
testRunTitle: 'Smoke Tests (PROJECTNAME)'
timeoutInMinutes: 60
- AlexKaras2 years agoChampion Level 3
Thank you a lot for the detailed answer indeed!
> We're running the pipeline on a Windows build agent pool
Probably, this makes a difference... Our pipelines are running on self-hosted pool. I suspect lack of permissions, but did not hear back from our DevOps so far.
Related Content
- 3 years ago
- 4 years ago
Recent Discussions
- 4 days ago
- 4 days ago