Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: core
-
Labels:None
-
Similar Issues:
Description
The war-for-test artifact is used so that functional tests in plugins can have jenkins.war of the selected version in their classpath, thus letting the WAR exploder do its work. Yet this means that the space consumption in the Maven repository for each release is considerably larger than it really should be, since we store the 65Mb WAR twice!
Should explore whether there is some other means of locating jenkins.war that does not involve making a full copy. Can we store a placeholder JAR and have WarExploder look up jenkins.war using a relative path in the local repository? (And is there some way to force the WAR to be downloaded by the time the rest runs?) Or can the handler for the primary WAR artifact be customized to mark it as being valid to include in classpaths?
Attachments
Issue Links
- relates to
-
JENKINS-45245 Cannot run tests in IntelliJ IDEA with plugin parent POM 2.30
-
- Resolved
-
-
INFRA-1342 Deploy war-for-test artifacts for cores 2.64 through 2.79
-
- Closed
-
- links to
Code changed in jenkins
User: Victor Martinez
Path:
docs/Testing-DSL-Scripts.md
http://jenkins-ci.org/commit/job-dsl-plugin/ca99792f54e2f3a754e70a9a69e3c5f36c885db3
Log:
JENKINS-24064war-for-test classifier is not supported from 2.64+JENKINS-24064(https://issues.jenkins-ci.org/browse/JENKINS-24064)Bumped jenkins-test-harness and also removed the war-for-test classifier as required since version 2.64 onwards
Further details: