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

Avoid browser cache busting after Jenkins restart

    XMLWordPrintable

Details

    • atlantic, tasman

    Description

      Atm, the browser caches JS resources via normal cache control and expiry headers. However, the resources are all bundled as adjuncts and adjunct urls have a hash that gets changed after restart, which means all resources need to be reloaded after restart.

      See can we come up with a way of loading the resources from URLs that do not change after a restart.

      jamesdumay has already done some experimenting with a replacement ResourceManager. See PR-587.

      Other possibilities ...

      • Look at the use of AssetManager in Jenkins core
      • Look at bundling resources in the plugins under the webapp dir (no hash in these URLs).

      Note that this will most probably require changes to js-builder and js-modules so that we can "plug in" different resource resolution algos e.g. one specific to Blue Ocean and whatever we do above.

      Attachments

        Issue Links

          Activity

            jamesdumay James Dumay added a comment -

            tfennelly LMK when this should go in the sprint (or not)

            jamesdumay James Dumay added a comment - tfennelly LMK when this should go in the sprint (or not)
            jamesdumay James Dumay added a comment -

            We should have a mini-design doc here and have members of the team collaborate on it

            jamesdumay James Dumay added a comment - We should have a mini-design doc here and have members of the team collaborate on it
            tfennelly Tom FENNELLY added a comment -

            jamesdumay yeah, I think we need to be doing mini-design docs for all work. I think we agreed that would be in a google doc that's linked to on the JIRA and, most importantly, circulated to the dev mailing list (the new one).

            tfennelly Tom FENNELLY added a comment - jamesdumay yeah, I think we need to be doing mini-design docs for all work. I think we agreed that would be in a google doc that's linked to on the JIRA and, most importantly, circulated to the dev mailing list ( the new one ).

            People

              tfennelly Tom FENNELLY
              tfennelly Tom FENNELLY
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: