<div dir="ltr">I'm sorry, I think I made a mistake. Right after I pushed the first version, I received a BUILD FAILED email. Can I abandon the commit or something without messing it up further?<div><br></div><div>--</div><div>Vishnu</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 8:20 PM, Vishnu Sreekumar <span dir="ltr"><<a href="mailto:vishnu.srkmr@gmail.com" target="_blank">vishnu.srkmr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Did an initial commit, please review..<div><br></div><div><br></div><div>--</div><div>Vishnu</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 7:40 PM, Vishnu Sreekumar <span dir="ltr"><<a href="mailto:vishnu.srkmr@gmail.com" target="_blank">vishnu.srkmr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks David, that was really helpfull.. :)<div><br></div><div>From what I understand so far, I need to create the yaml file which calls a shell-script (which should go inside shell-scripts/). The alert_patch....py with all the required options will be called withing the shell script.</div><div>If this is correct,</div><div>1) What should be the trigger for the job?</div><div><br></div><div>I am still not sure what the scm is for. But as you suggested I'll start with the yaml file and the basic structure first.</div><div><br></div><div>--</div><div>Vishnu</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 6:29 PM, David Caro Estevez <span dir="ltr"><<a href="mailto:dcaroest@redhat.com" target="_blank">dcaroest@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Vishnu!!<br>
<br>
Thanks! Yes, had a lot of rest :)<br>
<br>
Let me give you a small intro to jenkins yaml ;)<br>
<br>
We keep all of the jobs yaml files (and related) here:<br>
<br>
<a href="https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs;hb=refs/heads/master" target="_blank">https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs;hb=refs/heads/master</a><br>
<br>
There you can see three (for now) dirs that separate code by code type (sheel,<br>
groovy anbd yaml). Under sheel and groovy you'll find shell and groovy<br>
scripts/templates that we use inside the jenkins jobs themselves.<br>
<br>
They might not be run per-se, as they might be templates and require to have<br>
some of the variables inside them resolved previously to be valid shell/groovy<br>
scripts.<br>
<br>
Under yaml, you'll find all the yaml files we use, separated by function (as<br>
they are separated by jenkins-job-builder itself, like triggers, projects/jobs,<br>
scms, ...)<br>
<br>
There's a small README file that explains a bit how it's organized and how to<br>
test it (I have to update it too ;/, we moved to a newer version of<br>
jenkins-job-builder last week and the parameters to run it have changed a bit)<br>
<br>
So for this job, you can write everything up on a single yaml file under<br>
jobs/confs/yaml/system/ with a name like system_gerrit-patches-whatever.yaml<br>
<br>
There you can just create a job section with a shell builder that does the<br>
calling.<br>
<br>
You'll need also to include the jenkins scm,check first if you can use one of<br>
the already defined under scm for it, if not, feel free to add the new one you<br>
need there.<br>
<br>
We can start just with creating that file and the basic structure of it, and<br>
move from there once reviewing on gerrit once the patch is there, what do you<br>
think?<br>
<div><div><br>
<br>
On 03/30, Vishnu Sreekumar wrote:<br>
> Hi David,<br>
><br>
> Hope you had a good vacation!<br>
><br>
> So I write a yaml template and push it to the repository? I don't have<br>
> access to the jenkins job builder. Do I need to commit the yaml file to a<br>
> specific folder or anwhere in this tree [1] is ok?<br>
><br>
> [1]<br>
> <a href="https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs;h=284a9e1579cdd0b2828b6e3b258b3e5800269a46;hb=refs/heads/master" target="_blank">https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs;h=284a9e1579cdd0b2828b6e3b258b3e5800269a46;hb=refs/heads/master</a><br>
><br>
> Thanks,<br>
> Vishnu<br>
<br>
</div></div><span><font color="#888888">--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605" target="_blank">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a><br>
Web: <a href="http://www.redhat.com" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>