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

Pipeline script from SCM not working for TFS

    XMLWordPrintable

Details

    Description

      When I create a new pipeline job and then select "Pipeline script from SCM" definition followed by "Team Foundation Version control (TFVC)" SCM along with appropriate url, path and credentials then save.

      I then return to the configuration for this project and find that the SCM selected is "git" along with empty fields related to git. There are now only two options in the SCM dd: git and Subversion

      I expect to find my previously entered TFS settings.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          rschiefer Robb Schiefer added a comment -

          I'm also having this issue using Jenkins 2.32.2 running inside a docker container.

          rschiefer Robb Schiefer added a comment - I'm also having this issue using Jenkins 2.32.2 running inside a docker container.
          uriparush uri parush added a comment -

          l also have the same problem.

          Is this issue going to be resolve in the near future?

           

           

          uriparush uri parush added a comment - l also have the same problem. Is this issue going to be resolve in the near future?    
          jlarfors Jacob Lärfors added a comment -

          Same for me. Everything up to date.

          Does anyone maintain this plugin still?

          jlarfors Jacob Lärfors added a comment - Same for me. Everything up to date. Does anyone maintain this plugin still?
          ashish_kataria Ashish Kataria added a comment -

          Same issue for me. I am unable to poll my TFS due to this after I migrated my project to a Pipeline. Kindly advise.

          ashish_kataria Ashish Kataria added a comment - Same issue for me. I am unable to poll my TFS due to this after I migrated my project to a Pipeline. Kindly advise.
          ashish_kataria Ashish Kataria added a comment -

          As per the description of JENKINS-42216, TFVC does not override isApplicable(Job), and thus is incorrectly being shown in the dropdown in the first place.

          I guess the world should simply migrate to GIT(easier said than done!).

          ashish_kataria Ashish Kataria added a comment - As per the description of JENKINS-42216 , TFVC does not override isApplicable(Job), and thus is incorrectly being shown in the dropdown in the first place. I guess the world should simply migrate to GIT(easier said than done!).
          it12lsp Christian Häussler added a comment -

          Is this issue going to be resolve in the near future?

          it12lsp Christian Häussler added a comment - Is this issue going to be resolve in the near future?
          kelliejos Kellie Jos added a comment -

          Hi, thank you for using the tfs plugin! Support for Jenkins pipelines was introduced with the 5.126.0 release of the tfs plugin. Please try updating your plugin version to resolve this issue. Thanks!

          kelliejos Kellie Jos added a comment - Hi, thank you for using the tfs plugin! Support for Jenkins pipelines was introduced with the 5.126.0 release of the tfs plugin. Please try updating your plugin version to resolve this issue. Thanks!

          People

            Unassigned Unassigned
            kevpluck Kevin Pluck
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: