# Is it possible to integrate TFS into Jenkins?

**URL:** https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106
**Category:** Using Jenkins
**Tags:** question, meeting
**Created:** [December 27, 2021, 1:57pm UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106 "2021-12-27T13:57:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![anuj](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@anuj](https://community.jenkins.io/u/anuj)
#### Post date: [December 27, 2021, 1:57pm UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106/1 "2021-12-27T13:57:06Z")

</div>

Is it possible to integrate TFS into Jenkins?

---

<div class="post-metadata">

### Author: ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)
#### Post date: [December 27, 2021, 2:49pm UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106/2 "2021-12-27T14:49:26Z")

</div>

A Jenkins TFS plugin exists, but it was removed from distribution due to a licensing issue. The licensing issue appears to have been resolved but the plugin is not being distributed because it also has multiple unresolved security vulnerabilities.

You can read the licensing history in [[INFRA-2751] Team Foundation Server Plugin uses closed-source dependency - Jenkins Jira](https://issues.jenkins.io/browse/INFRA-2751) .

There are at least two security vulnerabilities:

- Credential ID enumeration - [Jenkins Security Advisory 2021-03-30](https://www.jenkins.io/security/advisory/2021-03-30/#SECURITY-2283%20(1))
- Credential capture - [Jenkins Security Advisory 2021-03-30](https://www.jenkins.io/security/advisory/2021-03-30/#SECURITY-2283%20(2))

No one has yet volunteered to adopt the plugin in order to resolve the security issues and make it again available for use by others. More information on the plugin adoption process is available at

> **[Adopt a Plugin](https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/)**
>
> Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software

---

<div class="post-metadata">

### Author: ![Ian\_W](https://avatars.discourse-cdn.com/v4/letter/i/cab0a1/32.png) [@Ian\_W](https://community.jenkins.io/u/Ian_W)
#### Post date: [December 28, 2021, 2:49am UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106/3 "2021-12-28T02:49:21Z")

</div>

The TFS plugin appears to have been unceremoniously abandoned by Microsoft, and they have not left it in a pretty state. Along with the security issues and [poor documentation](https://issues.jenkins.io/browse/INFRA-2751?focusedCommentId=401194&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-401194) of [the applicable SDK license](https://github.com/microsoft/team-explorer-everywhere/blob/0d7744c5ff77155b9315c1ff87de188b0d6152fc/LICENSE.txt) for the [embedded](https://github.com/jenkinsci/tfs-plugin/tree/master/tfs-sdk/src) and [out of date SDK](https://github.com/microsoft/team-explorer-everywhere/releases/), As the tfs-plugin uses certain SDK libraries which were [removed in 4.135.0](https://github.com/microsoft/team-explorer-everywhere/releases/tag/14.135.0), it’s non-trival to update the plugin to the latest SDK.

They also have not left much of an alternative path, other than installing the CLI (TEE-CLC-\*) from the [SDK release](https://github.com/microsoft/team-explorer-everywhere/releases/) and invoking from an Execute Shell step, which is messy (but gives you the full CLI flexibility) .

Nevertheless, if you are prepared to accept the security risks, it is possible to [install manually](https://www.jenkins.io/doc/book/managing/plugins/#advanced-installation) by downloading from [GitHub release](https://github.com/jenkinsci/tfs-plugin/releases) and installing. Make sure to have installed the [git-plugin](https://plugins.jenkins.io/git/) first (as normal), which should pull in all the dependencies for you.

---

<div class="post-metadata">

### Author: ![Letizia](https://avatars.discourse-cdn.com/v4/letter/l/b3f665/32.png) [@Letizia](https://community.jenkins.io/u/Letizia)
#### Post date: [January 10, 2022, 10:37am UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106/4 "2022-01-10T10:37:58Z")

</div>

I have your same problem, here we use TFS and Jenkins, so in a isolated system I installed this version of TFS plugin:

> **[Release commons-digester2 fix · glevy/tfs-plugin](https://github.com/glevy/tfs-plugin/releases/tag/commons-digester2)**
>
> Full Changelog: https://github.com/glevy/tfs-plugin/commits/commons-digester2

In my docker file I use this:  
RUN jenkins-plugin-cli --verbose -f /usr/share/jenkins/ref/plugins.txt  
COPY mypath/tfs.hpi /usr/share/jenkins/ref/plugins/

and this works with the latest jenkins/jenkins:lts

Hope this help

---

<div class="post-metadata">

### Author: ![tonychen](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tonychen](https://community.jenkins.io/u/tonychen)
#### Post date: [November 13, 2023, 7:51am UTC](https://community.jenkins.io/t/is-it-possible-to-integrate-tfs-into-jenkins/1106/5 "2023-11-13T07:51:45Z")

</div>

thanks Letizia.  
Already solved  
FATAL: hudson/util/Digester2  
java.lang.ClassNotFoundException: hudson.util.Digester2

Thanks.
