-
Notifications
You must be signed in to change notification settings - Fork 74
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
Avoid unnecessary rescans #268
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EyalDelarea
added
improvement
Automatically generated release notes
and removed
new feature
Automatically generated release notes
labels
Mar 19, 2023
eyalbe4
requested changes
Mar 27, 2023
@eyalbe4 After our talk , the solution was quit simple. The previously unused function in the tests is |
eyalbe4
requested changes
Mar 28, 2023
eyalbe4
requested changes
Mar 30, 2023
…ecessary_rescans
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Description:
When using cron job to monitor some VCS providers there are unnecessary rescans of the repo, as nothing has changed from the last scan.
Solution:
FrogBot will now mark that last commit build status as successful when scan has been completed.
when it will encounter this commit again it will not preform a rescan, unless certain amount of time has passed. currently set to 4 days as default.