I'd like to raise an Azure DevOps support ticket for an issue we're experiencing with a number of agents (they seem to go down overnight for no reason).
Would appreciate some advice on where and how to raise this ticket with Microsoft.
You can ask your question here: Developer Community. They try to reproduce your problem and communicate with the product team to resolve it or include a new fix to next releases.
Related
I have a bulk of workitem in azuredevops project. I want do delete the comments inside all of them, even the comments raised by others. Is there a way to do it? I tried with delete comments api and it gives me an error: VS403664: Unable to update the comment xxx, you must be a creator of the comment to update it
I was also facing the same issue.
Delete comment feature is now no longer supported in azure devops because in recent time azure devops architecture has been changed due to that it is not providing
comment id to each and every comment hence it's not possible to distinguished each and every comment and because of this issue deleting comment is not supported by azure devops.
unfortunately in the azure devops docs it's not updated yet.
I hope this will be helpful.
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 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.
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".
I have a VSTS repo connect to SonarCloud for quality analysis.
I need unique issues source for my team.
When SonarCloud create issues in his system, I want create an equivalent issue in VSTS.
And, when the issue in VSTS closed by a commit, I want close SonarCloud issue.
Can you help ?
Same question with GitHub...
Thx
Although there are issues created during an analysis in SonarCloud, the result is passed. So it won't create bug work item for such builds in VSTS.
The SonarCloud extension itself can not achieve what you want, one workaround here is using SonarCloud api and VSTS REST API to implement your own solution.