Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30479

TFS plugin did not support version 2005

XMLWordPrintable

      Since version 4.0.0 is the TFS plugin not supporting TFS Server 2005 (and probably TFS Server 2008) anymore. It would be nice to say the drop of support in changelog on website
      https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin

      Also would it be good, to have support for it in the current plugin, to get improvments.
      This could be done by separate the logics into new and old TFS implementation.

          [JENKINS-30479] TFS plugin did not support version 2005

          Manfred Moser added a comment -

          This is a version of TFS that is over 10 years old. You should upgrade your TFS server and not ask an open source plugin to support such an old system. I suggest to close the issue.

          Manfred Moser added a comment - This is a version of TFS that is over 10 years old. You should upgrade your TFS server and not ask an open source plugin to support such an old system. I suggest to close the issue.

          Ronny Borchert added a comment - - edited

          The support would be simple by using the old code as fallback strategy.
          I reported this only, be sure the author is knowing which impact the change in 4.0.0 has.

          Ronny Borchert added a comment - - edited The support would be simple by using the old code as fallback strategy. I reported this only, be sure the author is knowing which impact the change in 4.0.0 has.

          Manfred Moser added a comment -

          It was a known issue and a conscious decision to move the TFS SDK and removal of the command line calls. Adding the old code back in would add all the old problems including the need for a TFS client install on the nodes. If you really need this.. stick with the old version of the plugin.

          Manfred Moser added a comment - It was a known issue and a conscious decision to move the TFS SDK and removal of the command line calls. Adding the old code back in would add all the old problems including the need for a TFS client install on the nodes. If you really need this.. stick with the old version of the plugin.

          Ronny Borchert added a comment -

          I would say if the TFS client install is missing you get an error, so I see not why.
          Which problems are solved by moving from tf.exe to TFS SDK?

          Ronny Borchert added a comment - I would say if the TFS client install is missing you get an error, so I see not why. Which problems are solved by moving from tf.exe to TFS SDK?

          Manfred Moser added a comment -

          Provisioning is simplified. The codebase got a large cleanup and so on. It would be a LOT of work to add it back in. I doubt anybody would do that work.

          Manfred Moser added a comment - Provisioning is simplified. The codebase got a large cleanup and so on. It would be a LOT of work to add it back in. I doubt anybody would do that work.

          Manfred Moser added a comment -

          These old versions are not even mainstream supported by Microsoft. And our readme page explicitly references only newer versions. See https://github.com/jenkinsci/tfs-plugin

          Manfred Moser added a comment - These old versions are not even mainstream supported by Microsoft. And our readme page explicitly references only newer versions. See https://github.com/jenkinsci/tfs-plugin

          Ronny Borchert added a comment -

          Ok, then do please change the readme.md file that TFS 2005 Server is not working!

          Ronny Borchert added a comment - Ok, then do please change the readme.md file that TFS 2005 Server is not working!

          Olivier Dagenais added a comment -

          Do you have any suggestions to improve the current wording in the README.md?

          The following versions of TFS are no longer supported and may only partially work with the plugin:

          ...or maybe the text/headings around that table? For example, would a "compatibility matrix" with green checkmarks and red Xs for supported and unsupported (respectively) versions be better?

          Also, I implemented your suggestion and amended the release notes for version 4.0.0 to contain:

          This change marks the drop of support for older versions of TFS (2005, 2008 and 2010)

          Olivier Dagenais added a comment - Do you have any suggestions to improve the current wording in the README.md ? The following versions of TFS are no longer supported and may only partially work with the plugin: ...or maybe the text/headings around that table? For example, would a "compatibility matrix" with green checkmarks and red Xs for supported and unsupported (respectively) versions be better? Also, I implemented your suggestion and amended the release notes for version 4.0.0 to contain: This change marks the drop of support for older versions of TFS (2005, 2008 and 2010)

          Ronny Borchert added a comment -

          A "compatibility matrix" would be fine. Because the "partial work" term in above the table is total confusing.

          Ronny Borchert added a comment - A "compatibility matrix" would be fine. Because the "partial work" term in above the table is total confusing.

          Olivier Dagenais added a comment -

          I have updated the README.md at commit 03e4a65fbd29d1dd06c3929ab33388d2a8238e0d to put all versions in a single table.

          Olivier Dagenais added a comment - I have updated the README.md at commit 03e4a65fbd29d1dd06c3929ab33388d2a8238e0d to put all versions in a single table.

            oli_at_jsi Olivier Dagenais
            arbeita Ronny Borchert
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: