The alpha, beta, and stable channels do not match the rook release process. Each storage provider defines their own stability based on the CRDs rather than defining it with the release process. Rook really only has two release streams: master and the official releases. Master is published with each merge, while releases go through a signoff process to ensure quality. Thus, the alpha, beta, and stable channels are removed and replaced with a single release channel. Signed-off-by: travisn <tnielsen@redhat.com>
36 lines
1.0 KiB
Plaintext
36 lines
1.0 KiB
Plaintext
// Rook build for Jenkins Pipelines
|
|
|
|
pipeline {
|
|
agent { label 'ec2-stateful' }
|
|
|
|
options {
|
|
disableConcurrentBuilds()
|
|
timestamps()
|
|
}
|
|
|
|
parameters {
|
|
string(name: 'version', defaultValue: '', description: 'The version you are releasing, for example, v1.0.0')
|
|
string(name: 'channel', defaultValue: 'release', description: 'Only the release channel is supported.')
|
|
}
|
|
|
|
stages {
|
|
stage('Promote Release') {
|
|
environment {
|
|
DOCKER = credentials('rook-docker-hub')
|
|
AWS = credentials('rook-jenkins-aws')
|
|
}
|
|
steps {
|
|
sh 'docker login -u="${DOCKER_USR}" -p="${DOCKER_PSW}"'
|
|
sh "build/run make -j\$(nproc) -C build/release promote BRANCH_NAME=${BRANCH_NAME} VERSION=${params.version} CHANNEL=${params.channel} AWS_ACCESS_KEY_ID=${AWS_USR} AWS_SECRET_ACCESS_KEY=${AWS_PSW}"
|
|
}
|
|
}
|
|
}
|
|
|
|
post {
|
|
always {
|
|
sh 'make -j\$(nproc) -C build/release clean'
|
|
deleteDir()
|
|
}
|
|
}
|
|
}
|