Our organization has a team of developers in multiple different locations. A new developer has made a change which results in the organization’s application not working properly. The company had backups to correct the issue, but their backup system did not have current backups. They had to use 1-week-old backups to get the app functional and 40 hours of dev time to get it working the way it used to work. Other than having checks and balances for backups running properly, or better controls in place for new developers, we need a solution that helps prevent this issue from occuring again and also make the source code more centralized. This will make it easier for the developers to work on the app from multiple different locations since the company has offices in three different locations.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Create a Repo Using the Web Portal
- Go to https://dev.azure.com/.
- From the repo drop-down, select New repository.
- In the Create a new repository dialog, verify that Git is the repo type and enter a name for the new repo.
- Select Create.
- Clone the Repo
- From the web browser, open the team project for your organization in Azure DevOps and select Repos > Files.
- Select Clone in the upper-right corner of the Files window and copy the Clone URL.
- Open the Git command window (Git Bash on Git for Windows) and browse to the folder where the code should go on the computer. Run
git clonefollowed by the path copied from the Clone URL in the previous section. - Switch directory to the directory with the cloned repository.
- Work with the Code
- Browse to the folder with the cloned repo and open the
README.mdfile. - Make changes and then save the file.
- Commit the changes.
- Go to DevOps Portal to confirm the changes are reflected.
- Browse to the folder with the cloned repo and open the
