vbatts/ruby-ex
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Use the new rollout command instead of deploy

Browse source
This commit is contained in:
Ovidio Mallo 2016-12-07 21:31:01 +01:00
parent bfb46e557f
commit 832da546e2
2 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
deployment/config/app.yaml
View file

@ -28,7 +28,7 @@ objects:
triggers:
- type: ImageChange
imageChangeParams:
automatic: true
automatic: false
containerNames:
- ${APP}
from:

6
deployment/pipeline.groovy
View file

@ -12,7 +12,8 @@ node() {
stage('Deploy to DEV') {
sh "${ocCmd} process -f ${appConfigUrl} -v ENV=dev -n rubex-dev | ${ocCmd} apply -f - -n rubex-dev"
sh "${ocCmd} tag rubex-dev/frontend:latest rubex-dev/frontend:dev"
sh "${ocCmd} deploy frontend --follow -n rubex-dev"
sh "${ocCmd} rollout latest dc/frontend -n rubex-dev"
sh "${ocCmd} rollout status dc/frontend -n rubex-dev"
}
def isPromoteToTest = false
@ -24,7 +25,8 @@ node() {
stage('Deploy to TEST') {
sh "${ocCmd} process -f ${appConfigUrl} -v ENV=test -n rubex-test | ${ocCmd} apply -f - -n rubex-test"
sh "${ocCmd} tag rubex-dev/frontend:dev rubex-dev/frontend:test"
sh "${ocCmd} deploy frontend --follow -n rubex-test"
sh "${ocCmd} rollout latest dc/frontend -n rubex-test"
sh "${ocCmd} rollout status dc/frontend -n rubex-test"
}
}
}