| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
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
|
|\ \
| | |
| | | |
chore: enable mypy check `warn_return_any`
|
| |/
| |
| |
| | |
Update code so that the `warn_return_any` check passes.
|
|\ \
| | |
| | | |
chore: make code PEP597 compliant
|
| |/
| |
| |
| |
| |
| | |
Use `encoding="utf-8"` in `open()` and open-like functions.
https://peps.python.org/pep-0597/
|
|\ \
| |/
|/| |
test(functional): bump GitLab docker image to 15.2.0-ee.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cluster support was deprecated in GitLab 14.5 [1]. And disabled by
default in GitLab 15.0 [2]
* Update docs to mark clusters as deprecated
* Remove testing of clusters
[1] https://docs.gitlab.com/ee/api/project_clusters.html
[2] https://gitlab.com/groups/gitlab-org/configure/-/epics/8
|
| |
| |
| |
| | |
In GitLab >= 15.0 `title` is required when creating a topic.
|
| |
| |
| |
| | |
Use the GitLab docker image 15.2.0-ee.0 in the functional testing.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a custom argparse help formatter that overrides the output
format to list items vertically.
The formatter is derived from argparse.HelpFormatter with minimal changes.
Co-authored-by: John Villalovos <john@sodarock.com>
Co-authored-by: Nejc Habjan <nejc.habjan@siemens.com>
|
| |
| |
| |
| |
| | |
https://github.com/python-gitlab/python-gitlab/issues/1698 has been
fixed. Add test to show that.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. If a value is of type ArrayAttribute then append '[]' to the name
of the value for query parameters (`params`).
This is step 3 in a series of steps of our goal to add full
support for the GitLab API data types[1]:
* array
* hash
* array of hashes
Step one was: commit 5127b1594c00c7364e9af15e42d2e2f2d909449b
Step two was: commit a57334f1930752c70ea15847a39324fa94042460
Fixes: #1698
[1] https://docs.gitlab.com/ee/api/#encoding-api-parameters-of-array-and-hash-types
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use `monkeypatch` to ensure that no config files are reported for the
test.
Closes: #2172
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
chore: fixtures: after delete() wait to verify deleted
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
| |
Catch the deprecation warning for the call to `gl.lint()`, so it won't
show up in the log.
|
| |
|
| |
|
|\
| |
| | |
feat: add `asdict()` and `to_json()` methods to Gitlab Objects
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an `asdict()` method that returns a dictionary representation copy
of the Gitlab Object. This is a copy and changes made to it will have
no impact on the Gitlab Object.
The `asdict()` method name was chosen as both the `dataclasses` and
`attrs` libraries have an `asdict()` function which has the similar
purpose of creating a dictionary represenation of an object.
Also add a `to_json()` method that returns a JSON string
representation of the object.
Closes: #1116
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the `attributes` method would show the original values in a
Gitlab Object even if they had been updated. Correct this so that the
updated value will be returned.
Also use copy.deepcopy() to ensure that modifying the dictionary returned can
not also modify the object.
|
|/
|
|
|
|
|
|
| |
This can be used to tell if a `RESTObject` was created using
`lazy=True`.
Add a message to the `AttributeError` if attribute access fails for an
instance created with `lazy=True`.
|
| |
|
| |
|
|
|
|
| |
Enable the `mypy` `strict_equality` check.
|
| |
|
| |
|