On Tuesday 21 April 2015 13:45:06 Scarlett Clark wrote: > kdev-crossfire: > https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLATF > ORM=Linux,compiler=gcc/11/ > > kdev-php-formatter: > https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4/P > LATFORM=Linux,compiler=gcc/10/console > > kdev-xtest: > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest%2 > 0master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console
All of the above are unmaintained and should not run through CI until someone spends time on fixing their issues. They are all in playground as well. > kdev-css: > https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Linux > ,compiler=gcc/5/console This one was easy and I fixed it. But in general, I don't think that adding all playground projects to the CI is a good idea, as many things in there are just historic artifacts. Bye -- Milian Wolff m...@milianw.de http://milianw.de
signature.asc
Description: This is a digitally signed message part.
