azure-pipelines-agent: [BUG]:
What happened?
warning resulting in an error later in the pipeline with agent 3.220.1 2023-05-09T10:09:43.4362072Z ##[warning]Artifact does not contain any files to download. 2023-05-09T10:09:43.4381870Z 0 placed file(s): 0 downloaded, 0 empty
The artifact does exist and job works with agent 3.220.0
downgraded the agent from 3.220.1 (pre-release) to 3.220.0 (latest release).
The job is using the xldeploy plugin and should upload the build artifacts to xldeploy.
Versions
Azure DevOps Server 2020 Update 1.2 agent 3.220.1
Environment type (Please select at least one enviroment where you face this issue)
- Self-Hosted
- Microsoft Hosted
- VMSS Pool
- Container
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2020 Update 1.2
Operation system
Windows 2016 (10.0.14393)
Version controll system
No response
Relevant log output
2023-05-09T10:09:43.4362072Z ##[warning]Artifact does not contain any files to download.
2023-05-09T10:09:43.4381870Z 0 placed file(s): 0 downloaded, 0 empty
##[error]Task ended with an exception: Error: No package was found using search pattern 'c:\Agent\ws\r16\a\xxxxx\xxx-dar *\dar-xxxxx *.dar'.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 6
- Comments: 19 (6 by maintainers)
@ismayilov-ismayil : here are two logs. The first with a dot-named artifact showing only a single match (the folder) and the second targeting the same build pipeline with a dotless artifact name producing 2 matches (the folder and it’s zip file).
artifact name: lob.core
artifact name: build
Hi @markatky46 could you please advise what is your organization name? And I will check why you got pre-release version. For security reasons you can e-mail me your organization name: v-lisabitova@microsoft.com
We’ve rolled out the related changes for this issue. Feel free to reopen the ticket in case you face any problem.
There’s been a new agent version pushed
3.220.2
We’ve tested it and it’s resolved our problem with downloading artifacts.
Hi @Ondrashx @svbrburgman @kauemendes @kraduk @MATTHEWTAYLOR1995 @epmenard Could you please also share the names of your ADO organizations. For security reasons you can e-mail your organization names here: v-lisabitova@microsoft.com
Need them to define which changes in the vss api package caused the issue. Thank you.
We are also seeing this issue. We are unable to downgrade the agent as we use VMSS instances that are ephemeral. We identified a quick fix without downgrading the agent: ISSUE:- task: DownloadBuildArtifacts@1 This task is downloading the container but its not downloading the contents in the container ie., zip file. Hence facing the path error.
FIX:- download task version to 0: DownloadBuildArtifacts@0
May i ask also why a pre-release version has been rolled out and being consumed like a general release by my cloud service? Is there any way for us to select only general release versions?
Thanks all for providing the example pipelines and details! We were able to reproduce the issue and define the root cause and we’re working on fixing it.
@svbrburgman @epmenard @Ondrashx @kauemendes @kraduk @MATTHEWTAYLOR1995 Could you please provide example pipeline YAML-file? Because we cannot reproduce the issue.
Hi, we run into similar issue yesterday. What helped was to rename the artifactName of the published task, so it does not contain any dots. So, e.g. from ENV.Release -> ENVRelease. The download task than was able to download all the files in artifact.