Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
k8s-ingress
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
3
Merge Requests
3
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
uplex-varnish
k8s-ingress
Commits
6b432437
Commit
6b432437
authored
May 17, 2020
by
Tim Leers
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Push releases to docker hub
parent
fdfa9071
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
26 additions
and
7 deletions
+26
-7
.gitlab-ci.yml
.gitlab-ci.yml
+26
-7
No files found.
.gitlab-ci.yml
View file @
6b432437
...
...
@@ -2,6 +2,27 @@ stages:
-
test
-
build
-
e2e
-
release
push_to_docker
:
image
:
docker:19.03.8
stage
:
release
only
:
-
tags
services
:
-
docker:19.03.8-dind
script
:
-
docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:$CI_COMMIT_REF_NAME
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/varnish:$CI_COMMIT_REF_NAME
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/controller:$CI_COMMIT_REF_NAME
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:$CI_COMMIT_REF_NAME uplex/viking-haproxy:$CI_COMMIT_TAG
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/varnish:$CI_COMMIT_REF_NAME uplex/viking-varnish:$CI_COMMIT_TAG
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/controller:$CI_COMMIT_REF_NAME uplex/viking-controller:$CI_COMMIT_TAG
-
docker login -u "$DOCKERHUB_USER" -p "$DOCKERHUB_CREDS"
-
docker push uplex/viking-haproxy:$CI_COMMIT_TAG
-
docker push uplex/viking-varnish:$CI_COMMIT_TAG
-
docker push uplex/viking-controller:$CI_COMMIT_TAG
test
:
image
:
golang:1.11.6
...
...
@@ -236,11 +257,11 @@ example:varnish-pod-template:
-
docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/controller:$CI_COMMIT_SHA
# using haproxy and varnish image with latest tag due to performance. if we are changing this image a lot, we need to improve this as can lead to pulling the incorrect image
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/varnish:
latest
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:
latest
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/varnish:
$CI_COMMIT_REF_NAME
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:
$CI_COMMIT_REF_NAME
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/controller:$CI_COMMIT_SHA varnish-ingress/controller
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:
latest
varnish-ingress/haproxy
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/varnish:
latest
varnish-ingress/varnish
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/haproxy:
$CI_COMMIT_REF_NAME
varnish-ingress/haproxy
-
docker tag $CI_REGISTRY_IMAGE/varnish-ingress/varnish:
$CI_COMMIT_REF_NAME
varnish-ingress/varnish
-
kind load docker-image varnish-ingress/varnish
-
kind load docker-image varnish-ingress/haproxy
-
kind load docker-image varnish-ingress/controller
...
...
@@ -279,11 +300,9 @@ example:varnish-pod-template:
before_script
:
-
apk add -U make
-
docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:
latest
||
true
-
docker pull $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:
$CI_COMMIT_REF_NAME
||
true
after_script
:
-
docker tag varnish-ingress/$IMAGE $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:$CI_COMMIT_SHA
-
docker tag varnish-ingress/$IMAGE $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:$CI_COMMIT_REF_NAME
-
docker tag varnish-ingress/$IMAGE $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:latest
-
docker push $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:$CI_COMMIT_SHA
-
docker push $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:$CI_COMMIT_REF_NAME
-
docker push $CI_REGISTRY_IMAGE/varnish-ingress/$IMAGE:latest
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a 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