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.
Just a few small things that will make crowd tests more stable. During the tests, we need to create a new user directory in Btibucket. Since there's no REST API for that, we first need to get atl_token by making a get call and parsing html response. We run 3 instances of Bitbucket, and atl_token is a per tomcat thing.That's why we scale Btibucket to 1 first. Without a short wait, occasionally Bitbucket does not respond with atl_token. After the scaledown, let's give Kube and Bitbucket some time to get back to a normal state. Also, let's make an additional call if the initial one did not return atl_token (network glitch etc).
Tested 13 runs :) Not a single failure.
Also, increasing tests timeout as sometimes due to networking conditions and how fast AWS is on a given day, the tests are timing out.
Checklist