[Build] Use own cache in Version-Increment workflow #3157
Merged
Conversation
This file contains hidden or 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
This avoids conflicting interference with the caches of the verification workflows in SWT.
HannesWell
force-pushed
the
fix-caching-version-check
branch
from
c884d0d to
91519c8
Compare
Member
Author
|
The testing seemed to be successful: Lets hope that it also works in practice. FYI @fedejeanne and @HeikoKlare |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As it was pointed out by @akurtakov, the version-check for SWT maybe fails because the used caches interfere with the caches of the verification workflows.
This change ensures that the version-check workflow has its own cache.