<div dir="ltr"><div><div>Hi Niels,<br><br></div>Thank you. This gives me a much clearer picture than what I had with simply exploring the Jenkins web UI and the server. I still have a few more questions:<br><br></div><div>What is /opt/qa. Where is that code coming from?<br></div><div><br>I'm guessing that a lot of this isn't written down. So I'm going to make an effort to document the current state as is in the Ops-Guide section of the documentation.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 30, 2016 at 1:36 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</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 Mon, May 30, 2016 at 10:21:27AM +0530, Nigel Babu wrote:<br>
> Hello folks,<br>
><br>
> I'm trying to get a sense of how our Jenkins instance. In particular, I'm<br>
> trying to understand the following:<br>
><br>
> 1. How jobs are created. Is this version controlled or automated in any<br>
> manner?<br>
<br>
</span>The jobs are created in the Jenkins webui, and later exported with the<br>
Jenkins CLI (<a href="https://build.gluster.org/cli" rel="noreferrer" target="_blank">https://build.gluster.org/cli</a>). The resulting XML files are<br>
stored here:<br>
<a href="https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/jenkins/jobs" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/jenkins/jobs</a><br>
<span class=""><br>
> 2. How are the machines created? Do we have a standardized image?<br>
<br>
</span>No idea, Micheal Scherer should know. I guess Manu setup the NetBSD<br>
systems, not sure who takes care of the FreeBSD ones.<br>
<span class=""><br>
> 3. Where is the code (the repository) for the tests that are run?<br>
<br>
</span>Most of the tests have their scripts in the patch-acceptance-test<br>
repository:<br>
<a href="https://github.com/gluster/glusterfs-patch-acceptance-tests" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-patch-acceptance-tests</a><br>
<br>
The regression tests themselves are contained in the glusterfs<br>
repository. We expect that all changes to the sources come with a<br>
test-case.<br>
<span class=""><br>
> 4. What is the process for going from updating the code for a test to<br>
> updating the job on Jenkins? Is this automated and/or documented?<br>
<br>
</span>Not sure. The number of people that modify the Jenkins jobs is very<br>
small. All of them are aware (or should be!) that a modification<br>
requires updating the XML files in the git repo.<br>
<span class=""><br>
> 5. How many of the jobs are critical?<br>
<br>
</span>All of the regular running ones?<br>
<span class=""><br>
> 6. What is the process for creating new jobs/new types of tests?<br>
<br>
</span>That is hardly ever needed, and more of an exception. If someone needs a<br>
new job on <a href="http://build.gluster.org" rel="noreferrer" target="_blank">build.gluster.org</a> one of the people with an account can<br>
create it.<br>
<span class=""><br>
> Bonus Question: Is there any friction that you'd like to see us reduce?<br>
<br>
</span>One of the things we're doing for this is to move more time consuming<br>
and multi-host tests to <a href="http://ci.centos.org" rel="noreferrer" target="_blank">ci.centos.org</a>. Currently the regression tests<br>
are still running on our own instance, but the CentOS CI has much more<br>
and much faster hardware (no VMs). There is the long-term plan to move<br>
at least a bunch of the heavy testing to their Jenkins instance.<br>
<br>
Also scheduled jobs (distaf tests, tests for integration with other<br>
projects, nightly builds, ....) are supposed to get added to the CentOS<br>
CI, and not our <a href="http://build.gluster.org" rel="noreferrer" target="_blank">build.gluster.org</a> environment:<br>
<a href="https://ci.centos.org/view/Gluster/" rel="noreferrer" target="_blank">https://ci.centos.org/view/Gluster/</a><br>
<br>
Thanks,<br>
Niels<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>