Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
We’ve received the question “why are you storing your releases on AWS and not on Azure” for projects, such as the vsts-agent and ALM-Rangers/Migrate-assets-from-RM-server-to-VSTS.
For example, when you’re downloading a release from either of these projects you’ll notice amazonaws in the download URLs, as highlighted below:
Both projects, and others, are open source solutions (OSS) on GitHub and storing their releases there. It happens that GitHub uses AWS to store our release artefacts.
If we look at the ALM-Rangers/Migrate-assets-from-RM-server-to-VSTS project, we’ll note that its pipeline is hosted by ❶ Visual Studio Team Services (VSTS) on Azure. When we ❷ commit code to the GitHub repository, the continuous integration build is ❸ triggered, followed by ❹ automated tests, storage of the ❺ release back to GitHub, which rolls it out to the ❻ Amazon cloud.
It’s a great showcase of using two cloud computing solutions to implement a CI/CD pipeline for an open source solution.
Reference information:
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in