<div dir="ltr">Maybe I could create a new temporary job to just get stuff installed. I'll see what I can do.<div><br></div><div>Also, what about the *BSDs?</div><div><br></div><div>~kaushal</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 11, 2015 at 9:11 PM, Justin Clift <span dir="ltr"><<a href="mailto:justin@gluster.org" target="_blank">justin@gluster.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11 Feb 2015, at 13:38, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
> I was looking at the job configurations on Jenkins. Most of the jobs are run by running shell scripts defined in the Jenkins job configuration. The shell scripts can be edited directly from the Jenkins interface.<br>
><br>
> So, I was thinking, if I could use these scripts to get the packages I need installed on the slaves.<br>
><br>
> I need to get the packages installed on the slaves so I can get at least the initial lot of changes merged before the feature freeze. But, Luis is away and no body has responded to the BSD requests yet, and I'm getting a little anxious.<br>
><br>
> The smoke job does this to get cmockery installed, so I'm assuming I could do this. But what do other feel about this?<br>
<br>
</span>Hmmm, if that gets the job done while Luis is away, then yeah, go for it. Just be careful<br>
not to break things. :)<br>
<span class="HOEnZb"><font color="#888888"><br>
+ Justin<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
GlusterFS - <a href="http://www.gluster.org" target="_blank">http://www.gluster.org</a><br>
<br>
An open source, distributed file system scaling to several<br>
petabytes, and handling thousands of clients.<br>
<br>
My personal twitter: <a href="http://twitter.com/realjustinclift" target="_blank">twitter.com/realjustinclift</a><br>
<br>
</div></div></blockquote></div><br></div>