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

Make the plugin generic and language neutral

XMLWordPrintable

    • 453.va_f398e86a_9ec

      We would like to use this plugin for VHDL testing.
      Unfortunately, several aspects of the plugin makes it java-specific.

      I suggest the plugin is modified so that it becomes more generic and useful for all kinds of tests regardless of language.

      These changes must be made:
      1: The plugin currently parallelises on the "testclass" granularity. In systems other than java there is no "testclass" concept. Just a bunch of "testcases". The plugin assumes all testcases belong to the same class, and is unable to parallelise any tests. The plugin should be changed to parallelise on the "testcase" granularity.
      For backwards compatibility, the plugin could autodetect if any testclasses exists.

      2: The plugin appends ".java" and ".class" to each testname in the exclusionfile. The testnames should be unmodified.

      3: The plugin replaces all "." with "/" in the testnames. The testnames should be unmodified.

          [JENKINS-28924] Make the plugin generic and language neutral

          Olof Kraigher added a comment -

          I require the same feature. Many non-Java test frameworks integrate with Jenkins using junit xml using just the "name" rather than the "classname" atttibutes of the testcase tag. It would be a shame to need to have a different Jenkins plugin to parallelize them. Maybe you could have a "raw" mode clean of java assumptions where the java specialization was a specific optional layer on top?

          Olof Kraigher added a comment - I require the same feature. Many non-Java test frameworks integrate with Jenkins using junit xml using just the "name" rather than the "classname" atttibutes of the testcase tag. It would be a shame to need to have a different Jenkins plugin to parallelize them. Maybe you could have a "raw" mode clean of java assumptions where the java specialization was a specific optional layer on top?

          Linus Geson added a comment -

          For those of you interested in this feature the pull request has been updated/overwritten with new implementation. You can now chose the plugin to either output just the testCaseName or className.testCaseName in the exclusion/inclusion files. Support for workflow plugin was also added.

          Linus Geson added a comment - For those of you interested in this feature the pull request has been updated/overwritten with new implementation. You can now chose the plugin to either output just the testCaseName or className.testCaseName in the exclusion/inclusion files. Support for workflow plugin was also added.

            vlatombe Vincent Latombe
            tib Timmy Brolin
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: