You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the common failure modes of our production system is "hey, this widget was supposed to have been updated, but seems to be running old code". To help make this problem easier & quicker to diagnose, we should modify each indicator so that when it starts up, it prints its name and some kind of version information.
Version information could be:
repo version (this is available in .bumpversion.cfg but probably doesn't survive our deployment mechanism)
indicator version (which we currently don't track, but maybe we should? it would probably live in setup.py (claims_hosp example))
gitref (not visible in deployed code but we could make jenkins write it down)
build date (another thing jenkins would have to do)
The text was updated successfully, but these errors were encountered:
Assigning Mitch to this -- work with @korlaxxalrok to figure out how to store/deploy versioning information with Jenkins, then go through each indicator and add a log line at the start of run_module.
usafacts
jhu
dsew_community_profile
google_symptoms - will need auth keys to run locally (ask Luke)
One of the common failure modes of our production system is "hey, this widget was supposed to have been updated, but seems to be running old code". To help make this problem easier & quicker to diagnose, we should modify each indicator so that when it starts up, it prints its name and some kind of version information.
Version information could be:
The text was updated successfully, but these errors were encountered: