I want to create a new team project in TFS2018. The create fails with error TF400797. After some research I discovered when I choose Team Foundation Version Control the creation of a new project succeeds! So, the problem has to deal with Git as our source control provider. We use TFS as our Git Server.
The version of TFS we use is:
Microsoft Visual Studio Team Foundation Server
Version 16.131.27701.1
Related
How can I connect to on-premises TFS using Visual Studio Code? Is that possible the same way as in Visual Studio?
If you need to use Git, all you need is Visual Studio Code. Git is a built-in feature.
In order to also use TFVC you'll need to install an extension. You'll need Visual Studio Code and the Azure Repos Extension and a recent version of Team explorer and/or Team Explorer Command Line Client.
To edit Azure Pipelines (available in Azure DevOps Server 2019), you'll need to also install this Azure Pipelines extension.
The naming is a bit confusing, but these Azure DevOps extension also work with recent version of Team Foundation Server and Azure DevOps Server (new name).
First you need to install the official Azure DevOps Extension for Visual Studio Code which released by Microsoft.
It supports both TFVC and GIT version control type.
Clone your Git repository
With Git, the extension uses the remote origin of your repository to
determine how to connect to Team Services (or your Team Foundation
Server), in most cases you will need to have a Git repository already
cloned locally. If you intend on cloning an existing repository, do so
before proceeding. If you do not have a Git repository cloned locally
but already have a Team Services account (or a Team Foundation Server
instance), you may create a local repository (via git init) and once
you set the "origin" remote for that local repository, the extension
will detect the change to the remote and attempt to contact the Team
Services account (or Team Foundation Server).
Create your TFVC workspace
With TFVC, the extension uses information about the current workspace
to determine how to connect to Team Services (or your Team Foundation
Server). Workspaces can be created using the Visual Studio IDE,
Eclipse or with the JetBrains IDEs (e.g, Android Studio, IntelliJ).
Note: At this time, you will need to have a local TFVC workspace already available on your local machine. More information about the
difference between the two types (and how to determine which one
you're using) can be found here.
You could also take a look at below videos to help get you started using the extension quickly:
Set up the Team Services extension for Visual Studio Code - If
you haven't used the extension before, this video will show you how
to set it up, create a personal access token and get up and running.
Walkthrough of the Team Services extension for Visual Studio
Code - This is a walkthrough of most of the features of the Team
Services extension.
TFVC Source Code Control for Visual Studio Code - This video shows
you how to set up the TFVC support on Windows and demonstrates much
of the functionality available for Team Foundation Version Control.
Above is for Windows machine, if you are working on Mac, please take a look at this answer.
Note:
VS Code will leverage your machine's Git installation, so you need to install Git first before you get these features. Make sure you install at least version 2.0.0.
You need Team Foundation Server 2015 Update 2 or later.
I'm trying to configure Jenkins Team Foundation Server Plugin to our cloud VSTS server .
used Personal access for authenticationtokens gave all scope.
the test in TFS/Team Services show: Success via SOAP API .
but when I start the
build I get : Query returned no result!
I guess this might be related with project path because as i said the test in TFS/Team Services show: Success via SOAP API .
this is how I enter the urls :
Collection URL : https://projectdev.visualstudio.com/
Project path : $/project.Generics/project.Generic
got the project path from VSTS -> Code -> Files
tried adding / DefaultCollection didn't help too
what am I missing?
your help will be appreciated!
Team Foundation Server Plugin can integrate TFS/VSTS source sontrol (Git or TFVC) in jenkins Job, and trigger TFS/VSTS release (not VSTS build).
Details you can find in tfs-plugin README:
This plugin integrates Team Foundation Version Control (also known as
TFVC) and Git to Jenkins by connecting to Team Foundation Server (TFS)
and Visual Studio Team Services (Team Services). It also lets you
trigger a release in Visual Studio Team Services, through a post-build
step in Jenkins.
The "collection URL" looks correct to me.
The "Project path" should be "$/{Project}/{FolderPath}".
In your case, is your project named "project.Generics" and "project.Generic" is a folder in the project?
Currently, we are using TFS 2012 and we have a heavily customized build process as described below.
1. Build the source
2. Run an EXE as console to host WCF services
3. Restore databases on local sql server
4. Run functional test
5. delete databases
6. close the exe started in step 2.
7. Create an Installable exe using WiX ( Wix with custom bootstratpper)
8. Update version number file to TFS
Now we want to move to Visual Studio online from onpremise. Trying to setup a build process with Private Build agent. I have created an VM , installed and registerd agent. I do see agent name back in website.
When I go back to Visual studio and try to create new xaml build definition I am getting below error.
TFS22501: Creating a build definition requires a build controller be defined for this team project collection. There may not be any controllers configured or you may not have permissions to view them. contact your team foundation server administrator.
can somebody please help ?
If you're using XAML build, you have to use the old-style XAML build controller/agent. The VSTS agent is for the new build system.
I would strongly recommend migrating your builds to the new build system as part of your migration to VS Team Services, as the XAML build system is effectively dead.
We have a Team Project we created in 2013. The web site of the project allows Git Repos to be created, but in Visual Studio 2017 the Git repos we created are always Offline and exhibiting other odd behaviors (loading TFVC's interface in Visual Studio even when connecting to a Git repo within it for example). I used Fiddler to check out the traffic and noticed that this particular project is missing the SourceControlGitEnabled = true flag. A project we created a year and a half later DOES include the SourceControlGitEnabled flag and works properly.
Is there a TFS Team Project setting we can alter/enable or do I have to create a new Project with Git as the repo and migrate everything to it?
When you create a new repo in the Team Project in TFS2013, there should be a warning as below:
Note that some versions of Visual Studio will only provide full Team
Explorer integration with a repository that has the same name as the
team project. Users may need to manually clone this new repository to
use it in Visual Studio.
This maybe the limitation of TFS2013 with GIT, either manually clone this new repository to use it in Visual Studio or create a new Project with Git as the repo and migrate everything to it, both should be work.
My system is an on-premises setup for TFS 2015 and I am trying to get Release Management working with my Jenkins continuous integration system. I have recently added the ""Visual Studio Team Services Continuous Deployment" plugin to Jenkins. After finding out that I need to have Basic Authentication enabled on my TFS server to avoid a 401 - Unauthorized: Access is denied due to invalid credentials. error I am getting to the next error: NullPointerException.
I have looked through the code for the vsts-cd-plugin to see that there is an explicit reference to this API call that I don't believe is in TFS 2015 Update 3...
"/_apis/release/releases?api-version=3.0-preview.2"
Has anyone been successful in using the vsts-cd-plugin with Jenkins and an on-premises TFS 2015 setup? Does anyone have a suggestion on how I can fix this problem to create a TFS Release from Jenkins?
The API version 3.0-preview.2 is for Visual Studio Team Services, it is not included in On-premise TFS. In On-premise TFS, you need to use 2.2-preview.1.
api-version = 3.0-preview.1
Using on-premises: An earlier, and slightly different, version of this
Release Management API is available in Team Foundation Server 2015
Update 2. To use, you must specify an API version of 2.2-preview.1.
New release references a release definition to deploy an application
comprising of one/
You can try to download the source code of the plugin and update the API version and then build it on your local machine and install it in Jenkins.