Commit 6b64fd0d authored by Ben Cooksley's avatar Ben Cooksley

Start preparation for the jump to Qt 5.11 on Windows

parent 74546008
......@@ -2,22 +2,30 @@
node( "Windows Builder 1" ) {
// We want Timestamps on everything
timestamps {
// We assume someone has gone in advance and done the initial setup of CraftMaster
// As this is a setup deployment, we operate from C:\CM
// First things first though, updating our copies of craftmaster and ci-tooling
stage('Update Tooling') {
// First things first, grab the Craft management tooling, and update our Craft checkouts
stage('Preparing Craft') {
// Make sure we start with a clean slate
deleteDir()
// Grab our tooling which we will need in a few moments
checkout changelog: false, poll: false, scm: [
$class: 'GitSCM',
branches: [[name: 'master']],
extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'bf-tooling/']],
userRemoteConfigs: [[url: 'https://anongit.kde.org/sysadmin/binary-factory-tooling']]
]
// Make sure that Craftmaster and the CI Tooling is up to date
bat """
cd C:\\Craft\\CI\\craftmaster\\
git pull
cd C:\\Craft\\CI\\ci-tooling\\
git pull
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/craftmaster --into "C:/Craft/CI2/" --branch stable
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/sysadmin/ci-tooling --into "C:/Craft/CI2/" --branch master
"""
}
// Now that is done, it's time to rebuild the Craft Cache!
stage('Update Craft Setup') {
bat """
cd C:\\Craft\\CI\\craftmaster\\
cd C:\\Craft\\CI2\\craftmaster\\
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c -i --no-cache craft
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c --list-file ../ci-tooling/craftmaster/packages.list
"""
......@@ -25,26 +33,34 @@ node( "Windows Builder 1" ) {
}
}
// Then Builder 2....
// Then we'll update Builder 2
node( "Windows Builder 2" ) {
// We want Timestamps on everything
timestamps {
// We assume someone has gone in advance and done the initial setup of CraftMaster
// As this is a setup deployment, we operate from C:\CM
// First things first though, updating our copies of craftmaster and ci-tooling
stage('Update Tooling') {
// First things first, grab the Craft management tooling, and update our Craft checkouts
stage('Preparing Craft') {
// Make sure we start with a clean slate
deleteDir()
// Grab our tooling which we will need in a few moments
checkout changelog: false, poll: false, scm: [
$class: 'GitSCM',
branches: [[name: 'master']],
extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'bf-tooling/']],
userRemoteConfigs: [[url: 'https://anongit.kde.org/sysadmin/binary-factory-tooling']]
]
// Make sure that Craftmaster and the CI Tooling is up to date
bat """
cd C:\\Craft\\CI\\craftmaster\\
git pull
cd C:\\Craft\\CI\\ci-tooling\\
git pull
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/craftmaster --into "C:/Craft/CI2/" --branch stable
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/sysadmin/ci-tooling --into "C:/Craft/CI2/" --branch master
"""
}
// Now that is done, it's time to rebuild the Craft Cache!
stage('Update Craft Setup') {
bat """
cd C:\\Craft\\CI\\craftmaster\\
cd C:\\Craft\\CI2\\craftmaster\\
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c -i --no-cache craft
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c --list-file ../ci-tooling/craftmaster/packages.list
"""
......@@ -52,26 +68,34 @@ node( "Windows Builder 2" ) {
}
}
// Then Builder 3!
// Finally we'll update Builder 3
node( "Windows Builder 3" ) {
// We want Timestamps on everything
timestamps {
// We assume someone has gone in advance and done the initial setup of CraftMaster
// As this is a setup deployment, we operate from C:\CM
// First things first though, updating our copies of craftmaster and ci-tooling
stage('Update Tooling') {
// First things first, grab the Craft management tooling, and update our Craft checkouts
stage('Preparing Craft') {
// Make sure we start with a clean slate
deleteDir()
// Grab our tooling which we will need in a few moments
checkout changelog: false, poll: false, scm: [
$class: 'GitSCM',
branches: [[name: 'master']],
extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'bf-tooling/']],
userRemoteConfigs: [[url: 'https://anongit.kde.org/sysadmin/binary-factory-tooling']]
]
// Make sure that Craftmaster and the CI Tooling is up to date
bat """
cd C:\\Craft\\CI\\craftmaster\\
git pull
cd C:\\Craft\\CI\\ci-tooling\\
git pull
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/craftmaster --into "C:/Craft/CI2/" --branch stable
python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository git://anongit.kde.org/sysadmin/ci-tooling --into "C:/Craft/CI2/" --branch master
"""
}
// Now that is done, it's time to rebuild the Craft Cache!
stage('Update Craft Setup') {
bat """
cd C:\\Craft\\CI\\craftmaster\\
cd C:\\Craft\\CI2\\craftmaster\\
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c -i --no-cache craft
python Craftmaster.py --config config/CraftBinaryCache.ini --target=windows-msvc2017_64-cl-debug -c --list-file ../ci-tooling/craftmaster/packages.list
"""
......
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