Changes between Version 141 and Version 142 of KDEProblems/KDEMacPortsCI/Status

Timestamp:

Jul 26, 2014, 1:54:35 PM (10 years ago)

Author:

mkae (Marko Käning)

Comment:

Remove the extra section on the KDE/CI scripts as they are now included in the mp-osx-ci repo

KDEProblems/KDEMacPortsCI/Status

@@ -60 +60 @@
 
 In order to start building up a build slave for KDE's Jenkins-based CI system it is in principle needed to clone [http://quickgit.kde.org/?p=websites%2Fbuild-kde-org.git websites/build-kde-org], BUT further down it will become clear, that it is a good idea to track all changes to be made for websites/build-kde-org in a dedicated branch.
-That is why a [http://quickgit.kde.org/?p=clones%2Fwebsites%2Fbuild-kde-org%2Fkaning%2Fmp-osx-ci.git dedicated repository clone] has been introduced which contains a new branch with all changes needed for CI system on OSX.
+That is why the [http://quickgit.kde.org/?p=clones%2Fwebsites%2Fbuild-kde-org%2Fkaning%2Fmp-osx-ci.git dedicated repository clone "mp-osx-ci"] has been introduced which contains a new branch 'mp-osx-ci' containing all changes needed for a CI system on OSX.
 
 Create some folders, clone and update CI system (assuming a user "kdeci" with its home directory "/Users/kdeci"): 
@@ -76 +76 @@
 (BTW, if you were checking out the original repository from git://anongit.kde.org/websites/build-kde-org you'd have to check out the "production" branch.)
 
-=== Grab the scripts for the CI system from the MacPorts/KDE testing repository ===
-
-Clone the [https://projects.kde.org/projects/playground/sdk/macports-kde "MacPorts/testing repository"] and have a look at the CI scripts:
-{{{
-$ cd ~/WC
-$ git clone git://anongit.kde.org/macports-kde
-$ sudo port install tree
-$ tree macports-kde/contrib/scripts/KDECI/
-macports-kde/contrib/scripts/KDECI/
-├── README.txt
-├── build.sh
-├── create-env.sh
-├── install.sh
-├── mp-osx-ci_diff.sh
-├── patch_mp-osx-ci.diff
-├── patches
-│   └── qt5
-│       └── kf5-qt5
-│           └── patch-qstandardpaths_mac.cpp.diff
-├── prepare.sh
-├── tier-install.sh
-├── tier1.fw
-├── tier2.fw
-├── tier3.fw
-├── tier4.fw
-└── tier5.fw
-
-3 directories, 14 files
-}}}
-In principle those files can be run from within that clone, but they are not perfect yet, so they might end up in ~/scripts if you interrupt the script execution.
-Up to now I always copied these files therefore directly into ~/scripts, which is - admittedly - not really a good solution!
-
-These scripts become important later on...