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

war-for-test makes for excessively large artifacts of Jenkins core


    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None

      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?

            jglick Jesse Glick
            jglick Jesse Glick
            0 Vote for this issue
            3 Start watching this issue