Changes between Version 100 and Version 101 of KDEProblems
- Timestamp:
- Apr 30, 2015, 6:53:33 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
KDEProblems
v100 v101 28 28 == Continuous Integration of KDE software == 29 29 30 KDE's developers are running a [http://build.kde.org/ Jenkins-based CI system] for the most of the KDE software. While this is already fully functioning for Linux a similar Windows-CI system is in a similar state to the idea of a CI system for KDE application on Mac(Ports).30 KDE's developers are running a [http://build.kde.org/ Jenkins-based CI system] for the most of the KDE software. This is fully functioning for Linux (and close to that for OSX) as of now. A Windows-CI system is in development at the moment. 31 31 32 32 There is also a set of [http://ebn.kde.org/ code-vetting software called English Breakfast Network] (EBN, for short) which supports all developers in writing cleaner code and documentation. 33 33 34 The KDE community has plans to [http://community.kde.org/Frameworks/Epics/Continuous_Integration introduce CI of KDE software also on OSX]. Further details can be found on a dedicated [wiki:KDEProblems/KDEMacPortsCI KDE/MacPorts CI page]. 35 36 If you're interested, you can check the [wiki:KDEProblems/KDEMacPortsCI/Status current status of an OSX/CI system based on MacPorts]. 34 An overview regarding KDE/CI can be found on a dedicated [wiki:KDEProblems/KDEMacPortsCI KDE/MacPorts CI page]. If you're interested in setting up an alternative CI system, you can check the [wiki:KDEProblems/KDEMacPortsCI/Status current status of an OSX/CI system based on MacPorts] which doesn't require Jenkins in order to function. 37 35 38 36