SCM/CI: Improve storing projects and packages for setting flags #15978
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
Before, we stored (performed one call to the backend) a project or a package for every flag set with the SCM/CI integration set_flag step. From now on, we store only once for every single project or package.
eduardoj
force-pushed
the
refactoring/set_flags_store
branch
from
325e41d to
cb1e67c
Compare
danidoni
reviewed
Apr 12, 2024
danidoni
approved these changes
Apr 12, 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.
Before, we stored (performed one call to the backend) a project or a package for every flag set with the SCM/CI integration set_flag step.
From now on, we store only once for every single project or package.
Seen after working on #15951.