If you had used Gated Check-In Builds previously in Team Foundation Server 2010, you may have noticed that there was no way to "block" people from overriding the Gated Check-In builds and bypassing the Gated Check-In build.
This became very frustrating because whenever a developer wanted to commit the check-in to TFS Source Control, they could do so and completely avoid the validation checks that were being used as part of the Gated Check-In Build!!
Fortunately, this seems to have been remedied in Team Foundation Server 2013, with the addition of a new build permission called "Override check-in validation by build" in the Security administration area of Team Foundation Server.
Below is a screenshot of the new permissions available with Team Foundation Server 2013 builds:
So now you have a way to actually FORCE your development team to follow Gated Check-In build guidelines!!
This became very frustrating because whenever a developer wanted to commit the check-in to TFS Source Control, they could do so and completely avoid the validation checks that were being used as part of the Gated Check-In Build!!
Fortunately, this seems to have been remedied in Team Foundation Server 2013, with the addition of a new build permission called "Override check-in validation by build" in the Security administration area of Team Foundation Server.
Below is a screenshot of the new permissions available with Team Foundation Server 2013 builds:
So now you have a way to actually FORCE your development team to follow Gated Check-In build guidelines!!
No comments:
Post a Comment