Skip to content

GitLab

C
CI Tooling
Commit aaad13e6 authored by Ben Cooksley's avatar Ben Cooksley
Browse files
Options

Eliminate Windows on Qt 5.13 builds - replacing them with Qt 5.14 ones instead

parent adc38b75
Pipeline #13449 skipped with stage
    Hide whitespace changes
    Inline Side-by-side
    Showing with 6 additions and 514 deletions
    archive-configs/production.yaml
    View file @ aaad13e6
    ......@@ -9,7 +9,6 @@ server:
    archiveDirectory: "/srv/production/"
    cacheLocation:
    WindowsMSVCQt5.13: "C:\\CI\\archives\\WindowsMSVCQt5.13\\"
    WindowsMSVCQt5.14: "C:\\CI\\archives\\WindowsMSVCQt5.14\\"
    SUSEQt5.12: "/srv/archives/production/SUSEQt5.12/"
    SUSEQt5.13: "/srv/archives/production/SUSEQt5.13/"
    ......
    archive-configs/sandbox.yaml
    View file @ aaad13e6
    ......@@ -9,7 +9,7 @@ server:
    archiveDirectory: "/srv/sandbox/"
    cacheLocation:
    WindowsMSVCQt5.13: "C:\\CI\\sandbox-archives\\WindowsMSVCQt5.13\\"
    WindowsMSVCQt5.14: "C:\\CI\\sandbox-archives\\WindowsMSVCQt5.14\\"
    SUSEQt5.12: "/srv/archives/sandbox/SUSEQt5.12/"
    SUSEQt5.13: "/srv/archives/sandbox/SUSEQt5.13/"
    FreeBSDQt5.13: "/usr/home/jenkins/archives/sandbox/"
    ......
    build-specs/Frameworks/kio-WindowsMSVCQt5.13.yaml deleted 100644 → 0
    View file @ adc38b75
    kf5-qt5:
    run-tests: False
    stable-kf5-qt5:
    run-tests: False
    build-specs/KDevelop/kdev-python-WindowsMSVCQt5.13.yaml deleted 100644 → 0
    View file @ adc38b75
    "kf5-qt5":
    "cmake-options": '-DPYTHON_EXECUTABLE="C:/Program Files/Python36-32/python.exe"'
    "per-test-timeout": 60
    "stable-kf5-qt5":
    "cmake-options": '-DPYTHON_EXECUTABLE="C:/Program Files/Python36-32/python.exe"'
    "per-test-timeout": 60
    build-specs/KDevelop/kdevelop-WindowsMSVCQt5.13.yaml deleted 100644 → 0
    View file @ adc38b75
    "kf5-qt5":
    "per-test-timeout": 60
    "stable-kf5-qt5":
    "per-test-timeout": 60
    helpers/check-platform.py
    View file @ aaad13e6
    ......@@ -14,7 +14,6 @@ allPlatforms = {
    'SUSEQt5.12': 'Linux',
    'SUSEQt5.13': 'Linux',
    'FreeBSDQt5.13': 'FreeBSD',
    'WindowsMSVCQt5.13': 'Windows',
    'WindowsMSVCQt5.14': 'Windows',
    None: 'MacOSX',
    'AndroidQt5.13': 'Android'
    ......
    local-metadata/product-definitions.yaml
    View file @ aaad13e6
    ......@@ -5,7 +5,7 @@
    platforms:
    - "SUSEQt5.12"
    - "SUSEQt5.13"
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    - "FreeBSDQt5.13"
    - repositories:
    - "frameworks/extra-cmake-modules"
    ......@@ -57,7 +57,7 @@
    - repositories:
    - "kde/workspace/drkonqi"
    platforms:
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    branchGroups:
    - "kf5-qt5"
    - "stable-kf5-qt5"
    ......@@ -115,7 +115,7 @@
    - 'kde/pim/kcontacts'
    - "kde/pim/kpimtextedit"
    platforms:
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    - repositories:
    - "kde/kdemultimedia/elisa"
    platforms:
    ......@@ -222,7 +222,6 @@
    - "playground/network/ruqola"
    platforms:
    - "SUSEQt5.12"
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    - "FreeBSDQt5.13"
    - repositories:
    ......@@ -275,7 +274,7 @@
    platforms:
    - "SUSEQt5.12"
    - "FreeBSDQt5.13"
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    branchGroups:
    - "kf5-qt5"
    - "stable-kf5-qt5"
    ......@@ -291,7 +290,7 @@
    platforms:
    - "SUSEQt5.12"
    - "FreeBSDQt5.13"
    - "WindowsMSVCQt5.13"
    - "WindowsMSVCQt5.14"
    - repositories:
    - "calligra/calligra"
    - "calligra/calligraplan"
    ......
    local-metadata/project-ignore-rules.yaml
    View file @ aaad13e6
    ......@@ -4,22 +4,6 @@
    'SUSEQt5.13':
    - 'kdesupport/qca'
    'WindowsMSVCQt5.13':
    - 'kdesupport/polkit-qt-1'
    - 'kdesupport/qca'
    - 'frameworks/networkmanager-qt'
    - 'frameworks/modemmanager-qt'
    - 'frameworks/bluez-qt'
    - 'frameworks/prison'
    - 'frameworks/kdesu'
    - 'frameworks/kpty'
    - 'frameworks/kwayland'
    - 'frameworks/kactivities-stats'
    - 'kde/workspace/libksysguard'
    - 'kde/kdeedu/marble'
    - 'kde/kdenetwork/kaccounts-integration'
    - 'extragear/libs/pulseaudio-qt'
    'WindowsMSVCQt5.14':
    - 'kdesupport/polkit-qt-1'
    - 'kdesupport/qca'
    ......
    pipeline-templates/Frameworks/WindowsMSVCQt5.13.template deleted 100644 → 0
    View file @ adc38b75
    // 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') {
    // Make sure we have a clean slate to begin with
    deleteDir()
    // This includes any potential install directory
    bat """
    if exist "C:\\CI\\Software Installs\\${projectName}" rmdir /s /q "C:\\CI\\Software Installs\\${projectName}"
    """
    // 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']]
    ]
    }
    // 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
    bat """
    python -u ci-tooling/helpers/prepare-dependencies.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/configure-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/compile-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/install-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/" --divertTo "%WORKSPACE%/install-divert/"
    """
    }
    // 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)
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/run-tests.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall "C:/CI/Software Installs/${projectName}/"
    """
    // Collect our results
    junit allowEmptyResults: true, testResults: 'JUnitTestResults.xml'
    }
    // 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
    bat """
    python -u ci-tooling/helpers/capture-install.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --divertedTo "%WORKSPACE%/install-divert/" --installedTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // Final thing to do: some code quality checks
    stage('Checking Code Quality') {
    // 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
    // Cobertura doesn't support Pipeline either, so no code coverage publishing...
    // See https://issues.jenkins-ci.org/browse/JENKINS-30700
    // Scan the logs and publish a warnings report
    warnings consoleParsers: [[parserName: 'MSBuild']], excludePattern: '(C|c):/(Program Files \\(x86\\)|program files \\(x86\\)|Craft|craft)/.*'
    }
    }
    // 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 or is FAILURE then we want to send an email
    if( previousResult != currentBuild.result || currentBuild.result == 'FAILURE' ) {
    // Start constructing the list of our recipients
    // At this point we can only be either a failure or an unstable build, so notify those who have requested unstable build notifications
    def mailTo = [ unstableBuildEmails ]
    // If the build was a solid failure (either now or previously) then notify those who want to know about failures only
    if( previousResult == 'FAILURE' || currentBuild.result == 'FAILURE' ) {
    // Add them to the list
    mailTo << buildFailureEmails
    }
    // If someone kicked this job off, they're presumably interested as well
    mailTo << emailextrecipients( [[$class: 'RequesterRecipientProvider']] )
    // We always want to notify our dashboard as well
    mailTo << "kde-dashboard@kde.org"
    // 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: false
    )
    }
    // 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
    // As the Windows Slaves are permanent ones, we erase the Workspace as the last thing we do
    deleteDir()
    // Cleanup the installation directory too
    bat """
    if exist "C:\\CI\\Software Installs\\${projectName}" rmdir /s /q "C:\\CI\\Software Installs\\${projectName}"
    """
    }
    }
    pipeline-templates/WindowsMSVCQt5.13.template deleted 100644 → 0
    View file @ adc38b75
    // 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') {
    // Make sure we have a clean slate to begin with
    deleteDir()
    // This includes any potential install directory
    bat """
    if exist "C:\\CI\\Software Installs\\${projectName}" rmdir /s /q "C:\\CI\\Software Installs\\${projectName}"
    """
    // 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']]
    ]
    }
    // 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
    bat """
    python -u ci-tooling/helpers/prepare-dependencies.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/configure-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/compile-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/install-build.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/${projectName}/" --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
    bat """
    python -u ci-tooling/helpers/capture-install.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --divertedTo "%WORKSPACE%/install-divert/" --installedTo "C:/CI/Software Installs/${projectName}/"
    """
    }
    // 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)
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/run-tests.py --product ${productName} --project ${projectName} --branchGroup ${branchGroup} --platform ${currentPlatform} --usingInstall "C:/CI/Software Installs/${projectName}/"
    """
    // Collect our results
    junit allowEmptyResults: true, testResults: 'JUnitTestResults.xml'
    }
    // Final thing to do: some code quality checks
    stage('Checking Code Quality') {
    // 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
    // Cobertura doesn't support Pipeline either, so no code coverage publishing...
    // See https://issues.jenkins-ci.org/browse/JENKINS-30700
    // Scan the logs and publish a warnings report
    warnings consoleParsers: [[parserName: 'MSBuild']], excludePattern: '(C|c):/(Program Files \\(x86\\)|program files \\(x86\\)|Craft|craft)/.*'
    }
    }
    // 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 or is FAILURE then we want to send an email
    if( previousResult != currentBuild.result || currentBuild.result == 'FAILURE' ) {
    // Start constructing the list of our recipients
    // At this point we can only be either a failure or an unstable build, so notify those who have requested unstable build notifications
    def mailTo = [ unstableBuildEmails ]
    // If the build was a solid failure (either now or previously) then notify those who want to know about failures only
    if( previousResult == 'FAILURE' || currentBuild.result == 'FAILURE' ) {
    // Add them to the list
    mailTo << buildFailureEmails
    }
    // If someone kicked this job off, they're presumably interested as well
    mailTo << emailextrecipients( [[$class: 'RequesterRecipientProvider']] )
    // We always want to notify our dashboard as well
    mailTo << "kde-dashboard@kde.org"
    // 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: false
    )
    }
    // 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
    // As the Windows Slaves are permanent ones, we erase the Workspace as the last thing we do
    deleteDir()
    // Cleanup the installation directory too
    bat """
    if exist "C:\\CI\\Software Installs\\${projectName}" rmdir /s /q "C:\\CI\\Software Installs\\${projectName}"
    """
    }
    }
    pipeline-templates/dependency-build/WindowsMSVCQt5.13.template deleted 100644 → 0
    View file @ adc38b75
    // Request a node to be allocated to us
    node( currentPlatform ) {
    // We want Timestamps on everything
    timestamps {
    // For Windows we need to help keep the path short otherwise builds might trip up due to path length limitation
    // This isn't a concern for most jobs, but the Dependency Build jobs get bitten by this quite badly due to $BASEDIR/Administration/Dependency Build....
    ws('C:/CI/DepBuild/') {
    // 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') {
    // Make sure we have a clean slate to begin with
    deleteDir()
    // This includes any potential install directory
    bat """
    if exist "C:\\CI\\Software Installs\\Dependencies" rmdir /s /q "C:\\CI\\Software Installs\\Dependencies"
    """
    // 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']]
    ]
    }
    // Now we can build the dependencies of this product
    stage('Build Product Dependencies') {
    // This script will do the following:
    // 1) Determine what is in this Product
    // 2) Determine what those repositories depend on
    // 3) Determine what dependencies are outside of this Product
    // 4) Sort those dependencies into an appropriate order to build them
    // 5) Checkout, Configure, Compile, Install and Capture the Installation each of those dependencies in turn
    // We can't do this as Pipeline steps unfortunately (at least not easily)
    // Tests and Other Quality Tests won't be run during this process
    // The results of this process are only intended to be used as part of the base of this Product, so don't need testing
    bat """
    call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Auxiliary/Build/vcvars64.bat" -vcvars_ver=14.16
    set CRAFT_ROOT=C:/Craft/CI-Qt513/windows-msvc2017_64-cl-debug/
    python -u ci-tooling/helpers/build-product-dependencies.py --product ${productName} --branchGroup ${branchGroup} --environment ${ciEnvironment} --platform ${currentPlatform} --installTo "C:/CI/Software Installs/Dependencies/"
    """
    }
    }
    // As the Windows Slaves are permanent ones, we erase the Workspace as the last thing we do
    deleteDir()
    // This includes any potential install directory
    bat """
    if exist "C:\\CI\\Software Installs\\Dependencies" rmdir /s /q "C:\\CI\\Software Installs\\Dependencies"
    """
    // 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 - these people always want to be notified about Dependency Build jobs
    def mailTo = []
    // 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: false
    )
    }
    }
    }
    }
    Markdown is supported
    0% or .
    You are about to add 0 people to the discussion. Proceed with caution.
    Finish editing this message first!
    Please register or to comment