<div dir="ltr"><div><br></div><a href="https://gerrit.ovirt.org/#/c/39357/">https://gerrit.ovirt.org/#/c/39357/</a><br><div><br></div><div>I fixed the intendation error. But the build still failed.</div><div><br></div><div>I've the below questions.</div><div><br></div><div>1) How do I specify the full path to the script?</div><div>2) As which user does it connects to the gerrit server? (I've left the --user option blank)</div><div>3) How about the ssh authentication?</div><div><br></div><div>Thanks,</div><div>Vishnu</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 1, 2015 at 9:19 PM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hey vishnu,<br>
can you share the link to the patch? is it still blocking you?<br>
<div><div class="h5"><br>
----- Original Message -----<br>
> From: "Vishnu Sreekumar" <<a href="mailto:vishnu.srkmr@gmail.com">vishnu.srkmr@gmail.com</a>><br>
> To: "David Caro Estevez" <<a href="mailto:dcaroest@redhat.com">dcaroest@redhat.com</a>>, "Eyal Edri" <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>>, <a href="mailto:infra@ovirt.org">infra@ovirt.org</a><br>
> Sent: Monday, March 30, 2015 3:23:21 PM<br>
> Subject: Re: Help with the jenkins yaml<br>
><br>
> I'm sorry, I think I made a mistake. Right after I pushed the first version,<br>
> I received a BUILD FAILED email. Can I abandon the commit or something<br>
> without messing it up further?<br>
><br>
> --<br>
> Vishnu<br>
><br>
> On Mon, Mar 30, 2015 at 8:20 PM, Vishnu Sreekumar < <a href="mailto:vishnu.srkmr@gmail.com">vishnu.srkmr@gmail.com</a> ><br>
> wrote:<br>
><br>
><br>
><br>
> Did an initial commit, please review..<br>
><br>
><br>
> --<br>
> Vishnu<br>
><br>
> On Mon, Mar 30, 2015 at 7:40 PM, Vishnu Sreekumar < <a href="mailto:vishnu.srkmr@gmail.com">vishnu.srkmr@gmail.com</a> ><br>
> wrote:<br>
><br>
><br>
><br>
> Thanks David, that was really helpfull.. :)<br>
><br>
> From what I understand so far, I need to create the yaml file which calls a<br>
> shell-script (which should go inside shell-scripts/). The alert_patch....py<br>
> with all the required options will be called withing the shell script.<br>
> If this is correct,<br>
> 1) What should be the trigger for the job?<br>
><br>
> I am still not sure what the scm is for. But as you suggested I'll start with<br>
> the yaml file and the basic structure first.<br>
><br>
> --<br>
> Vishnu<br>
><br>
> On Mon, Mar 30, 2015 at 6:29 PM, David Caro Estevez < <a href="mailto:dcaroest@redhat.com">dcaroest@redhat.com</a> ><br>
> wrote:<br>
><br>
><br>
><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<br>
> (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<br>
> 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,<br>
> 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<br>
> 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<br>
> 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>
><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>
> --<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">+420 532 294 605</a><br>
> Email: <a href="mailto:dcaro@redhat.com">dcaro@redhat.com</a><br>
> Web: <a href="http://www.redhat.com" target="_blank">www.redhat.com</a><br>
> RHT Global #: 82-62605<br>
><br>
><br>
><br>
><br>
</div></div>> _______________________________________________<br>
> Infra mailing list<br>
> <a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/infra" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
><br>
</blockquote></div><br></div>