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

Allow the directory that plugins are exploded into to be changed

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None

    Description

      For cases where JENKINS_HOME is located on e.g. NFS or a SAN, as the exploded plugin directories are really a redundant copy, it would be beneficial to be able to relocate these outside of JENKINS_HOME (much like the --webroot parameter allows relocating the extracted WAR file directory outside of JENKINS_HOME)

      Most likely the only way to implement this is as either a system property or a CLI parameter as by the time Jenkins has started up it is too late to change the configuration option.

      Additionally there is the use case where the JENKINS_HOME is on a redundant file system in case of disaster recovery, so the target extraction directory may vary depending on which node in the DR is being brought on-line, so it does not make sense to store this in a configuration file (as there is no guarantee that the mount paths are the same, etc)

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          View 9 older comments
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Stephen Connolly
          Path:
          changelog.html
          war/pom.xml
          http://jenkins-ci.org/commit/jenkins/20317bb1e409d30626abf43f88bee07aa29524f3
          Log:
          JENKINS-32765 Update extras-executable-war to pick up system property and record feature in changelog

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/20317bb1e409d30626abf43f88bee07aa29524f3 Log: JENKINS-32765 Update extras-executable-war to pick up system property and record feature in changelog
          stephenconnolly Stephen Connolly added a comment -

          Fixed towards 1.648

          stephenconnolly Stephen Connolly added a comment - Fixed towards 1.648
          dogfood dogfood added a comment -

          Integrated in jenkins_main_trunk #4449
          JENKINS-32765 Update extras-executable-war to pick up system property (Revision 20317bb1e409d30626abf43f88bee07aa29524f3)

          Result = SUCCESS
          stephen connolly : 20317bb1e409d30626abf43f88bee07aa29524f3
          Files :

          • war/pom.xml
          • changelog.html
          dogfood dogfood added a comment - Integrated in jenkins_main_trunk #4449 JENKINS-32765 Update extras-executable-war to pick up system property (Revision 20317bb1e409d30626abf43f88bee07aa29524f3) Result = SUCCESS stephen connolly : 20317bb1e409d30626abf43f88bee07aa29524f3 Files : war/pom.xml changelog.html
          olenz Olaf Lenz added a comment -

          Wouldn't it make more sense to introduce a single parameter "--cacheroot" (or something like that) where the webroot, the pluginroot and also the jar cache could be put (see JENKINS-18578), instead of providing an extra parameter for all of these?

          olenz Olaf Lenz added a comment - Wouldn't it make more sense to introduce a single parameter "--cacheroot" (or something like that) where the webroot, the pluginroot and also the jar cache could be put (see JENKINS-18578 ), instead of providing an extra parameter for all of these?
          stephenconnolly Stephen Connolly added a comment -

          That wouldn't work for people running in Bring-Your-Own-Servlet-Container mode, those people need a separate configurable option as the webapp expansion is controlled by e.g. Tomcat.

          Additionally, when testing multiple versions of Jenkins it can be helpful to use different -webroot options with the same -pluginroot (assuming you have done the correct pinning)

          stephenconnolly Stephen Connolly added a comment - That wouldn't work for people running in Bring-Your-Own-Servlet-Container mode, those people need a separate configurable option as the webapp expansion is controlled by e.g. Tomcat. Additionally, when testing multiple versions of Jenkins it can be helpful to use different - webroot options with the same -pluginroot (assuming you have done the correct pinning)

          People

            stephenconnolly Stephen Connolly
            stephenconnolly Stephen Connolly
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: