For a test license you can log into the license app with your GitLab login. You can use one of the shared licenses or if you need special add-ons, such as geo, you can generate a new one.
Please keep in mind you can't generate licenses for customers only for testing purposes. To generate a new license, log in to the license app and click on the 'New License' green button on the right side of the screen. Click on "You can also manually create a license without a Zuora subscription" at the bottom of the screen and fill out all non-optional fields.
As a member of support, you have access to a variety of ephemeral testing environments. You can build and tear down whatever resources you need to reproduce customer environments, try new features or learn about deploying a new topology.
The resources that are created in these environments are:
For a Digital Ocean and Docker testing environment (droplet) follow this guide. Once you've gone through all the steps excluding Usage you can skip to the below section named Creating Gitlab test instance.
For a GCP Testing environment, you should have access to the support-internal project as a baseline entitlement.
If you do not, please create an access request and tag your manager.
AWS credentials and instructions are stored in the Support Vault.
If you need access to Azure for testing, please create an access request and tag your manager.
Specifically for Group SAML/SCIM (GitLab.com) testing, shared account credentials are in 1password Azure Active Directory Sandbox (SAML Testing).
Specifically for Group SAML/SCIM (GitLab.com) testing, shared account credentials are in 1password Okta Sandbox (SAML Testing).
This guide involves configuring and setting up VMWare and Docker locally and assumes you're using Mac OS X.
This command will create a new VMware fusion virtual machine called gitlab-test-env that will act as a docker host.
-1)4GBgitlab-test-envvmwarefusiondocker-machine create \
--vmwarefusion-cpu-count -1 \
--vmwarefusion-memory-size 4096 \
--vmwarefusion-disk-size 30000 \
--driver vmwarefusion gitlab-test-env
This guide involves configuring and setting up VirtualBox and Docker locally and assumes you're using Mac OS X.
This command will create a new VirtualBox virtual machine called gitlab-test-env that will act as a docker host.
-1)4GBgitlab-test-envvirtualboxdocker-machine create \
--virtualbox-cpu-count -1 \
--virtualbox-memory 4096 \
--virtualbox-disk-size 30000 \
--driver virtualbox gitlab-test-env
In this example we'll create a GitLab EE 11.9.9 instance.
First connect the docker client to the docker host you created previously.
eval "$(docker-machine env gitlab-test-env)"
You can add this to your ~/.bash_profile file to ensure the docker client uses the gitlab-test-env docker host. You can use echo to do so:
echo 'eval "$(docker-machine env gitlab-test-env)"' >> ~/.bash_profile
Optionally replace the ee in the URL with ce
wget -q https://registry.hub.docker.com/v1/repositories/gitlab/gitlab-ee/tags -O - | sed -e 's/[][]//g' -e 's/"//g' -e 's/ //g' | tr '}' '\n' | awk -F: '{print $3}'
88882222
gitlab_shell_ssh_port using --env GITLAB_OMNIBUS_CONFIG gitlab-test-11.911.9.9-ee.0export SSH_PORT=2222
export HTTP_PORT=8888
export VERSION=11.9.9-ee.0
export NAME=gitlab-test-11.9
docker run --detach \
--env GITLAB_OMNIBUS_CONFIG="external_url 'http://$(docker-machine ip gitlab-test-env):$HTTP_PORT'; gitlab_rails['gitlab_shell_ssh_port'] = $SSH_PORT;" \
--hostname $(docker-machine ip gitlab-test-env) \
-p $HTTP_PORT:$HTTP_PORT -p $SSH_PORT:22 \
--name $NAME \
gitlab/gitlab-ee:$VERSION
docker-machine ip gitlab-test-env
# example output: 192.168.151.134
docker exec -it $NAME /bin/bash
# example commands
root@192:/# vi /etc/gitlab/gitlab.rb
root@192:/# gitlab-ctl reconfigure
For example, to set the gitlab_shell_ssh port on a container named gitlab-ee to port 2222
docker exec -it gitlab-ee \
sed -i "s/.*gitlab_shell_ssh_port.*/gitlab_rails['gitlab_shell_ssh_port'] = 2222/g" /etc/gitlab/gitlab.rb
docker exec -it gitlab-ee gitlab-ctl reconfigure
