Skip to content

Latest commit

 

History

History
104 lines (59 loc) · 3.5 KB

set-up-gitlab.md

File metadata and controls

104 lines (59 loc) · 3.5 KB
Raw

Setting up Gitlab for the Continuous Delivery Demo

We use docker containers for all of the continuous deliver pieces, so follow the first section on setting up the Docker container on your host. Docker isn't required if you wish to manually set up an environment somewhere else.

Set up Docker container

You'll need to pull the GitLab docker image that we use for this demo:

docker pull sameersbn/gitlab:7.2.2

Then you can start the container:

docker run -itdP --name gitlab --privileged -e 'GITLAB_SIGNUP=true' sameersbn/gitlab:7.2.2

To find out what port (on the host) the Gitlab container is listening on (for port 80), run this:

docker port gitlab 80

Required manual steps

Here are the manual steps we need to take to set up the gitlab repo. Note, I'm fully aware there's a rich Gitlab API that we can use to automate most of this stuff. Feel free to submit a pull request.

Set up user account

Then you'll need to navigate to the location on the host where gitlab is exposed, and login with these credentials (note it could take a minute or two for the GitLab application to initialize and come up):

Use these default credentials:

username: root
password: 5iveL!fe

Gitlab Signin

At this point you'll be asked to choose a new password. For the demo, we're using redhat01 as the password.

Gitlab Signin

Adding SSH keys

You should add ssh keys, but you don't have to. If you wish to, you can use the keys located in the $PROJ_ROOT/ssh-keys/git folder of this project. If you don't use SSH keys, you can use HTTP access with the root/redhat01 account as the un/pw

Example of HTTP git url:

http://root:redhat01@__GITLAB_IP__:80/root/quickstart-fuse-rest.git

If you do use the SSH keys, it'll be handy to have this in your ssh config file so you can push to any easy host/port combo:

Host gitlab 
    Hostname ceposta-public
    Port 49153
    IdentityFile ~/.ssh/redhat_rsa

That way your git URL can just be:

git@gitlab:root/quickstart-fuse-rest.git

For the demo, we'll just use the HTTP git URL and as a side note, the gerrit replication uses the HTTP url.

Setting up the quickstart-fuse-rest project

You should create a new GitLab project and name it exactly quickstart-fuse-rest. The naming is important because the Jenkins build jobs are set up to look for that name.

Gitlab Signin

Make sure you mark the project public, and make it an empty project.

We will use Gerrit to replicate code to this Gitlab Project so we don't need to import anything.

Setting up the automation scripts project

The Jenkins builds will use scripts to automate creating the OpenShift Enterprise + Fuse environment. Those scripts are located in this project (eg, https://github.com/christian-posta/ceposta-devops-ose).

We need to create a new PUBLIC project like we did above, only we have to name it ceposta-devops-ose.

Then you can clone the ceposta-devops-ose project from github, add a remote and push it to gitlab:

git remote add gitlab http://root:redhat01@ceposta-public:49173/root/ceposta-devops-ose.git
git push gitlab master

What's Next?

You can go right to the Demo or you can set up Gerrit since that's the next container that should be set up to do the demo.