Closed Bug 1067961 Opened 10 years ago Closed 10 years ago

The UI assets are cached for too long - cache has to be cleared after production pushes

Categories

(Tree Management :: Treeherder, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: camd)

References

Details

Even the next day after a treeherder-ui production push, I still have to clear my cache in order to see changes on production.

Telling all uses of treeherder to clear their caches doesn't scale - this is a blocker since it prevents any followup fixes from working, given that it's likely people are already visiting treeherder from try links, so have the assets cached.

Ryan (or Wes?) reported seeing caching for several days after a prod push last week too.
Summary: The UI assets are cached for too long - force clearing of cache required long after production pushes → The UI assets are cached for too long - cache has to be cleared after production pushes
Assignee: nobody → cdawson
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/treeherder-ui

https://github.com/mozilla/treeherder-ui/commit/0e81024fa683ec14b25d1282f922c135bff07888
bug 1067961 - add versioning to css and js assets

https://github.com/mozilla/treeherder-ui/commit/6c8349119d9fd0007c6104d0b01ac11de0b8c758
Merge pull request #193 from mozilla/css-js-versioning

bug 1067961 - add versioning to css and js assets
second part of caching fix complete:
https://github.com/mozilla/treeherder-ui/pull/196

https://github.com/mozilla/treeherder-ui/commit/ad1df9ff7db7fbb3fb2f74c69dedb02100bcc4c3
https://github.com/mozilla/treeherder-ui/commit/b46a3f2233f9711e9e42a56e7c1a8069e23c4aa4

this is going out to master today.  you MAY have to force refresh one last time if the changes prior to this are still cached.  from then on, you won't.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.