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

windows managed batch looses arguments when used within testlink

      "Execute managed windows batch" within "Test Execution" within Testlink looses the defined arguments (both in "single build steps" and as well in "iterative test build steps").

      The used windows batch file defines one argument, which is shown as "required arguments".
      Clicking on "Define arguments" I can input an argument.
      Clicking on "Save", then again on "Configure", to have a look on my Jenkins Job, this argument is lost.

      Doing the same outside of Testlink, "Execute manage windows batch" works as it should, the arguments are kept.

      I attach a printout with a very simple example, which I only used for testing purposes.

      testlink plugin version: 3.1.8

          [JENKINS-16294] windows managed batch looses arguments when used within testlink

          Angela Bauer created issue -
          Angela Bauer made changes -
          Description Original: "Execute managed windows batch" within "Test Execution" within Testlink looses the defined arguments (both in "single build steps" and as well in "iterative test build steps".

          The used windows batch file defines one argument, which is shown as "required arguments".
          Clicking on "Define arguments" I can input an argument.
          Clicking on "Save", then again on "Configure", to have a look on my Jenkins Job, this argument is lost.

          Doing the same outside of Testlink, "Execute manage windows batch" works as it should, the arguments are kept.

          I attach a printout with a very simple example, which I only used for testing purposes.
          New: "Execute managed windows batch" within "Test Execution" within Testlink looses the defined arguments (both in "single build steps" and as well in "iterative test build steps").

          The used windows batch file defines one argument, which is shown as "required arguments".
          Clicking on "Define arguments" I can input an argument.
          Clicking on "Save", then again on "Configure", to have a look on my Jenkins Job, this argument is lost.

          Doing the same outside of Testlink, "Execute manage windows batch" works as it should, the arguments are kept.

          I attach a printout with a very simple example, which I only used for testing purposes.

          testlink plugin version: 3.1.8
          Oleg Nenashev made changes -
          Component/s New: testlink [ 15754 ]
          Component/s Original: plugin [ 15491 ]
          Oleg Nenashev made changes -
          Assignee New: Bruno P. Kinoshita [ kinow ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147108 ] New: JNJira + In-Review [ 176813 ]

            kinow Bruno P. Kinoshita
            baue_ang Angela Bauer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: