This might be not as uncommon as deleting the VSTS account, but this is critically important to the end users. Up until now, there was no way to recover the deleted VSTS git repository. However, with the launch of new version of API, there is now a way to recover them and keep our jobs for another day.
However, this functionality is not yet available for GUI lovers and for now, available at API level only. In this blog post, we’ll learn how to restore a deleted git repository by using REST APIs inside postman tool. However, you can use any REST client for this purpose. Continue reading “Recover the deleted VSTS Git Repository”→
This is one of the rare occurrence but one may come across this scenario. Once a VSTS account is deleted, Microsoft keeps it for 30 days (although in a deactivated state). So it is possible to recover the deleted account during those 30 days.
In this blog post, we’ll learn the steps required to restore a deleted VSTS account. For this post’s purpose, I’ll delete my personal VSTS account i.e. mohitgoyal.visualstudio.com. Only a VSTS admin can delete the VSTS account. Since I am the owner of the account, so I have this privilege.
In the handsight, we’ll also know how to delete the VSTS account 😉
Code review or Peer code review is a well known practice in software development, where code written by one programmer is reviewed thoroughly by his peers. In some cases, it is reviewed by one’s seniors as well. When done correctly, peer reviews save time, streamlining the development process upfront and drastically reducing the amount of work required later of Quality Assurance teams. Reviews can also save money, particularly by catching the types of bugs that might slip undetected through testing, through production, and into the end-users.
As part of best practices, your source code should always in working state so that it can be readily made available in case of the disaster. The easiest way of maintaining this is by making use of various branches for source code modification and merging only valid source code changes in the master branch. Also build and release process is often set on the master branch so that you can always deploy release from working source code. So it becomes further important to protect your master branch from unwanted changes. In this blog post, we’ll discuss how to protect master branch from unwanted changes in VSTS by making use of both permissions and code policies.
We recently came across this situation, while we were trying to integrate unit testing for one of the applications into VSTS build definition. So strangely enough, all of the test cases were passed but still the task failed:
The combination of technical and cultural processes behind databases makes automation difficult. Databases has a state associated with them, so you cannot blow them away like application code and create again from scratch without losing the data. Managing change in a way that doesn’t impact the data is very problematic. Combine that with the cultural issues, the silos, it creates a really difficult problem. There are some general best practices that you can apply to tackle a lot of this complexity, but any time you try to design the solution and get into the technicalities, a lot of time you end up implementing something very specific to a particular type of database. In this blog post, we’ll learn how to use SSDT to implement continuous integration and deployment for SQL database Schema to take some of these worries away.
Any software development team working on a software product generally needs to consume the components either already developed by another team in their organization or another third party organization. So they require a mechanism through which they can create, share and consume the source code. Most often a times, this code is bundled into “packages” that contain compiled code (as DLLs) along with other content needed in the projects that consume these packages.