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

Compute history #204

Merged
merged 16 commits into from
Aug 30, 2022
Merged

Compute history #204

merged 16 commits into from
Aug 30, 2022

Conversation

edwinkortman
Copy link
Contributor

@edwinkortman edwinkortman commented Aug 29, 2022

Fixes #149

Edwin Kortman added 6 commits August 29, 2022 13:33
This interface will allow us to mock the service instead of having to instantiate the entire object each time we want to test it.
It's failing because the activity isn't doing anything yet.
The cache directory is needed because that's where all the relevant information about git is located.
This git path is needed later down the line for determining the history intervals. The idea is that an analysis only has one source control, it will (most likely) not mix SVN and Git for example.
The activity uses ComputeHistory.cs to determine the intervals it has to stop at, for each interval found it will fire the HistoryIntervalStopFoundEvent.cs
@mscottford mscottford marked this pull request as ready for review August 29, 2022 15:15
@mscottford mscottford self-requested a review August 29, 2022 15:15
Copy link
Member

@mscottford mscottford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just need to remove the additional database fields.

Edwin Kortman and others added 4 commits August 29, 2022 18:22
The CacheDb.cs already knows where it lives, so just re-use that instead of saving it with the analysis.
Co-authored-by: M. Scott Ford <scott@corgibytes.com>
Edwin Kortman added 5 commits August 29, 2022 20:02
…e Cache Directory the entire time

From ComputeHistory the method ComputeCommitHistory also has been removed. This is only used in the command runner, and those will get removed eventually. To save some refactoring-time remove it now.
This object is then used by the compute history command runner. The object is the combination of a repository id and the cache directory. Together they can form a path where the repository has been cloned to.
@edwinkortman
Copy link
Contributor Author

@mscottford I've re-requested your review as I've added the implementation for AnalysisLocation and I want to know if this is how you envisioned it.

@edwinkortman edwinkortman added the enhancement New feature or request label Aug 30, 2022
@edwinkortman edwinkortman self-assigned this Aug 30, 2022
This should not have been removed in an earlier commit as this option is used by the analyse command (yet to be implemented).
@mscottford
Copy link
Member

Most recent commit approved during pairing session.

@edwinkortman edwinkortman merged commit 4f4e4cc into main Aug 30, 2022
@edwinkortman edwinkortman deleted the compute-history branch August 30, 2022 15:45
@github-actions github-actions bot locked and limited conversation to collaborators Aug 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compute history
2 participants