[Build] Update snapshots in Version-Increment workflow #3094
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 ensures that the workflow for automated version increments always operates on the latest content from the I-builds repository and discards cached data.
HannesWell
force-pushed
the
update-snapshots-in-versions-workflow
branch
from
9ced763 to
6e2e49f
Compare
Member
Author
|
At least in eclipse-platform/eclipse.platform.swt#2198 this seems to have helped to get the fresh composite content from the EF download-server, after latest I-build was marked unstable so that the 4.37-I-builds composite only contained the reference to the previous 4.36-RC2 (see also #3070 (comment)). In general I have the impression that the download-server caches returned results for quite a long time. |
Contributor
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6088 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This ensures that the workflow for automated version increments always operates on the latest content from the I-builds repository and discards cached data.
At least that's my hope and that worked locally for me. Let's see if it also helps in the CI.