-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempt to fix gitlab tests flakiness #1425
Draft
raul-arabaolaza
wants to merge
9
commits into
jenkinsci:master
Choose a base branch
from
raul-arabaolaza:FIX_GITLAB2
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Commits on Sep 26, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 4e66431 - Browse repository at this point
Copy the full SHA 4e66431View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1d56523 - Browse repository at this point
Copy the full SHA 1d56523View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0858e1b - Browse repository at this point
Copy the full SHA 0858e1bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 735d852 - Browse repository at this point
Copy the full SHA 735d852View commit details
Commits on Nov 21, 2023
-
Fix flakiness on Gitlab tests (First PR, Local Attempt 1652756)
I detected most of the times flakiness was caused by a lack of resources in the Gitlab container, as a result many API calls at random returned a 502 error code and an HTML page asking for the user to refresh... I have added a custom configuration to the Gitlab fixture which should help in resource constrained environments and increased the request timeout. Also not it uses the readiness checks instead of html web scrapping. Also some small code changes here and there like closing the gitlab4j clients or slighly reduce the scope of some tests.
Configuration menu - View commit details
-
Copy full SHA for 0eaf1f9 - Browse repository at this point
Copy the full SHA 0eaf1f9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4c65e63 - Browse repository at this point
Copy the full SHA 4c65e63View commit details -
Configuration menu - View commit details
-
Copy full SHA for c065f8a - Browse repository at this point
Copy the full SHA c065f8aView commit details -
Configuration menu - View commit details
-
Copy full SHA for cfd464f - Browse repository at this point
Copy the full SHA cfd464fView commit details
Commits on Nov 22, 2023
-
Configuration menu - View commit details
-
Copy full SHA for b8b6f0e - Browse repository at this point
Copy the full SHA b8b6f0eView commit details
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.