Use the new rollout command instead of deploy
This commit is contained in:
parent
bfb46e557f
commit
832da546e2
2 changed files with 5 additions and 3 deletions
|
@ -28,7 +28,7 @@ objects:
|
||||||
triggers:
|
triggers:
|
||||||
- type: ImageChange
|
- type: ImageChange
|
||||||
imageChangeParams:
|
imageChangeParams:
|
||||||
automatic: true
|
automatic: false
|
||||||
containerNames:
|
containerNames:
|
||||||
- ${APP}
|
- ${APP}
|
||||||
from:
|
from:
|
||||||
|
|
|
@ -12,7 +12,8 @@ node() {
|
||||||
stage('Deploy to DEV') {
|
stage('Deploy to DEV') {
|
||||||
sh "${ocCmd} process -f ${appConfigUrl} -v ENV=dev -n rubex-dev | ${ocCmd} apply -f - -n rubex-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} 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
|
def isPromoteToTest = false
|
||||||
|
@ -24,7 +25,8 @@ node() {
|
||||||
stage('Deploy to TEST') {
|
stage('Deploy to TEST') {
|
||||||
sh "${ocCmd} process -f ${appConfigUrl} -v ENV=test -n rubex-test | ${ocCmd} apply -f - -n rubex-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} 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"
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue