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

VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • vstestrunner-plugin
    • None
    • Jenkins LTS 2.73.3 / Jenkins LTS 2.89.3.4
      VSTest plguin 1.0.5

      After installed latest plugin version 1.0.5 the plugin settings under "global tool configuration" and the option to choose it in any job configuration, inside build section, disappear. 

       

      This doesn't occur with version 1.0.4

       

          [JENKINS-47932] VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure

          We have this issue, had to role back to v1.0.4. Any ideas why this has happened?

          Chris Stylianou added a comment - We have this issue, had to role back to v1.0.4. Any ideas why this has happened?

          I can confirm the behaviour. Essentially this is a blocker

          Bernhard Merkle added a comment - I can confirm the behaviour. Essentially this is a blocker

          Renato Chencinski added a comment - - edited

          Also, when job with existing vstext config is saved, the configuration is deleted from the job xml (except, for some strange reason, when the step is inside a conditional step).

          Step option also doesn't show in my environment, which might explain the delete behavior.

          Renato Chencinski added a comment - - edited Also, when job with existing vstext config is saved, the configuration is deleted from the job xml (except, for some strange reason, when the step is inside a conditional step). Step option also doesn't show in my environment, which might explain the delete behavior.

          Matt Sheppard added a comment -

          Any word on this? Every time we run plugin updates inevitably someone forgets that this has been broken for months and ends up breaking all of our pipelines all over again.... we're going to have to migrate from this plugin soon in order to avoid logistical nightmares...

          version 1.0.4 = "All good"

          version 1.0.5 = "headache"

          Exact same symptoms as previous commentors...

          Matt Sheppard added a comment - Any word on this? Every time we run plugin updates inevitably someone forgets that this has been broken for months and ends up breaking all of our pipelines all over again.... we're going to have to migrate from this plugin soon in order to avoid logistical nightmares... version 1.0.4 = "All good" version 1.0.5 = "headache" Exact same symptoms as previous commentors...

          R. Schreurs added a comment -

          Still not solved in 1.0.7.

          R. Schreurs added a comment - Still not solved in 1.0.7.

            Unassigned Unassigned
            cjuroz Cristian Uroz
            Votes:
            10 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: