Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
presentation-gitlab-k8s
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Admin message
la forge Heptapod sera en maintenance de 12h à 13h le mardi 18 mars 2025
Show more breadcrumbs
Arthur Lutz
presentation-gitlab-k8s
Commits
ac0ab640a794
Commit
ac0ab640a794
authored
6 years ago
by
Alexander Trost
Browse files
Options
Downloads
Patches
Plain Diff
Use new image.entrypoint and image.name GitLab CI format
parent
5ce824774d24
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+18
-6
18 additions, 6 deletions
.gitlab-ci.yml
with
18 additions
and
6 deletions
.gitlab-ci.yml
+
18
−
6
View file @
ac0ab640
image
:
golang:1.10.3-stretch
image
:
name
:
golang:1.10.3-stretch
entrypoint
:
[
"
/bin/sh"
,
"
-c"
]
# The problem is that to be able to use go get, one needs to put
# The problem is that to be able to use go get, one needs to put
# the repository in the $GOPATH. So for example if your gitlab domain
# the repository in the $GOPATH. So for example if your gitlab domain
...
@@ -43,7 +45,9 @@
...
@@ -43,7 +45,9 @@
# For this you need to set `S3_ACCESS_KEY` and `S3_SECRET_KEY` in your GitLab project CI's secret variables
# For this you need to set `S3_ACCESS_KEY` and `S3_SECRET_KEY` in your GitLab project CI's secret variables
#release_upload:
#release_upload:
# stage: release
# stage: release
# image: minio/mc
# image:
# name: minio/mc
# entrypoint: ["/bin/sh", "-c"]
# script:
# script:
# - echo "=> We already have artifact sotrage in GitLab! This is for demonstational purposes only."
# - echo "=> We already have artifact sotrage in GitLab! This is for demonstational purposes only."
# - mc config host add edenmalmoe https://s3.edenmal.net ${ACCESS_KEY} ${SECRET_KEY} S3v4
# - mc config host add edenmalmoe https://s3.edenmal.net ${ACCESS_KEY} ${SECRET_KEY} S3v4
...
@@ -53,7 +57,9 @@
...
@@ -53,7 +57,9 @@
image_build
:
image_build
:
stage
:
release
stage
:
release
image
:
docker:latest
image
:
name
:
docker:latest
entrypoint
:
[
"
/bin/sh"
,
"
-c"
]
variables
:
variables
:
DOCKER_HOST
:
tcp://localhost:2375
DOCKER_HOST
:
tcp://localhost:2375
services
:
services
:
...
@@ -67,7 +73,9 @@
...
@@ -67,7 +73,9 @@
-
docker push "${CI_REGISTRY_IMAGE}:${CI_COMMIT_REF_NAME}"
-
docker push "${CI_REGISTRY_IMAGE}:${CI_COMMIT_REF_NAME}"
deploy_review
:
deploy_review
:
image
:
lachlanevenson/k8s-kubectl:latest
image
:
name
:
lachlanevenson/k8s-kubectl:latest
entrypoint
:
[
"
/bin/sh"
,
"
-c"
]
stage
:
review
stage
:
review
only
:
only
:
-
branches
-
branches
...
@@ -95,7 +103,9 @@
...
@@ -95,7 +103,9 @@
-
kubectl get all,ing -l ref=${CI_ENVIRONMENT_SLUG}
-
kubectl get all,ing -l ref=${CI_ENVIRONMENT_SLUG}
stop_review
:
stop_review
:
image
:
lachlanevenson/k8s-kubectl:latest
image
:
name
:
lachlanevenson/k8s-kubectl:latest
entrypoint
:
[
"
/bin/sh"
,
"
-c"
]
stage
:
review
stage
:
review
variables
:
variables
:
GIT_STRATEGY
:
none
GIT_STRATEGY
:
none
...
@@ -114,7 +124,9 @@
...
@@ -114,7 +124,9 @@
-
kubectl delete all -l ref=${CI_ENVIRONMENT_SLUG}
-
kubectl delete all -l ref=${CI_ENVIRONMENT_SLUG}
deploy_live
:
deploy_live
:
image
:
lachlanevenson/k8s-kubectl:latest
image
:
name
:
lachlanevenson/k8s-kubectl:latest
entrypoint
:
[
"
/bin/sh"
,
"
-c"
]
stage
:
deploy
stage
:
deploy
environment
:
environment
:
name
:
live
name
:
live
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
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!
Save comment
Cancel
Please
register
or
sign in
to comment