<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Aug 4, 2015 9:27 PM, "Michael Scherer" <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br>
><br>
> Hi again,<br>
> So, while looking at jenkins, I would also propose the following course<br>
> of action.<br>
><br>
> We have some failry complex script stored inside jenkins config, and I<br>
> think it would be better to have them as script in the git repo :<br>
> <a href="https://github.com/gluster/glusterfs-patch-acceptance-tests">https://github.com/gluster/glusterfs-patch-acceptance-tests</a><br>
Definitely a yes from me. This would open up the gate to understand the Jenkins setup what we have as most of the folks don't have infrastructure knowledge.<br>
><br>
> it seems that someone ( Justin, Niels ? ) started to migrate<br>
> compare-bug-version-and-git-branch to a script, so I just went ahead and<br>
> finished that, by replacing the config with a call to that proper<br>
> script.<br>
><br>
> If broken, please ping me.<br>
><br>
> I would like to have 1 single script to run smoke + build, so we can<br>
> have a unified script between el6, fedora, netbsd6, netbsd7 and<br>
> freebsd.<br>
><br>
> Does it sound like a plan ?<br>
><br>
> --<br>
> Michael Scherer<br>
> Sysadmin, Community Infrastructure and Platform, OSAS<br>
><br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
><br>
</p>