• Icon: Task Task
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • tfs-plugin
    • None
    • PROD and uat

       

      Hi,

      All of sudden we are not seeing any of our Jenkins jobs to be configured with source code management with the TFS repositories that have been configured earlier.

       

      Upon investigating it looks like the TFVS plugin doesnt even exist to be installed on our machine.

       

      Can someone please help us out as this is impacting us from deploying things to both PROD and non-prod environments.

          [JENKINS-64807] TFVC plugin isnt even showing up to install

          Ian Williams added a comment -

          Is the plugin actually in the plugins directory on the FileSystem ( `$JENKINS_HOME}/plugins` ) ? Does it show as installed on your instance in the plugin Manager ( `${JENKINS_URL}/pluginManager/installed` )?
          Did you reinstall or change the instance configuration ?

          Not that this should have any impact on your local instance, but TFS plugin was removed from the plugins repository last year as it does not meet the OSI open source license requirements - INFRA-2751 to be made available via the plugins site.

          It also has a security vulnerability (SECURITY-1506 / CVE-2020-2249 ), which lead to the identification of the license violation.

          No one has heard a peep from MS in several years regarding the plugin and it's been even longer since redsolo stopped working on the plugin. This position would appear to be supported by their advisory for the Azure Repos VS Code extension.

          See also S/O responses here and here

          The plugin is still available to download from GitHub and manually install from the Web UI.

           

          ps: I have noting to do w/plugin other than a fellow frustrated user.

          Ian Williams added a comment - Is the plugin actually in the plugins directory on the FileSystem ( `$JENKINS_HOME}/plugins` ) ? Does it show as installed on your instance in the plugin Manager ( `${JENKINS_URL}/pluginManager/installed` )? Did you reinstall or change the instance configuration ? Not that this should have any impact on your local instance, but TFS plugin was removed from the plugins repository last year as it does not meet the OSI open source license requirements - INFRA-2751 to be made available via the plugins site. It also has a security vulnerability ( SECURITY-1506 / CVE-2020-2249 ), which lead to the identification of the license violation. No one has heard a peep from MS in several years regarding the plugin and it's been even longer since redsolo stopped working on the plugin. This position would appear to be supported by their advisory for the Azure Repos VS Code extension . See also S/O responses here and here The plugin is still available to download from GitHub and manually install from the Web UI .   ps: I have noting to do w/plugin other than a fellow frustrated user.

          Mark Waite added a comment -

          Closed as a duplicate of INFRA-2751. The TFS plugin appears to use components that are closed source. The Jenkins infrastructure has a policy to only host open source plugins.

          It looks like someone could bring the TFS plugin back if they were willing to:

          • Adopt the TFS plugin
          • Adjust to use a published open source version of the library
          • Resolve the two open security issues

          Mark Waite added a comment - Closed as a duplicate of INFRA-2751. The TFS plugin appears to use components that are closed source. The Jenkins infrastructure has a policy to only host open source plugins. It looks like someone could bring the TFS plugin back if they were willing to: Adopt the TFS plugin Adjust to use a published open source version of the library Resolve the two open security issues

          Daniel Beck added a comment -

          markewaite Not really, unless an instance is regularly reinstalled from scratch, existing setups should not be impacted.

          Daniel Beck added a comment - markewaite Not really, unless an instance is regularly reinstalled from scratch, existing setups should not be impacted.

          Ian Williams added a comment -

          markewaite, danielbeck, "an instance is regularly reinstalled from scratch" is in fact a regular occurrence in our operational process.

          Ian Williams added a comment - markewaite , danielbeck , "an instance is regularly reinstalled from scratch" is in fact a regular occurrence in our operational process.

          Daniel Beck added a comment -

          ianw I'm not saying it doesn't happen, but you're also unlikely to not mention error messages during download or similar, which isn't the case here.

          Daniel Beck added a comment - ianw I'm not saying it doesn't happen, but you're also unlikely to not mention error messages during download or similar, which isn't the case here.

            redsolo redsolo
            harikakodali harika
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: