Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
佳 邓
Gitlab4j Api
Commits
0bba89b8
Commit
0bba89b8
authored
May 03, 2019
by
Greg Messner
Browse files
No longer needed (#311).
parent
25281b2d
Changes
1
Hide whitespace changes
Inline
Side-by-side
example-test-gitlab4j.properties
deleted
100644 → 0
View file @
25281b2d
#
# To test GitLab4J-API, you must have access to a GitLab server.
#
# Copy this file to test-gitlab4j.properties and set the property
# values to match the GitLab server you are testing against.
#
# REQUIRED: The following values must be set or the tests will fail.
# The TEST_PRIVATE_TOKEN and TEST_USERNAME must belong to an admin user.
TEST_PRIVATE_TOKEN
=
TEST_ACCESS_TOKEN
=
TEST_USERNAME
=
TEST_NAMESPACE
=
TEST_PROJECT_NAME
=
TEST_HOST_URL
=
# OPTIONAL: To test the GroupApi, set these to an existing group name and group-project name,
# and the username of a group member
TEST_GROUP
=
TEST_GROUP_PROJECT
=
TEST_GROUP_MEMBER_USERNAME
=
# OPTIONAL: Used to test transfer project
TEST_XFER_NAMESPACE
=
# OPTIONAL: To test oauth2Login, set these properties
TEST_LOGIN_USERNAME
=
TEST_LOGIN_PASSWORD
=
# OPTIONAL: To test sudo capability, provide a username to sudo as
TEST_SUDO_AS_USERNAME
=
# OPTIONAL: To test block/unblock capability, provide a username to block/unblock
TEST_BLOCK_USERNAME
=
# OPTIONAL: To test using GitLab4J-API with a proxy, set the following properties
TEST_PROXY_URI
=
TEST_PROXY_USERNAME
=
TEST_PROXY_PASSWORD
=
# OPTIONAL: To thest the HealthCheckApi provide the health check token from the GitLab server
TEST_HEALTH_CHECK_TOKEN
=
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment