Skip to content

Commit 7a54254

Browse files
author
Sameer Naik
committed
release 8.0.4-2
1 parent 0cfc39b commit 7a54254

File tree

3 files changed

+22
-22
lines changed

3 files changed

+22
-22
lines changed

README.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[![Docker Repository on Quay.io](https://quay.io/repository/sameersbn/gitlab-ci/status "Docker Repository on Quay.io")](https://quay.io/repository/sameersbn/gitlab-ci)
22

3-
# quay.io/sameersbn/gitlab-ci:8.0.4-1
3+
# quay.io/sameersbn/gitlab-ci:8.0.4-2
44

55
`quay.io/sameersbn/gitlab-ci:8.x.x` image is meant for migration purposes only.
66

@@ -65,7 +65,7 @@ Dockerfile to build a [GitLab CI](https://about.gitlab.com/gitlab-ci/) container
6565

6666
## Version
6767

68-
Current Version: `8.0.4-1`
68+
Current Version: `8.0.4-2`
6969

7070
*The gitlab-ci version should match the gitlab version to avoid any compatibility issues*
7171

@@ -116,7 +116,7 @@ docker pull quay.io/sameersbn/gitlab-ci:latest
116116
Starting from GitLab CI version `5.1.0`, You can pull a particular version of GitLab CI by specifying the version number. For example,
117117

118118
```bash
119-
docker pull quay.io/sameersbn/gitlab-ci:8.0.4-1
119+
docker pull quay.io/sameersbn/gitlab-ci:8.0.4-2
120120
```
121121

122122
Alternately you can build the image yourself.
@@ -169,7 +169,7 @@ docker run --name gitlab-ci -d \
169169
--env 'GITLAB_CI_PORT=10081' --env 'GITLAB_URL=http://localhost:10080' \
170170
--env 'GITLAB_APP_ID=xxx' --env 'GITLAB_APP_SECRET=yyy' \
171171
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
172-
quay.io/sameersbn/gitlab-ci:8.0.4-1
172+
quay.io/sameersbn/gitlab-ci:8.0.4-2
173173
```
174174

175175
Point your browser to `http://localhost:10081` and login using your GitLab credentials.
@@ -200,7 +200,7 @@ Volumes can be mounted in docker by specifying the **'-v'** option in the docker
200200
```bash
201201
docker run --name gitlab-ci -it --rm \
202202
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
203-
quay.io/sameersbn/gitlab-ci:8.0.4-1
203+
quay.io/sameersbn/gitlab-ci:8.0.4-2
204204
```
205205

206206
## Database
@@ -230,7 +230,7 @@ docker run --name gitlab-ci -it --rm \
230230
--env 'DB_TYPE=postgres' --env 'DB_HOST=192.168.1.100' \
231231
--env 'DB_NAME=gitlab_ci_production' \
232232
--env 'DB_USER=gitlab_ci' --env 'DB_PASS=password' \
233-
quay.io/sameersbn/gitlab-ci:8.0.4-1
233+
quay.io/sameersbn/gitlab-ci:8.0.4-2
234234
```
235235

236236
#### Linking to PostgreSQL Container
@@ -274,7 +274,7 @@ We are now ready to start the GitLab CI application.
274274
docker run --name gitlab-ci -it --rm --link gitlab-ci-postgresql:postgresql \
275275
--env 'GITLAB_URL=http://172.17.0.2' \
276276
--env 'GITLAB_APP_ID=xxx' --env 'GITLAB_APP_SECRET=yyy' \
277-
quay.io/sameersbn/gitlab-ci:8.0.4-1
277+
quay.io/sameersbn/gitlab-ci:8.0.4-2
278278
```
279279

280280
Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the postgresql container as they are specified in the `docker run` command for the postgresql container. This is made possible using the magic of docker links and works with the following images:
@@ -328,7 +328,7 @@ docker run --name gitlab-ci -it --rm \
328328
--env 'GITLAB_APP_ID=xxx' --env 'GITLAB_APP_SECRET=yyy' \
329329
--env 'DB_HOST=192.168.1.100' --env 'DB_NAME=gitlab_ci_production' \
330330
--env 'DB_USER=gitlab_ci' --env 'DB_PASS=password' \
331-
quay.io/sameersbn/gitlab-ci:8.0.4-1
331+
quay.io/sameersbn/gitlab-ci:8.0.4-2
332332
```
333333

334334
#### Linking to MySQL Container
@@ -372,7 +372,7 @@ We are now ready to start the GitLab CI application.
372372
docker run --name gitlab-ci -it --rm --link gitlab-ci-mysql:mysql \
373373
--env 'GITLAB_URL=http://172.17.0.2' \
374374
--env 'GITLAB_APP_ID=xxx' --env 'GITLAB_APP_SECRET=yyy' \
375-
quay.io/sameersbn/gitlab-ci:8.0.4-1
375+
quay.io/sameersbn/gitlab-ci:8.0.4-2
376376
```
377377

378378
Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the mysql container as they are specified in the `docker run` command for the mysql container. This is made possible using the magic of docker links and works with the following images:
@@ -399,7 +399,7 @@ The image can be configured to use an external redis server instead of starting
399399
```bash
400400
docker run --name gitlab-ci -it --rm \
401401
--env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \
402-
quay.io/sameersbn/gitlab-ci:8.0.4-1
402+
quay.io/sameersbn/gitlab-ci:8.0.4-2
403403
```
404404

405405
### Linking to Redis Container
@@ -436,7 +436,7 @@ Please refer the [Available Configuration Parameters](#available-configuration-p
436436
```bash
437437
docker run --name gitlab-ci -it --rm \
438438
--env '[email protected]' --env 'SMTP_PASS=PASSWORD' \
439-
quay.io/sameersbn/gitlab-ci:8.0.4-1
439+
quay.io/sameersbn/gitlab-ci:8.0.4-2
440440
```
441441

442442
Please look up the [Available Configuration Parameters](#available-configuration-parameters) section for all available SMTP configuration options.
@@ -514,7 +514,7 @@ docker run --name gitlab-ci -it --rm \
514514
--publish 10081:80 --publish 10444:443 \
515515
--env 'GITLAB_CI_PORT=10444' -env 'GITLAB_CI_HTTPS=true' \
516516
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
517-
quay.io/sameersbn/gitlab-ci:8.0.4-1
517+
quay.io/sameersbn/gitlab-ci:8.0.4-2
518518
```
519519

520520
In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer.
@@ -530,7 +530,7 @@ docker run --name gitlab-ci -it --rm \
530530
--env 'GITLAB_CI_HTTPS=true' \
531531
--env 'GITLAB_CI_HTTPS_HSTS_MAXAGE=2592000' \
532532
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
533-
quay.io/sameersbn/gitlab-ci:8.0.4-1
533+
quay.io/sameersbn/gitlab-ci:8.0.4-2
534534
```
535535

536536
If you want to completely disable HSTS set `GITLAB_CI_HTTPS_HSTS_ENABLED` to `false`.
@@ -549,7 +549,7 @@ In summation, when using a load balancer, the docker command would look for the
549549
docker run --name gitlab-ci -it --rm \
550550
--env 'GITLAB_CI_HTTPS=true' \
551551
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
552-
quay.io/sameersbn/gitlab-ci:8.0.4-1
552+
quay.io/sameersbn/gitlab-ci:8.0.4-2
553553
```
554554

555555
#### Establishing trust with your server
@@ -586,7 +586,7 @@ Let's assume we want to deploy our application to '/ci'. GitLab CI needs to know
586586
docker run --name gitlab-ci -it --rm \
587587
--env 'GITLAB_CI_RELATIVE_URL_ROOT=/ci' \
588588
--volume /srv/docker/gitlab-ci/gitlab-ci:/home/gitlab_ci/data \
589-
quay.io/sameersbn/gitlab-ci:8.0.4-1
589+
quay.io/sameersbn/gitlab-ci:8.0.4-2
590590
```
591591

592592
GitLab CI will now be accessible at the `/ci` path, e.g. `http://www.example.com/ci`.
@@ -675,7 +675,7 @@ Execute the rake task to create a backup.
675675

676676
```bash
677677
docker run --name gitlab-ci -it --rm [OPTIONS] \
678-
quay.io/sameersbn/gitlab-ci:8.0.4-1 app:rake backup:create
678+
quay.io/sameersbn/gitlab-ci:8.0.4-2 app:rake backup:create
679679
```
680680

681681
A backup will be created in the backups folder of the [Persistence](#persistence). You can change the location of the backups using the `GITLAB_CI_BACKUP_DIR` configuration parameter.
@@ -696,7 +696,7 @@ Execute the rake task to restore a backup. Make sure you run the container in in
696696

697697
```bash
698698
docker run --name gitlab-ci -it --rm [OPTIONS] \
699-
quay.io/sameersbn/gitlab-ci:8.0.4-1 app:rake backup:restore
699+
quay.io/sameersbn/gitlab-ci:8.0.4-2 app:rake backup:restore
700700
```
701701

702702
The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.
@@ -705,7 +705,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the
705705

706706
```bash
707707
docker run --name gitlab-ci -it --rm [OPTIONS] \
708-
quay.io/sameersbn/gitlab-ci:8.0.4-1 app:rake backup:restore BACKUP=1417624827
708+
quay.io/sameersbn/gitlab-ci:8.0.4-2 app:rake backup:restore BACKUP=1417624827
709709
```
710710

711711
## Automated Backups
@@ -731,7 +731,7 @@ To upgrade to newer GitLab CI releases, simply follow this 3 step upgrade proced
731731
- **Step 1**: Update the docker image.
732732

733733
```bash
734-
docker pull quay.io/sameersbn/gitlab-ci:8.0.4-1
734+
docker pull quay.io/sameersbn/gitlab-ci:8.0.4-2
735735
```
736736

737737
- **Step 2**: Stop and remove the currently running image
@@ -744,7 +744,7 @@ docker rm gitlab-ci
744744
- **Step 3**: Start the image
745745

746746
```bash
747-
docker run --name gitlab-ci -d [OPTIONS] quay.io/sameersbn/gitlab-ci:8.0.4-1
747+
docker run --name gitlab-ci -d [OPTIONS] quay.io/sameersbn/gitlab-ci:8.0.4-2
748748
```
749749

750750
## Shell Access

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
8.0.4-1
1+
8.0.4-2

docker-compose.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ redis:
1111
volumes:
1212
- /srv/docker/gitlab-ci/redis:/var/lib/redis
1313
ci:
14-
image: quay.io/sameersbn/gitlab-ci:8.0.4-1
14+
image: quay.io/sameersbn/gitlab-ci:8.0.4-2
1515
links:
1616
- redis:redisio
1717
- postgresql:postgresql

0 commit comments

Comments
 (0)