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.
Related
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.
The company I work on recently purchased SonarQube Enterprise to improve code quality throughout all repositories. I found out that there is a feature that enables SonarQube to comment automatically on PRs targeting a specific branch, and I successfully managed to try that out.
Thing is:
That configuration is not scalable: I would need to manually configure every repo to follow that rule
That configuration needs a build pipeline to be defined "old school" on Azure DevOps to work, and we are moving into Pipeline as Code, starting of course with CI (where this takes place)
Anyone managed to get the PR commenting working in that scenario? Or, at least, solving the #1 problem?
Cheers
You can use REST APIs to do whatever configuration you need to do across your repositories. Refer to the REST API documentation.
Shouldn't matter, although I haven't tested it. The SonarQube tasks aren't aware of whether the build source is YAML or visual designer/classic/JSON builds. The underlying tasks and job running architecture is the same. As long as the build is hooked up to a branch policy, it should still work.
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 cannot deploy a release in Azure DevOps Server (on-premise). Whenever I do, Azure DevOps Server shows a "loading" spinner and hangs:
The spinner is shown forever:
There are two other users in our team who share the same issue I have. I've been assigned Azure DevOps Server Administrator rights, still I cannot deploy, so it isn't a rights issue.
I've been logging into another Windows machine, been using other browsers ... yet, to no avail. I always get to see the spinner only.
Strange enough: Other users in our team can deploy releases in our project flawlessly. Currently, it's only three persons in our team who observe Azure DevOps Server hang. Even we could deploy releases until two weeks ago. No-one has changed anything. It suddenly stopped to work for three of us (me included).
I suppose it's a bug in Azure DevOps Server.
What's causing this behaviour? How can we cope with it?
EDIT:
These are the JavaScript warnings I get to see when using IE 11:
It seems like the error is based on the fact that we separated our boards from the repository in Azure DevOps.
In Azure DevOps we created a common board for all projects, but we left the projects themselves in their own Area. Then we moved the boards' items to the new overall board while we left the repositories at their original location (Area).
This seems to cause the hang when a repository's board gets disabled.
Re-enabling the repository's (now obsolete and redundant) board solves the issue.
After installing Release Management client and connecting to my Visual Studio Online account I only see 4 actions.
Online I see that other people have a lot more actions in their toolbox:
What you are seeing is correct since in VSO you do pretty much everything in PowerShell using the Deploy Using PS/DSC action. I have a blog post series on Continuous Delivery with VSO here that might be of use in understanding how to get going.
As Graham pointed out what you are seeing is correct. On VSO RM only supports the DSC/PowerShell (vNext) pipelines. But the on premises product also supports the Agent based solution which is where you see all the additional actions and can add our own.
If you look at how the Agent based actions are created most are PowerShell and you can modify the PowerShell to work in a vNext pipeline. Here is an example of making a script work in both. That would require that the PowerShell be a part of your project so RM would be able to execute it during your release. Not as nice a solution as the Agent based but the next version of RM will address both of your concerns. There will be a way to establish a secure connection with Azure and a way for you to add custom actions or “Tasks”.
Keep an eye on DonovanBrown.com or follow me #DonovanBrown, I have blog post ready that I can’t post until the new RM is released. Before anyone asks I don’t have a date.