[sysadmin/ci-tooling] pipeline-templates: Run tests before installing for the XenialQt5.7 platform.
Ben Cooksley
null at kde.org
Sat Aug 19 00:21:27 UTC 2017
Git commit 6d857f92b06fe96fbbebeb9e62b1a02055ef0707 by Ben Cooksley.
Committed on 19/08/2017 at 00:21.
Pushed by bcooksley into branch 'master'.
Run tests before installing for the XenialQt5.7 platform.
This is driven by Frameworks. With few exceptions, only Frameworks uses XenialQt5.7 so this shouldn't affect anyone else.
CCMAIL: kde-frameworks-devel at kde.org
T +182 -1 pipeline-templates/FedoraQt5.8.template
M +1 -1 pipeline-templates/SUSEQt5.9.template
M +1 -1 pipeline-templates/XenialQt4.template
M +10 -10 pipeline-templates/XenialQt5.7.template
https://commits.kde.org/sysadmin/ci-tooling/6d857f92b06fe96fbbebeb9e62b1a02055ef0707
diff --git a/pipeline-templates/FedoraQt5.8.template b/pipeline-templates/FedoraQt5.8.template
deleted file mode 120000
index d8a080b..0000000
--- a/pipeline-templates/FedoraQt5.8.template
+++ /dev/null
@@ -1 +0,0 @@
-XenialQt5.7.template
\ No newline at end of file
diff --git a/pipeline-templates/FedoraQt5.8.template b/pipeline-templates/FedoraQt5.8.template
new file mode 100644
index 0000000..b8ba09a
--- /dev/null
+++ b/pipeline-templates/FedoraQt5.8.template
@@ -0,0 +1,182 @@
+// Provisionally mark the build as successful
+currentBuild.result = 'SUCCESS'
+
+// Request a node to be allocated to us
+node( currentPlatform ) {
+// We want Timestamps on everything
+timestamps {
+ // We want to catch any errors that occur to allow us to send out notifications (ie. emails) if needed
+ catchError {
+ // First Thing: Checkout Sources
+ stage('Checkout Sources') {
+
+ // Actual Application Sources
+ checkout changelog: true, poll: true, scm: [
+ $class: 'GitSCM',
+ branches: [[name: branchToBuild]],
+ browser: [$class: 'CGit', repoUrl: browserUrl],
+ extensions: [[$class: 'CloneOption', timeout: 120]],
+ userRemoteConfigs: [[url: repositoryUrl]]
+ ]
+
+ // Our CI scripts
+ checkout changelog: false, poll: false, scm: [
+ $class: 'GitSCM',
+ branches: [[name: 'master']],
+ extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'ci-tooling/']],
+ userRemoteConfigs: [[url: 'https://anongit.kde.org/sysadmin/ci-tooling']]
+ ]
+
+ // Projects metadata and next generation dependency metadata
+ checkout changelog: false, poll: false, scm: [
+ $class: 'GitSCM',
+ branches: [[name: 'master']],
+ extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'ci-tooling/repo-metadata/']],
+ userRemoteConfigs: [[url: 'https://anongit.kde.org/sysadmin/repo-metadata']]
+ ]
+
+ // Dependency Metadata
+ checkout changelog: false, poll: false, scm: [
+ $class: 'GitSCM',
+ branches: [[name: 'master']],
+ extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'ci-tooling/kde-build-metadata/']],
+ userRemoteConfigs: [[url: 'https://anongit.kde.org/kde-build-metadata']]
+ ]
+
+ // KApiDox: For api.kde.org metadata extraction
+ checkout changelog: false, poll: false, scm: [
+ $class: 'GitSCM',
+ branches: [[name: 'master']],
+ extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'ci-tooling/kapidox/']],
+ userRemoteConfigs: [[url: 'https://anongit.kde.org/kapidox']]
+ ]
+
+ // kde-dev-scripts: For packager metadata extraction
+ checkout changelog: false, poll: false, scm: [
+ $class: 'GitSCM',
+ branches: [[name: 'master']],
+ extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'ci-tooling/kde-dev-scripts/']],
+ userRemoteConfigs: [[url: 'https://anongit.kde.org/kde-dev-scripts']]
+ ]
+
+ }
+
+ // Now Prepare to Build: Get the dependencies ready
+ stage('Setup Dependencies') {
+ // Now we can determine what our dependencies are
+ // Then update to the latest version of the dependencies available from the master server
+ // Finally extract all of those dependencies in turn into the given 'installTo' directory
+ sh "python3 -u ci-tooling/helpers/prepare-dependencies.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --installTo '$HOME/install-prefix/'"
+ }
+
+ // Now we can configure our build
+ stage('Configuring Build') {
+ // This is delegated through a helper script to handle minor special cases like inSourceBuilds, non-CMake build systems, etc
+ sh "python3 -u ci-tooling/helpers/configure-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo '$HOME/install-prefix/'"
+ }
+
+ // Finally we can build it! (Once again, through a helper)
+ stage('Compiling') {
+ // We use a helper here so we can determine the appropriate number of CPUs (-j) to build with
+ sh "python3 -u ci-tooling/helpers/compile-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/'"
+ }
+
+ // Now ensure that it installs....
+ stage('Installing') {
+ // The helper ensures that DESTDIR and INSTALL_ROOT are set to 'divertTo'
+ // This allows us to capture the install at the next stage for later reuse in the Setup Dependencies step
+ sh "python3 -u ci-tooling/helpers/install-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo '$HOME/install-prefix/' --divertTo '$WORKSPACE/install-divert/'"
+ }
+
+ // Looks like it built okay - let's capture this for later use
+ // We'll also take the opportunity to extract metadata from CMake used by packagers and api.kde.org
+ stage('Capturing Installation') {
+ // First we create a tar archive of the installation which was diverted
+ // Then we upload a copy of that to the master server and have it publish the new archive
+ // Finally to save bandwidth our copy of the tar archive is moved to our local cache for reuse on later builds on this node
+ sh "python3 -u ci-tooling/helpers/capture-install.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --divertedTo '$WORKSPACE/install-divert/' --installedTo '$HOME/install-prefix/'"
+
+ // Now we extract the CMake metadata and upload that to the appropriate hosts
+ //sh "python3 -u ci-tooling/helpers/extract-cmake-dependency-metadata.py --project ${projectName} --branchGroup ${branchGroup} --usingInstall '$HOME/install-prefix/'"
+ sh "python3 -u ci-tooling/helpers/generate-dependency-diagram-data.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --usingInstall '$HOME/install-prefix/'"
+ }
+
+ // Now we can run our tests
+ stage('Running Tests') {
+ // Run the unit tests for this project
+ // Tests are run in a basic environment (X, DBus)
+ sh "python3 -u ci-tooling/helpers/run-tests.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/'"
+
+ // Collect our results
+ junit allowEmptyResults: true, testResults: 'JUnitTestResults.xml'
+ }
+
+ // Final thing to do: some code quality checks
+ stage('Checking Code Quality') {
+
+ // Perform Appstream Compliance Checks
+ sh "python3 -u ci-tooling/helpers/check-appstream-compliance.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/' --withDiverted '$WORKSPACE/install-divert/'"
+
+ // cppcheck is not supported by Pipeline at the moment, so we don't run that for now
+ // See https://issues.jenkins-ci.org/browse/JENKINS-35096
+
+ // Perform Cobertura Processing
+ // First, run the LCov extraction
+ sh "python3 -u ci-tooling/helpers/extract-lcov-results.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform}"
+
+ // Collect the results from the LCov extraction
+ step([
+ $class: 'CoberturaPublisher',
+ autoUpdateHealth: false, autoUpdateStability: false,
+ coberturaReportFile: 'CoberturaLcovResults.xml',
+ failNoReports: false, failUnhealthy: false, failUnstable: false,
+ maxNumberOfBuilds: 0,
+ onlyStable: false,
+ zoomCoverageChart: false
+ ])
+
+ // Scan the logs and publish a warnings report
+ warnings consoleParsers: [[parserName: 'GNU Make + GNU C Compiler (gcc)'], [parserName: 'Appstreamercli']], excludePattern: "/tmp/**"
+
+ }
+
+ }
+
+ // The build has been completed now - it either succeeded, is unstable, or failed
+ // These parts aren't run within a stage as they're purely administrative and their output will be minimal if any exists
+ // First, do we need to capture a copy of the Workspace? We do this if it was unstable or failed
+ // This is to allow developers to examine what happened more easily
+ if( currentBuild.result == 'FAILURE' || currentBuild.result == 'UNSTABLE' ) {
+ // Capture the workspace
+ sh "python3 -u ci-tooling/helpers/capture-workspace.py --environment ${ciEnvironment}"
+ }
+
+ // Let's determine if we need to send out notifications
+ // What happened in our previous build?
+ def previousResult = currentBuild.previousBuild?.result
+ // If our condition has changed, is FAILURE or UNSTABLE then we want to send an email
+ if( previousResult != currentBuild.result || currentBuild.result == 'FAILURE' || currentBuild.result == 'UNSTABLE' ) {
+ // Construct the list of our recipients - starting with the ones requested as part of our job
+ def mailTo = [ emailRecipients ]
+ // If someone kicked this job off, they're presumably interested as well
+ mailTo << emailextrecipients( [[$class: 'RequesterRecipientProvider']] )
+ // Finalise the list of recipients
+ mailTo = mailTo.join(',')
+
+ // Send the email now
+ emailext(
+ to: mailTo,
+ body: '${JELLY_SCRIPT,template="html_gmail"}',
+ mimeType: 'text/html',
+ subject: 'KDE CI: ${PROJECT_NAME} - Build # ${BUILD_NUMBER} - ${BUILD_STATUS}!',
+ attachLog: true
+ )
+ }
+
+ // IRC Notifications are currently not supported by Pipeline
+ // See https://issues.jenkins-ci.org/browse/JENKINS-33922
+ // We can probably workaround this using Pursuivant and the emails Jenkins sends out
+ // This would allow subscribing to build notifications for IRC channels in much the same way one subscribes for Commits and Bugzilla changes
+
+}
+}
diff --git a/pipeline-templates/SUSEQt5.9.template b/pipeline-templates/SUSEQt5.9.template
index d8a080b..e9e2176 120000
--- a/pipeline-templates/SUSEQt5.9.template
+++ b/pipeline-templates/SUSEQt5.9.template
@@ -1 +1 @@
-XenialQt5.7.template
\ No newline at end of file
+FedoraQt5.8.template
\ No newline at end of file
diff --git a/pipeline-templates/XenialQt4.template b/pipeline-templates/XenialQt4.template
index d8a080b..e9e2176 120000
--- a/pipeline-templates/XenialQt4.template
+++ b/pipeline-templates/XenialQt4.template
@@ -1 +1 @@
-XenialQt5.7.template
\ No newline at end of file
+FedoraQt5.8.template
\ No newline at end of file
diff --git a/pipeline-templates/XenialQt5.7.template b/pipeline-templates/XenialQt5.7.template
index b8ba09a..ef8cf90 100644
--- a/pipeline-templates/XenialQt5.7.template
+++ b/pipeline-templates/XenialQt5.7.template
@@ -81,6 +81,16 @@ timestamps {
sh "python3 -u ci-tooling/helpers/compile-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/'"
}
+ // Now we can run our tests
+ stage('Running Tests') {
+ // Run the unit tests for this project
+ // Tests are run in a basic environment (X, DBus)
+ sh "python3 -u ci-tooling/helpers/run-tests.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/'"
+
+ // Collect our results
+ junit allowEmptyResults: true, testResults: 'JUnitTestResults.xml'
+ }
+
// Now ensure that it installs....
stage('Installing') {
// The helper ensures that DESTDIR and INSTALL_ROOT are set to 'divertTo'
@@ -101,16 +111,6 @@ timestamps {
sh "python3 -u ci-tooling/helpers/generate-dependency-diagram-data.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --usingInstall '$HOME/install-prefix/'"
}
- // Now we can run our tests
- stage('Running Tests') {
- // Run the unit tests for this project
- // Tests are run in a basic environment (X, DBus)
- sh "python3 -u ci-tooling/helpers/run-tests.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall '$HOME/install-prefix/'"
-
- // Collect our results
- junit allowEmptyResults: true, testResults: 'JUnitTestResults.xml'
- }
-
// Final thing to do: some code quality checks
stage('Checking Code Quality') {
More information about the Kde-frameworks-devel
mailing list