We're currently investigating moving from on-premise DevOps to Cloud-based DevOps, there is sufficient migration information and processes, but what happens if we want to reverse it... bring it back in-house?
Is their a migration path for this?
Checked various websites and I cannot find anything that fits.
No, there is not. Azure DevOps is constantly receiving updates and is almost always ahead of any available on-prem versions of Azure DevOps Server. You can't go backwards.
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.
From the point of view of an team admin and user.
Particularly interested in planning tools and boards.
There is no such documentation. However, you can compare some features on this page: Azure DevOps Feature Timeline.
Additionally, Azure DevOps Service continually gets new features. To get new features on Azure DevOps Server, you have to update it.
Example of the last changes on the server on service:
Can someone recommend Help/Service Desk management system which works good with Azure DevOps?
We already have Azure Devops for code management with ci cd and test suites.
I am also considering JIRA service desk management, however thinking a bit scpetical in the lines of having two similar eco systems.
In next few months, we forsee potential clients who makes use of our IT services and would like to support them using service desk management.
Thank you.
By reference to this doc: What features and services do I get with Azure DevOps?, Azure DevOps provide Boards service including Agile process, Basic Process, Scrum process and CMMI process, which is easily sharing information and track the status of work, tasks, issues, or code defects. See: Azure DevOps Labs for details.
In addition, if you use Slack, you can use the Azure Boards app for Slack to create work items and monitor work item activity in your Azure Boards project from your Slack channel. If you use Microsoft Teams, you can use the Azure Boards app for Microsoft Teams to create work items and monitor work item activity in your Azure Boards project from your Teams channel. And Jira, Zappier, Service Now and so on.
BTW, if you use other management system like TeamSupport Help Desk, you could use Microsoft Power Platform to create automated workflows.
After investigation, we found that currently Azure DevOps has no service desk feature, I found a suggestion ticket in Developer community. You can vote and follow this ticket. You can also create a new suggestion ticket here. The product group will review these tickets regularly, and consider take it as roadmap.
BTW, I found this thread: https://www.reddit.com/r/azuredevops/comments/cbkxwz/azure_devops_as_a_help_desk_ticket_system/, which provides several choices, you could check it.
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.
I'm using azure devops pipeline to build my IIS application and deploy via release management to several different servers, and it works great. My issue though is that one of the servers I need to deploy to will always be offline, so I need to set up some sort of offline installer for that deployment. Is there a way to do this using the build and release management I already have that I'm not seeing?
Azure Pipelines assumes that the server is always available. Best I can think of is to generate some kind of drop on a fileshare and then add a Manual Intervention Task to pause the pipeline and allow you to do your thing.
There is no air-gapped agent nor a way to run part of your pipeline on another system and import the results.