Details
-
Enhancement
-
Resolution: Done
-
Major
-
3.3.0.GA
-
False
-
None
-
False
-
Release Notes
-
-
Enhancement
-
Done
Description
Synced from Eclipse Che issue
https://github.com/eclipse/che/issues/21184
Is your enhancement related to a problem? Please describe
I’m always frustrated when…Che uses the old version of a devfile.yaml, not the one I have modified a few seconds ago on github.com.
That can be reproduced starting a workspace from a GitHub repository, pushing a devfile.yaml change, deleting the existing workspace and starting a new one with the same exact factory URL and within a 5 minutes time frame.
The problem can also be reproduced test che-server /scm/resolver API using swagger: for 5 minutes, any new request will return the old devfile.yaml or che-editor.yaml, even if you have pushed some changes in the meantime.
Describe the solution you'd like
Che-sever /scm/resolver endpoint should return the updated file, not a cached version.
Release Notes Text
Che ignores changes to devfile.yaml and che-editor.yaml after pushing to a git repository (because che-server URLFetcher sometimes caches its results)
Attachments
Issue Links
- is duplicated by
-
CRW-3634 Che ignores changes to devfile.yaml and che-editor.yaml after pushing to a git repository
- Closed
- links to