• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: plugin-compat-tester
• Labels:

  None

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

Oleg Nenashev created issue - 2017-12-27 15:10

Oleg Nenashev made changes - 2017-12-27 15:10

Assignee

Original: Frédéric Camblor [ fcamblor ]

New: Oleg Nenashev [ oleg_nenashev ]

Oleg Nenashev made changes - 2017-12-27 15:11

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 - 2017-12-27 15:11

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Oleg Nenashev made changes - 2017-12-27 15:23

Remote Link

New: This issue links to "https://github.com/jenkinsci/plugin-compat-tester/pull/55 (Web Link)" [ 19601 ]

Oleg Nenashev made changes - 2017-12-27 15:23

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Oleg Nenashev made changes - 2017-12-28 14:25

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 - 2017-12-28 16:57

Epic Link

New: JENKINS-48734 [ 187440 ]

Oleg Nenashev made changes - 2018-01-14 09:21

Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Resolved [ 5 ]