Is there a way to change/edit the build steps for gated checkins on Visual Studio Team Services/Visual Studio Online? Currently it mirrors the same steps we have set up for our development branch (ei publishing drop files when it doesn't really need to) and looking at the build definition where we've got gated checkins enabled there doesn't seem to be any options which specify such a thing.
No, there isn’t such feature on Visual Studio Team Services.
Just clone a build definition and remove/disable steps/task, then check Gated Check-in for this build definition.
Related
I found info to set a policy such as check in on each computer in Visual Studio but I am hoping to set it in VSTS 2017 for all project team members.
Is there such a way?
I assume you're talking about TFVC check-in policies.
For policies to work, the associated policy assembly has to be installed for each user on their local PC. There is no way around this.
Policies only apply within Visual Studio. There is nothing preventing someone from bypassing the policy entirely by removing the assembly from their computer, by using the editor in the web portal, or by directly interacting with source control via code or the TF.exe command line utility.
My development environment is set up behind a corporate proxy through remote VMs. We uses Visual Studio as the main platform for our code developement , so we had no issue with code review process as Team Foundation Server have this feature.
However recently, we switch to eclipse while still maintaining the projects in TFS. Eclipse have TFS plugin which is good as we can continue on from our previous track without much effort. The only thing missing is the code review.
So, is there anyone who worked using TFS and eclipse in offline mode behind a corporate proxy, have an alternative way to do code review just like visual studio + TFS.
It's based on which version control system your team are using.
If you are using GIT as source control.
For now, the Team Foundation Server plug-in for Eclipse (Team Explorer Everywhere) supports pull requests to review code and collaborate with members of your team.
Collaborate
Work and code together
Use pull requests to review code and collaborate with members of your
team. Triage and track comments at each stage of the work to ensure no
feedback gets lost. Finally, configure merge, build, and review
policies for your Git branches and stay up-to-date with alerts.
Source: Team Explorer Everywhere
If you are using TFVC as source control.
There is no this function in the plug-in directly. You may need to use 3-party code-review plugins to achieve it. Such as SonarLint, Checkstyle Plug-in...
If you want to enforce Code review before any checkin in TFS server. You may need to use check-in policies which can evaluate whether the pending changes meet the validation requirements before they can be checked in to the server. So, if the code review through Sonar can be called programmatically, then you can build a custom check-in policy that calls Sonar inside the Evaluate method.
We currently use Visual Studio Team Services for our source control. Unfortunately, we do not use the project planning capabilities with VS team services. Meaning when we check-in code we do not map the source code to work items in a sprint.
Is it possible to query line of code changes for specific dates and certain application/solution from VS Team Services?
Both Git and TFVC have this information available, by linking your Visual Studio Team Services account to Power BI. The Git Activity and TFVC Activity reports provide a starting point, though for now the period you can report on is limited.
TL;DR: is it possible to set up gated check-in for one solution in Team Project so that this won't mess with other (non-related) code in same Team Project?
Detailed:
We have TFS Team Project with several solutions in it, each in separate folder.
Most of those solutions belong to dev team and are built daily using build server.
One solutions is for QAs, it contains automated UI tests.
Now we want to set up gated check-in (by instructions from here and some other docs)
This involves creating a build definition and CI trigger for it.
But it seems to us that a build set up like this will be triggered on each commit to the Team Project, not only on those performed by QA team.
So, question is if we can do gated check-in for our QA folder without migrating to separate Team Project and messing with devs.
Thanks.
EDIT: Related question
Your gated check-in build will be always triggered when you change something in the folders specified in the build definition workspace. Set up your build definition workspace to include only folders used by QA solution and cloak folders used by others if possible.
I'm intrigued by the idea in TeamCity of pre-testing commits (i.e. verifying they don't break the build before allowing check-in to occur) and I'm wondering if there is any way to implement this in TFS. It looks like TeamCity can interface to TFS version control as a backing store but of course I'd prefer a free solution.
In TFS there is the notion of check-in policies where you can execute code on the client and that can validate check-ins before allowing them to occur. However - what you are after sounds more like the notion of a "Gated Check-in" where a build is attempted on a central build server before the check-in is committed to the main code base. Take a look at the BuddyBuild project on CodePlex to add that functionality in the current versions of TFS.
In TFS 2010, gated check-in builds will be a feature out of the box.