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

PCT should support PCT for plugins with custom WAR

XMLWordPrintable

      PCT run for plugins requires plugin metadata. When "-war" is defined, this metadata will be downloaded from the WAR file... but

      • it will list only bundled plugins without ones in "-includePlugins"
      • In Jenkins 2.0+ the list is empty. In such case PCT skips all plugins and then fails with error while trying to read non-existent XML report file

          [JENKINS-48724] PCT should support PCT for plugins with custom WAR

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Assignee Original: Frédéric Camblor [ fcamblor ] New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Summary Original: PCT for a custom source with -war fails when Jenkins Core is newer than 2.0 New: PCT should support PCT for plugins with custom WAR
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Oleg Nenashev added a comment -

          https://github.com/jenkinsci/plugin-compat-tester/pull/55

          Oleg Nenashev added a comment - https://github.com/jenkinsci/plugin-compat-tester/pull/55
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/plugin-compat-tester/pull/55 (Web Link)" [ 19601 ]
          Oleg Nenashev made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Oleg Nenashev made changes -
          Description Original: PCT run for plugins requires plugin metadata. When "-war" is defined, this metadata will be downloaded from the WAR file... but
          * it will list only bundled plugins without ones in "-includePlugins"
          * In Jenkins 2.0+ the list is empty
          		 New: PCT run for plugins requires plugin metadata. When "-war" is defined, this metadata will be downloaded from the WAR file... but
          * it will list only bundled plugins without ones in "-includePlugins"
          * In Jenkins 2.0+ the list is empty. In such case PCT skips all plugins and then fails with error while trying to read non-existent XML report file
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-48734 [ 187440 ]

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          plugins-compat-tester-cli/src/main/java/org/jenkins/tools/test/PluginCompatTesterCli.java
          plugins-compat-tester/src/main/java/org/jenkins/tools/test/PluginCompatTester.java
          http://jenkins-ci.org/commit/plugin-compat-tester/0ea20aa895050be14627ed97fb7a07a24bb2935e
          Log:
          Merge pull request #55 from oleg-nenashev/feature/JENKINS-48724

          JENKINS-48724 - PCT should allow running PCT for a plugin with custom WAR.

          Compare: https://github.com/jenkinsci/plugin-compat-tester/compare/73cff3444253...0ea20aa89505

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: plugins-compat-tester-cli/src/main/java/org/jenkins/tools/test/PluginCompatTesterCli.java plugins-compat-tester/src/main/java/org/jenkins/tools/test/PluginCompatTester.java http://jenkins-ci.org/commit/plugin-compat-tester/0ea20aa895050be14627ed97fb7a07a24bb2935e Log: Merge pull request #55 from oleg-nenashev/feature/ JENKINS-48724 JENKINS-48724 - PCT should allow running PCT for a plugin with custom WAR. Compare: https://github.com/jenkinsci/plugin-compat-tester/compare/73cff3444253...0ea20aa89505

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: