On Tue, Mar 4, 2014 at 9:30 PM, David Faure <fa...@kde.org> wrote: > On Tuesday 04 March 2014 12:08:07 Ben Cooksley wrote: >> On Sun, Mar 2, 2014 at 5:03 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El Dissabte, 1 de març de 2014, a les 16:53:28, David Faure va escriure: >> >> On Saturday 01 March 2014 16:39:56 Albert Astals Cid wrote: >> >> > Every time someone commits to okular, which may a bit too much, no? >> >> >> >> This is not what I suggested. >> >> >> >> I suggested: if A and B are both marked as "dirty" because a commit was >> >> just pushed to them, then look at whether one depends on the other, and >> >> rebuild in this order. >> >> >> >> If A isn't "dirty", i.e. no commits for a long time, don't rebuild A. >> >> (where "A" is any okular dependency, in your example) >> > >> > Ah, agreed, that makes sense. Anyone knows if it's possible? >> >> This should be facilitated by the following Jenkins plugin. >> https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin >> >> However that means that someone will need to reconfigure all jobs to >> include the dependency metadata - so we will probably want to script >> it I imagine. > > I'm a big fan of scripting (and I can write scripts for any change you'd like > to see made to a bunch of files) -- but I thought you said jenkins jobs could > not be modified in config files and had to be modified in the GUI?
Jenkins has an Web API which can be used, as well as a Java client to help interact with it. In terms of modifying the configuration files on disk - they're XML based data, and i'm not sure if we can get Jenkins to reparse them short of restarting it completely. > > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE, in particular KDE Frameworks 5 > Thanks, Ben _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel