| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Use slugs for default project path and sanitize names before import
See merge request gitlab-org/gitlab-ce!21367
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Users importing from Bitbucket Cloud, Bitbucket Server, or GitHub
often complained about getting failed imports due to 422 errors.
This change ensures that project names are imported with names that
are guaranteed to pass the regular expression validation.
Part of #50021
|
| | |\ \
| | |/
| |/|
| | |
| | | |
[QA] Re-add Test::Instance for back-compatibility with GitLab < 11.3
See merge request gitlab-org/gitlab-ce!21339
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |/
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
|
| |\ \
| |/
| |
| | |
* master: (31 commits)
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "[QA] Automation Triage 11.1.0 RC9 - Filling textarea with deploy key timeouts sometime"
Closes #49179
See merge request gitlab-org/gitlab-ce!21258
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's too slow to use `set(value)`, often timing out.
Filling with JS is much faster for longer text, especially
when the key size is larger than 8192.
Before this patch:
```
Top 3 slowest examples (256.83 seconds, 89.4% of total time):
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::RSA(8192) to clone code using pipelines
161.26 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::ECDSA(521) to clone code using pipelines
47.79 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::ED25519() to clone code using pipelines
47.79 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
```
Note that 161.26 was timed out. So it would actually take longer if
it could ever complete. After patch:
```
Top 3 slowest examples (166.72 seconds, 83.8% of total time):
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::RSA(8192) to clone code using pipelines
83.66 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::ECDSA(521) to clone code using pipelines
42.78 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
cloning code using a deploy key user sets up a deploy key with QA::Runtime::Key::ED25519() to clone code using pipelines
40.27 seconds ./qa/specs/features/project/deploy_key_clone_spec.rb:42
```
Not that faster for smaller keys, but it's much faster for RSA 8192
(2 times faster). This was inspired from:
https://github.com/teamcapybara/capybara/blob/679548cea10773d45e32808f4d964377cfe5e892/lib/capybara/selenium/node.rb#L217
Where it's clearing the field by filling an empty string. Here we
do the same for the exact value we want to fill.
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[QA] Improve the fork scenario to take a username and password instead of always…
Closes gitlab-org/quality/staging#2
See merge request gitlab-org/gitlab-ce!21090
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
always creating a new user
Fixes https://gitlab.com/gitlab-org/quality/staging/issues/2.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| | |
This test takes too long and leads to flakiness so we disable it for now until somebody can figure out why it takes longer than 20 minutes to finish.
|
| |/ |
|
| |
|
|
| |
This fixes https://gitlab.com/gitlab-org/quality/nightly/issues/3 because the code_quality job holds up the production job. Waiting longer should reduce the likelihood of this.
|
| |\
| |
| |
| |
| | |
CE port of "List groups with developer maintainer access on project creation"
See merge request gitlab-org/gitlab-ce!21051
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
to "for all new and renamed projects""
|
| |
|
| |
This reverts merge request !20801
|
| | |
|
| |
|
|
| |
to appear
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is not done by default as it is said to incur a performance hit,
paired with local storage not always being used by the site being
tested.
(https://github.com/teamcapybara/capybara/issues/1702#issuecomment-219483444)
GitLab uses localStorage, for things like remembering which tab you used
last (on the login page for example, between sign-in, ldap, and register)
Fixes: https://gitlab.com/gitlab-org/gitlab-qa/issues/303
|
| |
|
|
| |
Signed-off-by: Tao Wang <twang2218@gmail.com>
|
| |
|
|
|
|
| |
class as well
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
|
| |\
| |
| |
| |
| | |
i18n: externalize strings from 'app/views/doorkeeper'
See merge request gitlab-org/gitlab-ce!19695
|
| | |
| |
| |
| | |
Signed-off-by: Tao Wang <twang2218@gmail.com>
|
| |/ |
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\
| |
| |
| |
| | |
[QA] Fix duplicate year in namespace name
See merge request gitlab-org/gitlab-ce!20581
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'49139-sleep-before-installing-tiller-to-prevent-race-condition' into 'master'
Resolve "Installing helm tiller sometimes fails with no api token found"
Closes #49139
See merge request gitlab-org/gitlab-ce!20580
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise we ocassionally see a race condition error:
No API token found for service account "default", retry after the token is automatically created and added to the service account
Waiting 10 seconds should remove this risk.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Resolve "Follow-up from "Milestone tests""
Closes #48690
See merge request gitlab-org/gitlab-ce!20563
|
| | | | |
| | | |
| | | |
| | | | |
closes #48690
|
| | |_|/
|/| |
| | |
| | | |
This reverts commit d493c91d21250e0b94a14f1808fcf8bb6f1a8d03.
|
| |/ /
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Add a new scenario to test GitHub import
Closes gitlab-qa#146
See merge request gitlab-org/gitlab-ce!19555
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/ |
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
