Frameworks/Epics/Continuous Integration: Difference between revisions

From KDE Community Wiki
No edit summary
(Some restructuring)
Line 6: Line 6:
* [http://quickgit.kde.org/?p=websites%2Fbuild-kde-org.git&a=blob&h=3292ffe7cccf2b80a5e127de0e28cff4cd620a35&hb=5491e3dc37c623f5ee081cde2b548637ae704ad8&f=documentation%2Fjob-execution.txt job execution]
* [http://quickgit.kde.org/?p=websites%2Fbuild-kde-org.git&a=blob&h=3292ffe7cccf2b80a5e127de0e28cff4cd620a35&hb=5491e3dc37c623f5ee081cde2b548637ae704ad8&f=documentation%2Fjob-execution.txt job execution]


=== Linux ===


There is currently WIP for a Mac OS X slave and we're looking for MS Windows licenses.
Is working well.
 
=== Mac OS X ===
 
Some work in progress.
Some more information [https://trac.macports.org/wiki/KDEProblems/KDEMacPortsCI about KDE CI on MacPorts].
 
=== MS Windows ===
 
A Windows server is being installed.
 
=== Other systems ===


Another idea would be CI for and on Android (ARM and/or x86).
Another idea would be CI for and on Android (ARM and/or x86).

Revision as of 22:14, 9 May 2014

We have actually already a good working Continuous Integration (CI) system for the KDE Frameworks (and KDE applications) for Linux thanks to Ben Cooksley. It is based on Jenkins and can be found at build.kde.org.

Some more information about our CI system can be found here:

Linux

Is working well.

Mac OS X

Some work in progress. Some more information about KDE CI on MacPorts.

MS Windows

A Windows server is being installed.

Other systems

Another idea would be CI for and on Android (ARM and/or x86).