debian-forge-composer/jenkins/Jenkinsfile
Major Hayden 08594bd66d 🚽 Use Jenkins pipeline for better flow
By using a small Jenkins pipeline in the repository, we can define
almost all of our testing parameters in the repo itself and not inside
Jenkins.

This also allows us to use the GitHub Branch Source plugin and
auto-discover new repositories without `ok to test` bombs in
pull requests.

Signed-off-by: Major Hayden <major@redhat.com>
2020-05-05 18:33:04 -05:00

84 lines
2.4 KiB
Groovy

pipeline {
agent none
options {
timestamps()
ansiColor('xterm')
}
stages {
stage("Functional Testing") {
parallel {
stage('Fedora 31 base') {
agent {
label "fedora31"
}
environment {
TEST_TYPE = "base"
}
steps {
sh "jenkins/run_tests.sh"
}
}
stage('Fedora 31 image') {
agent {
label "fedora31"
}
environment {
TEST_TYPE = "image"
}
steps {
sh "jenkins/run_tests.sh"
}
}
stage('Fedora 32 base') {
agent {
label "fedora32"
}
environment {
TEST_TYPE = "base"
}
steps {
sh "jenkins/run_tests.sh"
}
}
stage('Fedora 32 image') {
agent {
label "fedora32"
}
environment {
TEST_TYPE = "image"
}
steps {
sh "jenkins/run_tests.sh"
}
}
stage('RHEL 8.2 base') {
agent {
label "rhel82"
}
environment {
TEST_TYPE = "base"
}
steps {
sh "jenkins/run_tests.sh"
}
}
// Disable RHEL 8.3 image testing for now until we work out the
// QEMU issues there.
//
// stage('RHEL 8.2 image') {
// agent {
// label "rhel82"
// }
// environment {
// TEST_TYPE = "image"
// }
// steps {
// sh "jenkins/run_tests.sh"
// }
// }
}
}
}
}