Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect #28 historical analysis #29

Merged
merged 11 commits into from
Dec 26, 2015
Merged

Connect #28 historical analysis #29

merged 11 commits into from
Dec 26, 2015

Conversation

bglusman
Copy link
Owner

Add archeological_dig clas and DebtCeiling.dig feature for historical debt analysis.

@bglusman bglusman force-pushed the historical_analysis branch 5 times, most recently from d43ec4c to dce8aa5 Compare August 31, 2015 14:52
@bglusman bglusman force-pushed the historical_analysis branch from dce8aa5 to 78dad5f Compare August 31, 2015 15:03
@bglusman
Copy link
Owner Author

bglusman commented Sep 5, 2015

@seanmarcia since you were interested in/suggested the debt clock idea (#2) hopefully this will be of some interest to you... it needs refactoring, cleanup and tests (I think I want to use open3/popen3 instead of simply shelling out to git, as the warnings when failing to show git notes get noisy), but this is a surprisingly usable v1... it should only take a long time to run once, then be fairly fast afterwards, and can hook into the output data structure from DebtCeiling.dig with #results method to get all the historical debt scores. We can work on visualizing that with JS or whatever.. maybe a project for DCamp?

@bglusman bglusman force-pushed the historical_analysis branch from c4503ac to c573de4 Compare September 5, 2015 03:50
Using Open3 to avoiding noisy output to stderr etc
Still some blank lines coming out, from where?

Also logic changes to travel back to original
branch rather than detached head state
@bglusman bglusman force-pushed the historical_analysis branch from 057e5b0 to f5866a3 Compare September 6, 2015 16:47
@bglusman bglusman changed the title WIP: Connect #28 begin notional plan for git note/history storage Connect #28 historical analysis Sep 9, 2015
@bglusman
Copy link
Owner Author

Note to self/others: since the main usecase for this historical data might be on a CI server, it will git clone the repo everytime and blow away any git notes created.... so we should probably also support Redis, by checking if Redis gem is installed and some config present, and if so cache data there instead?

@pboling
Copy link

pboling commented Nov 16, 2015

@bglusman This is begging to be a SAAS product that would store the history, just like CodeClimate does. Have you given that any thought?

@bglusman bglusman force-pushed the historical_analysis branch 3 times, most recently from 6951f19 to bef0b7f Compare December 26, 2015 02:23
Extract method for cleanup and raise debt limit
because I exceeded current ceiling, sigh
@bglusman bglusman force-pushed the historical_analysis branch from bef0b7f to 6300d99 Compare December 26, 2015 02:40
@bglusman bglusman merged commit 93090c3 into master Dec 26, 2015
@bglusman bglusman deleted the historical_analysis branch December 27, 2015 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants