How to integrate OnPrem Azure DevOps Server with the cloud one

Question

My company uses the Azure DevOps online edition to manage all of our projects and repositories. Because our internal server network does not have internet connectivity, we were unable to configure CI/CD for the repositories.

To solve the problem, we established a new server with access to both the internet and the internal network. We installed and configured Azure DevOps Server 2019 on the new server. We don't want to switch from the cloud to the internet version of our repositories.

I attempted to link the OnPrem repository to the cloud repository, but it did not work. I issued a PAT on the cloud version and put it as a service connection in the OnPrem version's Pipelines, but I still can't see or link the cloud repositories.

I can clone the cloud repo to the OnPrem server, but I won't get the most recent code because the code is checked in the cloud repository.

Could someone please show me how to connect the two of them?

Answer 1

When I go to Project > Boards in my project, I get a list of all the boards. Only Epic, Stories, and Features work items appear in the Board Page dropdown. I'd like to have Issues, Test Plans, Tasks, and Bugs type work items there as well, so I don't have to go to other pages to see the same thing. But I can't seem to find any setup that will allow me to do so; could you possibly offer a technique for me to get in on single boards?
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops
 

Or take a look at this old blog article, which is where the communication section comes from:
https://devblogs.microsoft.com/devops/deploying-to-on-premises-environments-with-visual-studio-team-services-or-team-foundation-server/

The ideal approach would be to run self-hosted build agents on a server that is accessible via the internet and setup an agent pool in Azure DevOps Services for them. You'll want to use Deployment Groups for deployments and install deployment group agents on target servers, which will only need outbound 443 access to communicate with Azure DevOps Services.

If that isn't possible, you'll have to install deployment agents on the build machine, which will then see your other on-premise servers. However, this is an unsatisfactory solution because you'll either have to rely on WinRm capabilities for deployments or expose too much network between your build server and other on-premise servers.