Changes between Version 1 and Version 2 of KDEProblems/KDEMacPortsCI


Ignore:
Timestamp:
Apr 13, 2014, 11:13:54 PM (10 years ago)
Author:
mkae (Marko Käning)
Comment:

Info from Ben Cooksley on KDE-DEVEL

Legend:

Unmodified
Added
Removed
Modified

  • KDEProblems/KDEMacPortsCI

    v1 v2  
    22 
    33Currently there is an ongoing discussion on KDE-DEVEL about this topic. MacPort's key developers' expertise regarding the setup of their buildbots could perhaps be helpful for the KDE folks. On the other hand one might also run Jenkins on OSX and adapt its configuration to the KDE software's requirements.
     4
     5== Requirements for the CI system ==
     6
     7This is an excerpt from [http://lists.kde.org/?l=kde-devel&m=139738494320784&w=2 Ben Cooksley's post on KDE-DEVEL on thread "Running KDE apps on Apple OS X"]:
     8
     9----
     10
     11The infrastructure we have for our Linux builds should be nearly completely portable to OSX without too much trouble (in theory at least - i've never done any compilation on OSX).
     12
     13The actual requirements aren't written anywhere, but you might find the [http://quickgit.kde.org/?p=websites%2Fbuild-kde-org.git&a=tree&h=48c561bdfa467b0a09d6591491abc168b63197ce&hb=f2d024f155bed23a9e81b0175e5c7d752d6d8f14&f=documentation documentation I've written for the CI system] to be of some use.
     14
     15A basic run down of what the CI system needs however:
     16
     17 1) Python 2.x, with json and lxml support (for the scripts which conduct builds)
     18
     19 2) Java (for the Jenkins node agent itself)
     20
     21 3) RSync and SSH (for the transferral of completed builds between nodes)
     22
     23 4) Git, Subversion, Bazaar, wget and GNU Tar (to access source code)
     24
     25 5) GNU Patch (for applying custom patches, used in certain builds)
     26
     27 6) A compiler, usable by CMake, QMake and autotools based build systems
     28
     29 7) GNU Make, Automake, Autoconf (for carrying out the build, and configuring it in certain rare cases)
     30
     31We'll need to make adjustments to ensure the system doesn't attempt to launch Xvfb or a X11 Window Manager, which it currently will do when executing tests. These should be fairly easy to do however.
     32
     33To build certain projects, the compiler will need to support C# and a certain level of C++11 as well. The Mono bindings will not be buildable if C# support is unavailable.
     34
     35Under no circumstance should a CI node have Qt installed at the system level in any form, as this is provided directly by the CI system itself.
     36
     37----
     38
     39Checking on the above requirements in the current MacPorts tree shows that all necessary tools are available. Whether available versions of the programs work can be used with KDE's current CI system has to be checked.
     40
     41'''The only problem seems to be C# support.''' But those projects will probably only be running on Windows anyways.