I'm trying to change the release name format like V.1.0.0 in Azure DevOps release pipeline by following Version number counter for Azure DevOps documentation. But the version number counter task is giving the following error:
##[error]The remote server returned an error: (404) Not Found.
Note: The same task I have used in Build pipeline there it is working as expected.
So, please suggest me how to solve this problem.
Related
Hi i'm a newbie to azure devops CID and pipelining.
the azure devops is on premise, my pipeline looks as below however it fails at nuget pack command (2nd from bottom)
the error i get is ##[error]The nuget command failed with exit code(1) and error(Error NU5012: Unable to find 'C:\AzureDevOpsAgents\Agent#1_work\4\s\Code\MyCompany.Core\bin\release\net472\MyCompany.Core.dll'. Make sure the project has been built.
I went into the azure agents directory and the dll is located C:\AzureDevOpsAgents\Agent#1_work\4\s\Code\MyCompany.Core\bin\x64\Release\net472\MyCompany.Core.dll
the difference being the x64, so how i can i get nuget pack to take into consideration the architecture as part of the pack path
variables
ok i as usual every time i post a question on here, despite struggling for hours i manage to solve it.
I've added $(BuildPlatform)\ in front of the default $(BuildConfiguration) for the configuration to package and i can see a package in the location
I am used to run the uploadsummary logging command to add custom information to my builds.
However, I noticed that whereas it is OK to upload multiple summaries for a build (they will be displayed one after another), only the first one sticks to a release stage.
Observe:
Build
##[debug]Processed: ##vso[task.uploadsummary]D:\_wf\06\233\s\Summary1.md
##[debug]Processed: ##vso[task.uploadsummary]D:\_wf\06\233\s\Summary2.md
Release
2021-09-13T16:30:14.4533447Z ##[debug]Processed: ##vso[task.uploadsummary]D:\_wf\02\r1\a\source\Summary1.md
2021-09-13T16:30:14.4536640Z ##[debug]Processed: ##vso[task.uploadsummary]D:\_wf\02\r1\a\source\Summary2.md
Is there something I am doing wrong? Or is it a bug in Azure DevOps Server 2020?
How to upload multiple summaries to a release stage in Azure DevOps Server 2020?
I could reproduce this issue with Azure DevOps Server 2020 and Azure DevOps Services.
It seems that multiple summaries in one task of the release pipeline are not parsed into multiple summaries, but are overwritten. This may be an unexpected issue, but at least it needs to be confirmed with the product team.
To resolve this issue, you could try to use two task to upload the Summary1.md and Summary2.md.
I test it and it works fine on my side:
I am using Azure DevOps Server 2020 and the TFVC repo.
I have a build pipeline and it is currently failing at the Get Sources task while downloading the code. It download half and fails with the error "_Proc should be null. (Parameter '_proc)" (screenshot below for reference)
Can anyone help me on how to resolve this issue?
I am trying to deploy an existing .Net Core application using Azure Devops by creating Build and release pipelines. The build pipeline worked fine, but I get the below error when running the release pipeline (under Deploy Azure App Service).
Error: No package found with specified pattern: D:\a\r1\a***.zipCheck if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.
What should be done to fix this?
This error is because the build task is not configured. You can try to put the below YAML code at the last to make it work.
- task: PublishBuildArtifacts#1
I am trying to run a release pipeline which contains different stages for different sections of the website. However one of the stages throws an error when downloading the artifact. The other stages work as expected.
Error:
##[error]One or more errors occurred. (Dedup size does not match the downloaded size.
I cannot find anything only that explains to me what Dedup is with regards to Azure Pipelines
This issue seems relevant with the recently event on Azure Devops. In addition, this issue is more for agent.
If this issue occurred on what you are using is Hosted agent, just change to using your private agent to finish the release pipeline. Besides, if you are using private agent, please ensure the version of agent you are using is the latest one: 2.155.1.