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.
Related
My organization recently changed from using personal GitHub accounts to using GitHub Enterprise Managed Users. Since that change our pipeline continuous integration (in Azure Devops) has stopped working. We can still run the builds manually without issue, but it isn't even attempting to start the builds automatically. I've created new personal access tokens for the pipelines, but that hasn't fixed the continuous integration. Does anyone have any suggestions on what I should look at to get this working again?
Instead of relying on user-authenticates service connections between GitHub and Azure Pipelines, I recommend switching over go the Github App for Azure Pipelines to control what repositories Azure Pipelines can access:
https://github.com/apps/azure-pipelines
That will drastically simplify access maintenance between GitHub and Azure Pipelines and will break the reliance on personal or enterprise managed accounts.
I wound up fixing this by going to the repository in Git Hub, go to settings on the repository, and then to Web Hooks. In there, the hook that Azure Pipelines uses had an error on it because when our tech group migrated the repo they did not bring the secret over. To fix it I just had to delete the web hook, go to the pipeline and a button appeared to restore the connection.
I have two VS solutions (test and production), mapped to respective Devops repositories.
Everything was working well, until a network crash occurred. after intranet connection was restored, I realized that Devops test repository does not recognize pending changes to my VS test solution. Instead, mapping from VS production solution to Devops production repository seems to work correctly.
I tried to cancel and re-create mappings, but Im still facing that issue. how can I fix it?
thanks
Please try the following items:
Go to web portal, to see whether you can access the test repository as normal.
If you can access the test repository, check whether you use the same account to access the repository in VS.
Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService.
Clear Azure Devops Service caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache.
Re-launch the VS and try to connect to service again.
Check how many workspace you have and whether you selected the correct workspace.
I am using the free tier (though open source) of both Github and Azure pipelines. I am doing a C# boot camp and there are several active students making a few dozens weekly PRs. Normally, everything works, build is run on every new PR. However, today I see that none of the checks get triggered. Has anyone had any similar issues? What could be wrong?
Here is an example that illustrates no checks being done, regardless of pipelines being there and integration to azure installed:
https://github.com/csinn/CSharp-From-Zero-To-Hero/pull/222
P.S. I made no changes to the pipelines in the past month.
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".