On Wed, Aug 27, 2014 at 7:37 PM, Aleix Pol <[email protected]> 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.
absolutely. 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. HS -- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
