Introduce a new traversal policy #598
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
The "always" traversal policy behaves as follows: - if the tool result (e.g. licensee) for a specific component exist, the component will be refetched and the tool will be rerun. - if the tool result for a specific component is missing, using the "always" policy leads to a "Unreachable for reprocessing" status and the tool being skipped. The "always" traversal policy is basically a rerun for all the previously ran tools. It is somewhat cumbersome in the case to retriger harvest, especially for integration tests. The proposed new policy make reharvest simpler: - When the tool result for a component is available, the tool will be rerun and tool result updated, similar to the "always" policy. - When the tool result for a component is not available, the component will be fetched and the tool will be run. In summary, this "reharvestAlways" policy is to rerun the harvest tools if results exist and run the harvest tools if results are missing.
RomanIakovlev
approved these changes
Sep 27, 2024
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.
The "always" traversal policy behaves as follows:
The "always" traversal policy is basically a rerun for all the previously ran tools. It is somewhat cumbersome in the case to retrigger harvest, especially for integration tests.
The proposed new policy make re-harvest simpler: