Right now we are using the Cross-Platform CLI for Team Explorer Everywhere to do work on Linux. I want to have a check-in policy that forces users to add a comment to their checkin. Based on this page https://msdn.microsoft.com/en-us/library/gg475890(v=vs.100).aspx it seems like if I use the web interface or Visual Studio, or Visual Studio Command Line these policies won't apply. However, this page doesn't seem to give any information on how to do it using the command line and I can't find info anywhere else. Is there a way I can do this via the Linux command line or even a standalone app, or do I have to use Eclipse?
The Team Explorer Everywhere (TEE) Command-Line Client (CLC) cannot configure check-in policies and the TEE Eclipse plug-in must be used.
Related
I am trying to automatically configure the TF Workspace for all users when they login on a PC which is different from what they normally code on.
I am currently running the following to configure the workspace via a logon script
./TF.exe workspace /new /collection:azuredevops.url/project /permission:public /location:Server /filetime:current /noprompt
But when the user starts Visual Studio in Team Explorer it is not enabled /online for the user.
Even the "Connect to a project" is empty
How do I configure this in PowerShell or CMD using TF or any other function?
In the command line you are using, I see you set the value of the option /collection as "azuredevops.url/project".
According to the docs about tf workspace command (see here):
/collection: Specifies the project collection.
It seems that the value of the option /collection should be set as the collection URL.
I tried both the collection URL and the project URL in the command, only the collection URL did work, the project URL returned error.
In addition, you can manually try the following command on the machine,
tf.exe workspace /new /collection:<collection URL>
to see if it can normally pop-up the window like as the screenshot shows below.
This can verify if the tf workspace command is working on your machine.
[UPDATE]
The TF.exe is a tool that integrates some interfaces of Azure DevOps. It helps you set up the configurations of TFVC workspace on background, instead of manually filling the parameters via the VS UI. It's not a VS integrating tool that can fill parameters on the VS UI.
When you open VS, to automatically connect the project on the VS UI, you need to use the VS integrating API (or interfaces collection) to achieve the operation on the VS UI. However, currently, we have no such API or CLI to do this. So, you need to manually connect the project after opening VS.
I'm using Git with WebStorm's version control already, but have to use TFS version control. After some research fond this plugin but there is no tutorial that aiming to configure that plugin.
Can anyone guide me?
You can opt for using git tfs, locally you can still use Git and all of the advantages you're used to. And then push from git to TFVC. You'll need to install Team Explorer or the Team Explorer Cross Platform Commandline Tools.
Or you can use the native plugin for, thelatest version of the TFS / Azure DevOps (Server) plugin can be found on the Jetbrains site. It requires TFS 2015 or newer. You can use the plugin you found for older versions of TFS.
A good explanation to get started can be found here. The part to configure TFVC is replicated below.
Visual Studio Team Services plugin and TFVC
Before starting with TFVC, we need an external tool. The tool in question is TF command line tool. It ships with the Microsoft Team Explorer Everywhere 2015 and you can download it here.
The file we are interested in is TEE-CLC-14.0.3.zip. Download it and unzip it in a folder of your choice. You should end up with something similar to this.
Now, open the command prompt, move into the folder where you have extracted the TF command line tool and run the following:
tf eula /accept
If command succeeded and you haven’t received any error, you are good to go.
Now back to IDEA. Open the settings panel.
and move to Version Control -> TFVC pane. In the select path to executable field, enter the exact path to the tf.cmd command file located in TF command line tool folder.
Once done, press the test button and you should see the following message
Confirm all of the open windows and get back to the IDEA welcome page. Now you are ready to choose Team Services TFVC (Preview) version control.
At this point, same as for Git, you will be prompted about the connection towards your TFS. The following dialog will be shown.
Move to the Team Foundation Server tab and specify the address of your TFS server, then click connect. You will now be prompted for the credentials and if everything is ok, you will be shown the list of available TFVC repositories.
You can now create a new workspace directly from IDEA and start working with your TFVC repositories.
Is it possible to manage (create, change state, remove) project WorkItems from TEE CLC?
Looking at help and options, it doesn't seem possible, but eclipse version and SDK clearly make it possible.
A pointer to a doc would be appreciated.
Usually, command lines for managing Work items we are using are witadmin destroywi (destroy work items) and tfpt workitem (create or update work item). But, witadmin command-line tool installs with any version of Visual Studio, and tfpt workitem command-line tool installs with TFS power tools which works with VS client. Neither of them supports Team Explorer Everywhere Command Line Client.
I'm afraid there is no Team Explorer Everywhere Command Line Client command for managing work items.
As CeCe writes, there isn't any cross-platform tool to managed work items similar to witadmin or tfpt. Also, the TEE CLC uses the TFS SDK for Java but the CLC is packaged up in the download for convenience. There should not be a dependency between the plugin and the CLC.
Our shop uses Visual Studio Team Services, previously Visual Studio Online, for SVN and Builds.
We are trying to find a way to download the drop package (build zip) via the command line. For this purpose, we stumbled upon TFS Drop Downloader which appears to be made for this very reason. Unfortunately, the last revision was made in 2013 and does not appear to work with Visual Studio Team Services anymore. When we supply the parameters (collection, username, password, etc.) it asks again for credentials via a Windows dialog and all attempts seem to fail.
Is there another way to download the builds from Visual Studio Team Services via the command line?
Sample command line:
C:\> tfsdropdownloader /c:https://project.visualstudio.com/DefaultCollection /t:"Project Name" /b:"Build Definition" /u:username /p:password
Even though we supply username and password, the tool asks for credentials again via a Windows dialog and fails even when supplied.
I have web site project hosted at TFS Cloud. And I have hosting account at Godaddy, which allows me to deploy sites via FTP only.
I create publishing profile in Visual Studio 2012 and can successfully execute publishing to FTP in Visual Studio.
The problem:
This the task cannot be done using any standard TFS Build template and neither its standard workflow activities, even though it should be a trivial thing people do with TFS Build server. There is no ready "copy-paste" solution (wpp.targets) on MSBuild for that:
"C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Deploy\Microsoft.Web.Publishing.Deploy.FTP.targets"
Clearly says that it is not supported through the command line, one should use VS for that.
Question:
Is there any implemented solutions of that task that I can just copy paste to my team project with few clicks?
I expected to see lots of articles about it in web, however I didn't find any simple existing solution. Articles like this require me to install some 3rd party software (which is not an option in most popular hosting like Godaddy), and it's not clear how to use it with TFS.
In the default Build template, go to the process section and choose Msbuild Arguments and give the publishing profile.
MSBuild Arguments : /p:DebugSymbols=false;DebugType=None;DeployOnBuild=true;PublishProfile=YourProfileName
when Build got succeeded, it will be deployed to the ftp location.
this link may help you more : http://www.hanselman.com/blog/TinyHappyFeatures3PublishingImprovementsChainedConfigTransformsAndDeployingASPNETAppsFromTheCommandLine.aspx