| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`cancel_merge_when_pipeline_succeeds()` (#2350)
* Call was incorrectly using a `PUT` method when should have used a
`POST` method.
* Changed return type to a `dict` as GitLab only returns
{'status': 'success'} on success. Since the function didn't work
previously, this should not impact anyone.
* Updated the test fixture `merge_request` to add ability to create
a pipeline.
* Added functional test for `mr.cancel_merge_when_pipeline_succeeds()`
Fixes: #2349
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Simplify usage of `wait_for_sidekiq` by putting the assert if it timed
out inside the function rather than after calling it.
|
|
|
|
|
|
|
|
|
| |
* Use `settings.delayed_group_deletion=False` as that is the
recommended method to turn off the delayed group deletion now.
* Change test to look for `default` as `pages` is not mentioned in
the docs[1]
[1] https://docs.gitlab.com/ee/api/sidekiq_metrics.html#get-the-current-queue-metrics
|
|\
| |
| | |
test: attempt to make functional test startup more reliable
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The functional tests have been erratic. Current theory is that we are
starting the tests before the GitLab container is fully up and
running.
* Add checking of the Health Check[1] endpoints.
* Add a 20 second delay after we believe it is up and running.
* Increase timeout from 300 to 400 seconds
[1] https://docs.gitlab.com/ee/user/admin_area/monitoring/health_check.html
|
|/
|
|
| |
In GitLab >= 15.0 `title` is required when creating a topic.
|
|
|
|
| |
This reverts commit 67ab24fe5ae10a9f8cc9122b1a08848e8927635d.
|
| |
|
|
|
|
|
|
| |
Enable using GitLab Enterprise Edition (EE) in the functional tests.
This will allow us to add functional tests for EE only features in the
functional tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Saw issues in the CI where reset_gitlab() would fail. It would fail to
delete the group that is created when GitLab starts up. Extending the
timeout didn't fix the issue.
Changed the code to use the new `helpers.safe_delete()` function.
Which will delete the resource and then make sure it is deleted before
returning.
Also added some logging functionality that can be seen if logging is
turned on in pytest.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In our fixtures that create:
- groups
- project merge requests
- projects
- users
They delete the created objects after use. Now wait to ensure the
objects are deleted before continuing as having unexpected objects
existing can impact some of our tests.
|
|
|
|
|
|
|
| |
Ensure the path elements that are passed to the server are escaped.
For example a "/" will be changed to "%2F"
Closes: #2116
|
|
|
|
|
| |
Have been seeing timeout issues more and more. Increase timeout from
200 seconds to 300 seconds (5 minutes).
|
|
|
|
| |
This reverts commit e3035a799a484f8d6c460f57e57d4b59217cd6de.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Add EncodedId string class. This class returns a URL-encoded string
but ensures it will only URL-encode it once even if recursively
called.
Also added some functional tests of 'lazy' objects to make sure they
work.
|
|
|
|
|
|
|
|
|
|
| |
I have found trying to debug issues in the functional tests can be
difficult. Especially when trying to figure out failures in the CI
running on Github.
Add logging to `tests/functional/conftest.py` to have a better
understanding of what is happening during a test run which is useful
when trying to troubleshoot issues in the CI.
|
|
|
|
|
|
|
|
|
| |
Ensure reset_gitlab() succeeds by waiting to make sure everything has
been deleted as expected. If the timeout is exceeded fail the test.
Not using `wait_for_sidekiq` as it didn't work. During testing I
didn't see any sidekiq processes as being busy even though not
everything was deleted.
|
|
|
|
| |
It is not yet available upstream.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
BREAKING CHANGE: As of python-gitlab 3.0.0, the default branch for development
has changed from `master` to `main`.
|
|
|
|
|
|
|
| |
Timing issues between requesting group deletion and GitLab enacting that
deletion resulted in errors while attempting to delete a user which was
the sole owner of said group (see: test_groups). Pass the 'hard_delete'
parameter to ensure user deletion.
|
|
|
|
|
| |
Deploy tokens would remain in the instance if the respective project or
group was deleted without explicitly revoking the deploy tokens first.
|
|
|
|
|
|
| |
Additionally updates token creation to make use of `first_or_create()`,
to avoid errors from the script caused by GitLab constraints preventing
duplicate tokens with the same value.
|
|
Rename the 'tools/functional/' directory to 'tests/functional/'
This makes more sense as these are functional tests and not tools.
This was dicussed in:
https://github.com/python-gitlab/python-gitlab/discussions/1468
|