When I click on 'browse market place' for our production TFS server, it directly links to our VSTS account. If I then try to install the Sonarqube extension I only have the option to get it.
I can install it directly for VSTS or download it for our on-premise environment.
(it behaves the same way for other extensions as well)
The strange this is that on our test on-premise environemnt I still do have the option to directly install it.
2 questions:
1) What can I reconfigure on our production env to get a connection to it in the marketplace.
2) How do I get the downloaded file into our on-premise environment?
Update:
You could still be able to install the extension to TFS. Simply Click get it free option, there should be an option download at the bottom of the pop-up dialog.
You could then upload the locally extension to TFS server follow this tutorial, finally install to your team project collection.
If you are running on TFS earlier than 2017 Update 2, you will need to download and manually install the latest 3.x version of the VSIX.
You can download the VSIX on the "Releases" page of the GitHub repository
Versions 4.x are compatible with:
TFS 2017 Update 2+
TFS 2018
VSTS
You could directly get it from server through url, and it will show as Get it free.
More details please take a look at this tutorial: Analyzing with SonarQube Extension for VSTS/TFS
Beside suggest you could also go through below tutorialshow to get/install extension from TFS/VSTS:
Install extensions for Team Foundation Server (TFS)
Install free extensions for VSTS
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 have installed Team Foundation Server 2018 Update 1 and I want to install and configure automated generated builds for the team.
In Team Foundation Management Console, there is an entry "Build and release" but there a only informations and links that are not clickable.
If I click a link, another windows opens, but the ok button stays disabled, so I do not get additional information:
In earlier releases of TFS I could install and configure the tfs build system on this place.
How I can do now in tfs2018. Do I have to install additional software and where I can download.
For one reason, we are using Visual Studio 2015 (we want upgrade later to 2017).
Go to the TFS Web interface, in the settings panel find the Agent Pool and hit the "Download Agent" link.
TFS 2018 is the first TFS version that no longer supports the XAML agent infrastructure.
You need to deploy an agent first as jessehouwing mentiond above, you can also refer to this link for detials : Deploy an agent on Windows
Then create a build definition and Enable continuous integration (CI) to automate builds. Refer to this link for details： https://learn.microsoft.com/en-us/vsts/build-release/actions/ci-cd-part-1
Below articles may also helps for you:
Build and Release in VSTS and TFS
Build and release tasks
Build and release quickstarts
Thanks for the answers. No I have found the page, where I can download the build-agent.
For TFS2018 you can download the build agent by using the following url:
https://{your_server}/DefaultCollection/_admin/_AgentPool
Like provided from Microsoft you can find it for other TFS versions:
VSTS: https://{your_account}.visualstudio.com/_admin/_AgentPool
TFS 2017: https://{your_server}/tfs/DefaultCollection/_admin/_AgentPool
TFS 2015: http://{your_server}:8080/tfs/_admin/_AgentPool
What is the process for upgrading the default tasks loaded by Microsoft in an on-premises TFS with no internet connectivity?
According to https://learn.microsoft.com/en-us/vsts/build-release/tasks/ there are several tasks now available and supported in TFS v2015-2018/VSTS that do not appear in my TFS 2017u2 installation (specifically the Download Secure File task).
The default tasks are not shown in the Manage Extension screens and the git repo (https://github.com/Microsoft/vsts-tasks) does not appear to have any instructions for how to package and install the latest versions in an existing TFS.
Download Secure File this task is not support by TFS2017 update2 for now.
In the right of the task, there is a column called Versions which stands for the supported TFS version and VSTS for now.
I use TFS on-premises and I don't see some of these features. Why not?
Some of these features are available only on VSTS and not yet
available on-premises. Some features are available on-premises if
you have upgraded to the latest version of TFS.
Source Link
The task you need is only available/build-in with VSTS by now.
However, this task is open sourced, you could find it here. You could also build it and package it as normal extension. Take a look at below steps for your reference:
Globally install typescript and tfx-cli (to package VSTS
extensions): npm install -g typescript tfx-cli
From the suitable of the repo run npm install. This will pull down
the necessary modules for the tasks and for the build tools.
Run npm run build to compile the build tasks or build a specific
task (recommended): node make.js build --task ShellScript
Run npm run package -- --version <version> to create the .vsix
extension packages (supports multiple environments) that includes
the build tasks.
With the .vsix files, you are easy to directly upload the extension. Details about this area, you could refer here:
How do you install extension vsix files to TFS 2015 (Update 3)?
How do I use the tfs-cli (tfx) to update a TFS extension for an on-premise TFS instance?
Besides, even you have published the extension to your TFS successfully, this task may not compatible with your present version, just Giulio said, you could create a test first. Certainly, you could also create your own extension as your demands.
Look at the Contribute page: it is a bit cryptic if you are not familiar with Javascript tooling.
CAVEAT: there is no guarantee that an update Task works with your TFS version and rolling back a change is a non-trivial task. Use, at least, a separate Collection to test changes.
We started to use Team service on visualstudio.com for our versioning control.
As I don't intend to install vs2015 on the server, how can I download the latest version on the server from the Team service?
compiling and publishing on the server is easy
When you install the VSTS Build & Release Agent from VSTS it will include tf.exe, which is all that's needed to map and download sources from the commandline. An alternative to installing the agent is to install Team Explorer (stand-alone download would be 2013) or download the Cross Platform TFS Commandline tools.
You can also download the TFS Client Object Model through Nuget and call it directly from PowerShell.
As far as I can tell there is no stand-alone download of the TFS/VSTS commandline tool (tf.exe).
I've installed the prerequisite (Team Explorer 2013) to the best of my knowledge, but when I try to set up a VCS root to connect to our TFS Version Control server, I continue to get this error message:
"No TFS assemblies were found on the system. Please make sure you have
Microsoft Team Explorer installed. Supported versions: 2015 2013 2012
2010 2008 2005"
The Team Explorer I downloaded from Microsoft just seemed to be a plugin for Visual Studio, which doesn't make much sense as a server-side component. Anyway, I configured a connection to our TFS box within Team Explorer/Visual Studio on my TeamCity server.
So I have two questions that seem to be undocumented by JetBrains:
What does it mean to set up and configure Team Explorer? How can I validate that I have set up and configured Team Explorer on my TeamCity server correctly?
How does TeamCity know how to find the Team Explorer assemblies? Is there some sort of configuration I am supposed to do? Where is this documented?
I guess I'm looking for a true step-by-step set of instructions that make no assumptions about my understanding of TFS or Team Explorer, or any assumptions about what I may have already installed on my TeamCity box.
I've read the two articles on the JetBrains site regarding how to set this up, and they don't cover actually installing and configuring the prerequisites or configuring TeamCity to discover the Team Explorer assemblies it needs.
Team Explorer is the client software that you use to access Visual Studio Team Foundation Server functionality from Visual Studio. You can simply launch Team Explorer on your TeamCity server to create a team project and check in a project, to validate whether it is installed correctly.
I couldn't find any documentation that mentioned how does TeamCity find Team Explorer assemblies. But, based on my understanding, there is no configuration needed to detect Team Explorer. Please make sure your TeamCity server is running under Windows.
If the issue that can't find Team Explorer persists, you can install VS Premium instead of Team Explorer.
Setting up Jetbrains TeamCity for CI with Team Foundation Server:
Install Jetbrains TeamCity
If you are planning on using IIS or TFS on the same server, configure Jetbrains TeamCity to run on a port other than 80 or 8080
Once TeamCity is up and running, you can begin configuring your TeamCity installation for CI Builds.
Log into TeamCity with your user name and password
Create a new TeamCity Project
Create a new build configuration
You will now see a series of build configuration settings that you will have to complete presented in a Wizard-style navigation view.
Enter General Settings
Enter VCS Settings
After entering VCS Settings, Create and attach new VCS Root
Enter the relevant information for your TFS instance
Create a Build Step using Visual Studio as your build runner. You can create as many build steps as you need and specify the order of the steps (similar to a TFS Build Workflow).
For setting up Continuous Integration builds, you will need to specify a Build Trigger. CI Builds will generally use a VCS Trigger that is triggered on each source control check-in.
If you need to pass any parameters to your build, you can configure these in your Build Parameters.
That is all! You can then either run your Builds manually by clicking on the Run button in TeamCity or simply verify that your builds are triggered by the next check-in into TFS.