Le mardi 26 janvier 2016 à 09:47 +0100, Niels de Vos a écrit : > On Tue, Jan 26, 2016 at 08:55:39AM +0100, Michael Scherer wrote: > > Le lundi 25 janvier 2016 à 22:24 +0100, Niels de Vos a écrit : > > > On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote: > > > > I was also planning to look at jenkins job builder for the jenkins, but > > > > no time yet. Will be after jenkins migration to a new host (which is > > > > still not planned, unlike gerrit where we should be attempting to find a > > > > time for that) > > > > > > We also might want to use Jenkins Job Builder for the tests we're adding > > > to the CentOS CI. Maybe we could experiment with it there first, and > > > then use our knowledge to the Gluster Jenkins? > > > > Why not. I think it would work fine on our too, as i am not sure it need > > to completely take over the server configuration. > > I dont have any experience with JBB, and have no idea how it works. Our > Gluster Jenkins does not have many changes in the jobs, so maybe there > is no need for it? I really dont know. But, you might be able to spend > your time in a more useful way until we find out ;-) It allow us to track change in git, kinda like the get-job and xml script that you pointed. So people that would make change would have to submit patches, which permit to revert, track what was changed, review, etc, etc. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
