[JENKINS-71749] Add stable order when searching for repositories in GH organization #907
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.
Description
JENKINS-71749
When scanning the organization, repositories are obtained using
searchGH API. Results are paged by100items, in SR we have more repositories so the final result is the result of multiple paged calls. There is no sorting order set when repos are fetched, resulting in abest-matchsorting (according to GH), which turned out to be not a stable sort - the same repository was returned twice or even three times on multiple pages, and other repositories were lost. As a result, we observed that jobs were disappearing on Jenkins in the Org Folder.This PR adds stable sorting, based on the repository name, so no results are lost.
Submitter checklist
Reviewer checklist
Documentation changes
Users/aliases to notify