diff --git a/craft-cache/devel-pipelines/linux.pipeline b/craft-cache/devel-pipelines/linux.pipeline index c6cf6ce..5322bbd 100644 --- a/craft-cache/devel-pipelines/linux.pipeline +++ b/craft-cache/devel-pipelines/linux.pipeline @@ -1,55 +1,55 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/master/" // Request a node to be allocated to us node( "Ubuntu1604Craft" ) { // 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 we want to make sure Craft is ready to go stage('Preparing Craft') { // 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go sh """ python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into ~/Craft/BinaryCache/ python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into ~/Craft/BinaryCache/ """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { sh """ cd ~/Craft/BinaryCache/ python3.6 craftmaster/CraftMaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft python3.6 craftmaster/CraftMaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --option "[ContinuousIntegration]ClearBuildFolder=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // And finally, we'll upload it to the master server stage('Publish Craft Cache') { sh """ cd "$WORKSPACE/ci-tooling/" - python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } } diff --git a/craft-cache/devel-pipelines/macos.pipeline b/craft-cache/devel-pipelines/macos.pipeline index a0214b2..774b440 100644 --- a/craft-cache/devel-pipelines/macos.pipeline +++ b/craft-cache/devel-pipelines/macos.pipeline @@ -1,72 +1,72 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/master/" // Request a node to be allocated to us node( "macOS" ) { // 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 we want to make sure Craft is ready to go 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go sh """ /usr/local/bin/python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into ~/Craft/BinaryCache/ /usr/local/bin/python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into ~/Craft/BinaryCache/ """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { sh """ cd ~/Craft/BinaryCache/ /usr/local/bin/python3 craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft /usr/local/bin/python3 craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --option "[ContinuousIntegration]ClearBuildFolder=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // We need to catch errors here to ensure that the cleanup always runs, even if the upload fails // While this is a bit wasteful it at least determines that errors in the publishing process leave a builder with a very full disk! catchError { // And finally, we'll upload it to the master server stage('Publish Craft Cache') { sh """ cd "$WORKSPACE/ci-tooling/" - /usr/local/bin/python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + /usr/local/bin/python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } // Then we can cleanup everything we did stage('Cleaning Up') { sh """ rm -rf ~/Craft/BinaryCache/ """ } // As the macOS Slaves are permanent ones, we erase the Workspace as the last thing we do deleteDir() } } diff --git a/craft-cache/devel-pipelines/windows.pipeline b/craft-cache/devel-pipelines/windows.pipeline index df35696..53782ff 100644 --- a/craft-cache/devel-pipelines/windows.pipeline +++ b/craft-cache/devel-pipelines/windows.pipeline @@ -1,72 +1,72 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/master/" // Request a node to be allocated to us node( "WindowsMSVC" ) { // 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 we want to make sure Craft is ready to go 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go bat """ python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into "C:/Craft/BinaryCache/" python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into "C:/Craft/BinaryCache/" """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { bat """ cd C:/Craft/BinaryCache/ python craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft python craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --option "[ContinuousIntegration]ClearBuildFolder=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // We need to catch errors here to ensure that the cleanup always runs, even if the upload fails // While this is a bit wasteful it at least determines that errors in the publishing process leave a builder with a very full disk! catchError { // Upload it to the master server stage('Publish Craft Cache') { bat """ cd "%WORKSPACE%\\ci-tooling" - python helpers/sftp-directory-mirror.py --source C:/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + python helpers/sftp-directory-mirror.py --source C:/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } // Then we can cleanup everything we did // It is critical this always happens, otherwise builders can run out of disk space! stage('Cleaning Up') { bat """ rmdir /s /q C:\\Craft\\BinaryCache\\ """ } // As the Windows Slaves are permanent ones, we erase the Workspace as the last thing we do deleteDir() } } diff --git a/craft-cache/mingw-for-msvc.pipeline b/craft-cache/mingw-for-msvc.pipeline index e8f03de..ef37e9d 100644 --- a/craft-cache/mingw-for-msvc.pipeline +++ b/craft-cache/mingw-for-msvc.pipeline @@ -1,46 +1,46 @@ // Request a builder node( "WindowsMSVC" ) { // We want Timestamps on everything timestamps { // As this is a cache rebuild, we operate from C:/Craft/MinGWBinariesForMSVC // First things first though, updating our copies of craftmaster and ci-tooling stage('Update Tooling') { powershell ''' $ROOT = "C:/Craft/MinGWBinariesForMSVC/" Write-Host "Setting up things in $ROOT" function git_clone([string] $repo, [string]$checkoutDir) { if (!(test-path -path $ROOT)) { mkdir -p $ROOT } if (test-path -path $ROOT/$checkoutDir/) { cd $ROOT/$checkoutDir/ cmd /C "git pull --rebase 2>&1" } else { cmd /C "git clone $repo $ROOT/$checkoutDir 2>&1" } } git_clone "git://anongit.kde.org/craftmaster.git" "craftmaster" git_clone "git://anongit.kde.org/sysadmin/ci-tooling" "ci-tooling" ''' } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { bat ''' set ROOT="C:/Craft/MinGWBinariesForMSVC/" cd %ROOT% python -u craftmaster/Craftmaster.py --verbose --config craftmaster/config/autotools/autotools.ini ''' } // And finally, we'll upload it to the master server stage('Publish Craft Cache') { bat ''' set ROOT="C:/Craft/MinGWBinariesForMSVC/" cd %ROOT%/ci-tooling/ - python -u helpers/sftp-directory-mirror.py --source %ROOT%/cache/ --destination /srv/archives/files/craft/autotools/ --server racnoss.kde.org --username craft + python -u helpers/sftp-directory-mirror.py --source %ROOT%/cache/ --destination /srv/archives/files/craft/autotools/ --server milonia.kde.org --username craft ''' } } } diff --git a/craft-cache/stable-pipelines/linux.pipeline b/craft-cache/stable-pipelines/linux.pipeline index 1ab1236..843e37c 100644 --- a/craft-cache/stable-pipelines/linux.pipeline +++ b/craft-cache/stable-pipelines/linux.pipeline @@ -1,55 +1,55 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/2018.12/" // Request a node to be allocated to us node( "Ubuntu1604Craft" ) { // 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 we want to make sure Craft is ready to go stage('Preparing Craft') { // 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go sh """ python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into ~/Craft/BinaryCache/ python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into ~/Craft/BinaryCache/ """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { sh """ cd ~/Craft/BinaryCache/ python3.6 craftmaster/CraftMaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft python3.6 craftmaster/CraftMaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // And finally, we'll upload it to the master server stage('Publish Craft Cache') { sh """ cd "$WORKSPACE/ci-tooling/" - python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } } diff --git a/craft-cache/stable-pipelines/macos.pipeline b/craft-cache/stable-pipelines/macos.pipeline index ea625e4..a90a4ce 100644 --- a/craft-cache/stable-pipelines/macos.pipeline +++ b/craft-cache/stable-pipelines/macos.pipeline @@ -1,72 +1,72 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/2018.12/" // Request a node to be allocated to us node( "macOS" ) { // 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 we want to make sure Craft is ready to go 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go sh """ /usr/local/bin/python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into ~/Craft/BinaryCache/ /usr/local/bin/python3 "$WORKSPACE/bf-tooling/craft/checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into ~/Craft/BinaryCache/ """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { sh """ cd ~/Craft/BinaryCache/ /usr/local/bin/python3 craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft /usr/local/bin/python3 craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // We need to catch errors here to ensure that the cleanup always runs, even if the upload fails // While this is a bit wasteful it at least determines that errors in the publishing process leave a builder with a very full disk! catchError { // And finally, we'll upload it to the master server stage('Publish Craft Cache') { sh """ cd "$WORKSPACE/ci-tooling/" - /usr/local/bin/python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + /usr/local/bin/python3 helpers/sftp-directory-mirror.py --source ~/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } // Then we can cleanup everything we did stage('Cleaning Up') { sh """ rm -rf ~/Craft/BinaryCache/ """ } // As the macOS Slaves are permanent ones, we erase the Workspace as the last thing we do deleteDir() } } diff --git a/craft-cache/stable-pipelines/windows.pipeline b/craft-cache/stable-pipelines/windows.pipeline index 2a40bc1..ccc3f56 100644 --- a/craft-cache/stable-pipelines/windows.pipeline +++ b/craft-cache/stable-pipelines/windows.pipeline @@ -1,72 +1,72 @@ // Where will the craftmaster configuration be found (relative to the working directory that is)? def craftmasterConfigDir = "binary-factory-tooling/craft/configs/2018.12/" // Request a node to be allocated to us node( "WindowsMSVC" ) { // 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 we want to make sure Craft is ready to go 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']] ] // We are also reliant on the CI System Tooling for parts of this, so grab it too 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']] ] // Make sure that Craftmaster is ready to go bat """ python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository "git://anongit.kde.org/craftmaster" --into "C:/Craft/BinaryCache/" python "%WORKSPACE%\\bf-tooling\\craft\\checkout-repository.py" --repository "git://anongit.kde.org/sysadmin/binary-factory-tooling" --into "C:/Craft/BinaryCache/" """ } // Now that is done, it's time to rebuild the Craft Cache! stage('Build Craft Cache') { bat """ cd C:/Craft/BinaryCache/ python craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c -i craft python craftmaster/Craftmaster.py --config ${craftmasterConfigDir}/CraftBinaryCache.ini --target ${craftPlatform} --variables CreateCache=True UseCache=True -c --option "/.buildTests=False" --list-file ${craftmasterConfigDir}/BinaryCachePackages.list """ } } // We need to catch errors here to ensure that the cleanup always runs, even if the upload fails // While this is a bit wasteful it at least determines that errors in the publishing process leave a builder with a very full disk! catchError { // Upload it to the master server stage('Publish Craft Cache') { bat """ cd "%WORKSPACE%\\ci-tooling" - python helpers/sftp-directory-mirror.py --source C:/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server racnoss.kde.org --username craft + python helpers/sftp-directory-mirror.py --source C:/Craft/BinaryCache/cache/ --destination /srv/archives/files/craft/master/ --server milonia.kde.org --username craft """ } } // Then we can cleanup everything we did // It is critical this always happens, otherwise builders can run out of disk space! stage('Cleaning Up') { bat """ rmdir /s /q C:\\Craft\\BinaryCache\\ """ } // As the Windows Slaves are permanent ones, we erase the Workspace as the last thing we do deleteDir() } } diff --git a/flatpak/generic-build.pipeline b/flatpak/generic-build.pipeline index a764b7e..04cd1c5 100644 --- a/flatpak/generic-build.pipeline +++ b/flatpak/generic-build.pipeline @@ -1,72 +1,72 @@ // Request a node to be allocated to us node( "Flatpak&&x86_64" ) { // 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 { // Make sure the local environment is cleaned up stage('Cleaning up') { // We don't want to use a previously used staging repository, to make sure it doesn't exist sh """ rm -rf ~/staging-repo/ """ } // Retrieve the build instructions for Flatpak stage('Fetching Sources') { // Actual Application Sources checkout changelog: true, poll: true, scm: [ $class: 'GitSCM', branches: [[name: branchToBuild]], extensions: [[$class: 'CloneOption', timeout: 120]], userRemoteConfigs: [[url: repositoryUrl]] ] // General Flatpak build recipe repository checkout changelog: false, poll: false, scm: [ $class: 'GitSCM', branches: [[name: 'master']], extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'flatpak-kde-applications/']], userRemoteConfigs: [[url: 'https://anongit.kde.org/flatpak-kde-applications']] ] } // Build the application! stage('Building Application') { // Build it! // We conduct all builds from ~/jenkins to allow for the compiler cache to be shared between builds // It isn't necessary to create ~/staging-repo in advance as flatpak-builder will do that for us // We remove the app/ folder afterwards to be clean and tidy as we won't be inspecting it manually - we only want the artifacts in the repository! sh """ cd ~/jenkins/ BUILD_DATE=`date` flatpak-builder --force-clean --delete-build-dirs --arch=x86_64 --ccache --sandbox --user --install-deps-from=flathub --repo=\$HOME/staging-repo/ --subject="Built on \$BUILD_DATE" app "\$WORKSPACE/${manifest}" rm -rf app/ """ } // Run the repository export preparation process stage('Exporting Repository') { // Do the build! sh """ flatpak build-update-repo --prune --prune-depth=20 --generate-static-deltas \$HOME/staging-repo/ """ } // Finally we can sign the repository stage('Publishing Repository') { // Sign and then upload the repository to the final server sh """ flatpak build-commit-from --src-repo=\$HOME/staging-repo --gpg-sign=61C45BED \$HOME/public-repo --update-appstream flatpak build-update-repo --prune --prune-depth=20 --generate-static-deltas --gpg-sign=61C45BED \$HOME/public-repo - rsync -Ha --delete \$HOME/public-repo/ flatpak@racnoss.kde.org:/srv/www/distribute.kde.org/flatpak-apps-testing/ + rsync -Ha --delete \$HOME/public-repo/ flatpak@milonia.kde.org:/srv/www/distribute.kde.org/flatpak-apps-testing/ """ } } } } diff --git a/flatpak/publish-arm.pipeline b/flatpak/publish-arm.pipeline index 398bcc3..f8aaa71 100644 --- a/flatpak/publish-arm.pipeline +++ b/flatpak/publish-arm.pipeline @@ -1,18 +1,18 @@ // Request a node to be allocated to us node( "Flatpak" ) { // 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 { // Finally we can sign the repository stage('Publishing Repository') { // Sign and then upload the repository to the final server sh """ flatpak build-commit-from --src-repo=\$HOME/repo-arm --gpg-sign=61C45BED \$HOME/public-repo --update-appstream flatpak build-update-repo --prune --prune-depth=20 --generate-static-deltas --gpg-sign=61C45BED \$HOME/public-repo - rsync -Ha --delete \$HOME/public-repo/ flatpak@racnoss.kde.org:/srv/www/distribute.kde.org/flatpak-apps-testing/ + rsync -Ha --delete \$HOME/public-repo/ flatpak@milonia.kde.org:/srv/www/distribute.kde.org/flatpak-apps-testing/ """ } } } }