UAAS-454 - Automatically bump ClientDependency on deploy

Created by Chriztian Steinmeier 12 Jan 2017, 14:45:23 Updated by Chriztian Steinmeier 07 Feb 2018, 22:48:52

Is duplicated by: UAAS-670

I'm not totally sure what the best strategy is, but I find it weird that I have to bump the ClientDependency version myself, before finally deploying a chunk of changes from DEV to LIVE.

If there were a switch in the portal for this, I'd personally always have it ON (to auto-update CD) but I'm sure someone could have a really good use for turning it OFF for a specific deploy; e.g. for very large sites with many sessions and you know nothing's changed so don't want to force a cold refresh).

Comments

Kevin Jump 12 Jan 2017, 14:57:10

i have a basic health check to check the age of the files in the client dependency folder and increment the version number - https://www.nuget.org/packages/Jumoo.CdfHealthChecker/ ''I haven't tidied up the repo yet but i will push it to github - its not the most complex code''

maybe the feature could be implemented as a health check so if you don't want it to happen to automatically you could push do it via the back office ?


Chriztian Steinmeier 12 Jan 2017, 15:10:19

I like the Health Check idea very much, as it allows me to "just" do it without having to go through the portal.

(What happens on next deploy is another headache, I guess?)


Niels Lyngsø 15 Nov 2017, 13:48:20

I would like something simelar. An idea could be if any file of the listed types in 'fileDependencyExtensions' in ClientDependency.config has changed, it should get a new version id automatically.


Priority: Normal

Type: Bug

State: Open

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: