I'm using Azure DevOps for deployment activities (releases in yaml way)
From time to time I have to re-run stages if it fails,
The problem is that when I click on Show Previous Attempts nothing happens and I can't see Attempt #1
Is anybody facing the same? or any ideas how to fix it?
After investigation, this issue has been confirmed as a bug and reported to the product group. Currently a fix for this issue has been prepared and the status is pending release.
You can keep track of this issue in our Develop Community forum. We'll update you when it’s available.
Related
I am tasked to verify why expired builds are not deleted in my company's locally hosted Azure DevOps server.
When querying the SQL Database I find that there are very few deleted builds and most of those were manually triggered.
Most of the builds aren't actively retained.
I found this question which asks pretty much the same question I am asking but does not seem to have an answer. To me it looks like there is an infrequently found bug for cases like this, which has not yet been diagnosed. My question is: is there a way, for instance via REST API to trigger the deletion of Builds as defined via the DevOps Admin interface?
On further review, I discovered that what actually seems to be happening is that DevOps, though updated to the latest release, seems to be applying per-Pipeline rules. One of the pipelines has this custom rule: and I have evidence that tells me that the builds are being deleted as per that rule.
I found the answer in the Developer Community at Visual Studio. Seems to have been a problem that was fixed in their 2020.0.1 Patch 2 Release. I should note, however, that even though the issue is officially closed, there have been a couple of dissenting votes as of this date.
I’m using SonarQube 8.8 on Azure DevOps.
It’s work just fine, I have analyzed severals applications. However i have a problem on some applications:
When I run the pipeline it get's stuck in queue indefinitely "The agent request is not running because all potential agents are running other requests. Current position in queue:"
But as soon as I remove the sonarqube tasks, the build works just fine. There is no error message so I have no clue about where the problem may come from.
Can you please help
In your current situation, we recommend you can check your agent pool and make sure your all agent is available. And please check your parallel jobs. Also, we recommend you can try to create more self-agent in your local machine and try to run this pipeline.
And you can refer Sourav's answer in the comment.
More details about this issue you can refer this doc: You don't have enough concurrency
I have manually deleted a CI build that uses the MS Hosted ubuntu Agent as there was no Cancel option that was showing up. The elapsed time I think shows the build was deleted, but I see that the Hosted Agent continues to show that the build is in progress.
This is the first time I am running in to this situation. What is the best way to abort this build. I tried using the APIs here and here but that does not seem to help
Thanks
After investigation, there is a recently event of availability degradation of Azure DevOps, which affected these services and it has been resolved now.
If you want to know more information, please click here: https://status.dev.azure.com/_history.
Please check that your Cancel option is back to normal.
I am using Azure DevOps pipelines releases to try to deploy a windows service on premise. Periodically, the windows copy files step will hang and try again every 30 seconds and output "The process cannot access the file because it is being used by another process" as it attempts to copy the build artifacts.
We've ruled out any kind of permission issue. We've tried all sorts of tools to see what might be locking these files up and they don't tell us much.
This has happened before in the past with some other projects I was also trying to release on premise. Sometimes, I am able to just wait an hour or two and redeploy successfully (not exactly a solution I'm satisfied with), but this one particular project, a windows service, seems to be experiencing the issue very, very frequently. Almost every time I try to deploy.
Has anyone else experienced this? Or any word from Microsoft on the issue?
Thanks in advance.
I experienced this issue while trying to create and deploy a release from an existing artifact. So I have a build pipeline on Azure Devops that generates artifacts to be used by the release pipeline. All I did was to make a commit that triggered the build pipeline which generated a new artifact and triggered the release and it worked fine.
It was the first time I experienced this and I had no clue on why it happened.
I'm going to be doing more research and share any thing I find helpful.
I am having difficulties with the last two projects I have created using gated check-ins in Azure DevOps.
The error I receive:
[Error]The shelveset [ommitted] could not be found for check-in
We are using an onpremises agent and the last two projects I have created get this error on the gated check-in. However, our older apps that have identical build pipelines seem to be working fine so I do not understand why this is happening.
Does anyone have any ideas?
I was able to reproduce the same issue on my on premise agent as well as hosted agents. After investigating it seems like the account conflicts cause this error, that the build agent trys to check in the shelvesets with build service account other than you own account.
The same issue has been submitted to Microsoft. You can vote it up and keep track on it here, or your can submit a new issue regarding this issue on the same site by clicking on "Report a problem".