Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: jenkins-test-harness
-
Labels:None
-
Similar Issues:
Description
Specifically seems to be maven-hpi-plugin 2.0 that's causing this, with the JENKINS-24064 fix. Now we get an error like
java.lang.AssertionError: jenkins.war is not in the classpath. If you are running this from the core workspace, run 'mvn install' to create the war image in war/target/jenkins
whenever trying to run tests. Jesse Glick says this is due to Intellij not honoring https://github.com/jenkinsci/maven-hpi-plugin/blob/137e435d0770f78edbbd2ed54d91809b7e7be5aa/src/main/resources/META-INF/plexus/components.xml#L134, so we need to figure out how to, like, get it to honor that.
Attachments
Issue Links
- relates to
-
JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core
-
- Resolved
-
-
INFRA-1342 Deploy war-for-test artifacts for cores 2.64 through 2.79
-
- Closed
-
- links to
(4 links to)
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Component/s | jenkins-test-harness [ 21462 ] | |
Component/s | core [ 15593 ] |
Remote Link | This issue links to "jenkins-test-harness PR 65 (Web Link)" [ 17194 ] |
Summary | Cannot run tests in Intellij with plugin parent POM 2.31+ | Cannot run tests in IntelliJ IDEA with plugin parent POM 2.30 |
Assignee | Kohsuke Kawaguchi [ ci_jenkinsci_org ] |
Assignee | Kohsuke Kawaguchi [ ci_jenkinsci_org ] | Kohsuke Kawaguchi [ kohsuke ] |
Assignee | Kohsuke Kawaguchi [ kohsuke ] |
Resolution | Not A Defect [ 7 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Not A Defect [ 7 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Priority | Minor [ 4 ] | Critical [ 2 ] |
Attachment | Screen Shot 2017-09-15 at 17.41.01.png [ 39728 ] |
Attachment | sad panda2.png [ 39729 ] |
Remote Link | This issue links to "jenkins.git PR #3029 (Web Link)" [ 17736 ] |
Remote Link | This issue links to "plugin-pom PR #75 (Web Link)" [ 17737 ] |
Remote Link | This issue links to "maven-hpi PR #77 (Web Link)" [ 17738 ] |
Remote Link | This issue links to "jenkins-test-harness PR #72 (Web Link)" [ 17739 ] |
Assignee | Andrew Bayer [ abayer ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Link |
This issue relates to |
Remote Link | This issue links to "jenkins-test-harness PR 73 (Web Link)" [ 17740 ] |
Assignee | Andrew Bayer [ abayer ] | Jesse Glick [ jglick ] |
Remote Link | This issue links to "plugin-pom PR 76 (Web Link)" [ 17744 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Moving it to jenkins-test-harness since that is the immediate source of the error, though the changed behavior is actually in maven-hpi-plugin + plugin-pom and the fix probably needs to be in https://github.com/stapler/idea-stapler-plugin for which we have no apparent bug tracker.