CP, jenkins, and all that madness

Harald Sitter apachelogger at ubuntu.com
Wed Aug 27 17:51:13 UTC 2014

On Wed, Aug 27, 2014 at 7:37 PM, Aleix Pol <aleixpol at kde.org> wrote:
> Actually, maybe it could be interesting if you could just host the machines
> doing the tasks but extend the build.kde.org instance so the information
> could be shown together with each project.
> Or maybe it doesn't make sense, just a thought.

it is certainly a thing to consider in the future. adding a kubuntu
specific build slave to build.kde that does the heavy lifting and
having the projects orchestrated on build.kde proper certainly should
be possible. it would neatly aggregate all the relevant information in
one place.

to be fair though, from what I understand this does not actually
require the builds to be orchestrated by build.kde though: jenkins has
a concept of an external project which gets status information fed
from the outside and is in essence just reflecting something going on
elsewhere (either through the client.jar or the REST API apparently),
so propagating kubuntu integration status into build.kde wouldn't
necessarily require us to use jenkins directly.


More information about the kubuntu-devel mailing list