Changes between Version 180 and Version 181 of KDEProblems/KDEMacPortsCI/Status

Timestamp:

Aug 24, 2014, 12:19:29 PM (10 years ago)

Author:

mkae (Marko Käning)

Comment:

move helper bash scripts up

KDEProblems/KDEMacPortsCI/Status

@@ -139 +139 @@
 }}}
 and still required more work. The patch enables kdoctools and kdelibs4support to locate their files successfully (which had up to now to be handled using an even nastier workaround), but apart from that there are still problems with config files. '''In short: this is still work in progress...'''
+
+
+
+== Helper bash scripts == 
+
+KDE's Jenkins-based CI system mainly makes use of these two python scripts:
+{{{
+tools/prepare-environment.py
+tools/perform-build.py
+}}}
+
+For qt5 they've above been used in order to show the workflow. But in daily use it is more practical to consider some helper bash scripts which ease all actions needed to run project builds on an OSX/CI system for which there's not yet the Jenkins integration available.
+
+The various projects on the CI system have to be handled by replacing "PROJECT" with the project name of the corresponding framework or application:
+{{{
+$ python2.7 tools/prepare-environment.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
+...
+$ (cd ~/WC/KDECI-build/PROJECT; git checkout jenkins)
+...
+$ python2.7 tools/perform-build.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
+...
+}}}
+or alternatively by using [https://projects.kde.org/projects/playground/sdk/macports-kde/repository/revisions/master/show/contrib/scripts/KDECI helper bash scripts from our MacPorts/KDE git repository]
+{{{
+$ ./prepare.sh PROJECT
+...
+$ ./build.sh PROJECT
+...
+}}}
+where {{{prepare.sh}}} takes care of creating the build directory if it is not yet existing as well as checks out the branch 'jenkins'. Alternatively one can combine these steps using:
+{{{
+$ ./install.sh PROJECT
+}}}
 
 
@@ -260 +293 @@
 == Installation of other projects and KDE frameworks ==
 
-The various frameworks have to be handled by replacing "PROJECT" with the framework's project name:
-{{{
-$ python2.7 tools/prepare-environment.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
-...
-$ (cd ~/WC/KDECI-build/PROJECT; git checkout jenkins)
-...
-$ python2.7 tools/perform-build.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
-...
-}}}
-or alternatively by using [https://projects.kde.org/projects/playground/sdk/macports-kde/repository/revisions/master/show/contrib/scripts/KDECI scripts from our MacPorts/KDE git repository]
-{{{
-$ ./prepare.sh PROJECT
-...
-$ ./build.sh PROJECT
-...
-}}}
-where {{{prepare.sh}}} takes care of creating the build directory if it is not yet existing as well as checks out the branch 'jenkins'. This is only needed when building a project manually, otherwise it gets one by the jenkins slave. Alternatively one can combine both of these steps using:
-{{{
-$ ./install.sh PROJECT
-}}}
-
-All frameworks of a specific tier can be build as a whole using 
+Specific frameworks can be installed using {{{install.sh}}} , but one can also build all frameworks of a specific tier as a whole using 
 {{{
 $ # This builds all frameworks of tier 1