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?
-- Vishnu On Mon, Mar 30, 2015 at 8:20 PM, Vishnu Sreekumar <vishnu.sr...@gmail.com> wrote: > Did an initial commit, please review.. > > > -- > Vishnu > > On Mon, Mar 30, 2015 at 7:40 PM, Vishnu Sreekumar <vishnu.sr...@gmail.com> > wrote: > >> Thanks David, that was really helpfull.. :) >> >> 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. >> If this is correct, >> 1) What should be the trigger for the job? >> >> 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. >> >> -- >> Vishnu >> >> On Mon, Mar 30, 2015 at 6:29 PM, David Caro Estevez <dcaro...@redhat.com> >> wrote: >> >>> >>> Hi Vishnu!! >>> >>> Thanks! Yes, had a lot of rest :) >>> >>> Let me give you a small intro to jenkins yaml ;) >>> >>> We keep all of the jobs yaml files (and related) here: >>> >>> >>> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs;hb=refs/heads/master >>> >>> There you can see three (for now) dirs that separate code by code type >>> (sheel, >>> groovy anbd yaml). Under sheel and groovy you'll find shell and groovy >>> scripts/templates that we use inside the jenkins jobs themselves. >>> >>> They might not be run per-se, as they might be templates and require to >>> have >>> some of the variables inside them resolved previously to be valid >>> shell/groovy >>> scripts. >>> >>> Under yaml, you'll find all the yaml files we use, separated by function >>> (as >>> they are separated by jenkins-job-builder itself, like triggers, >>> projects/jobs, >>> scms, ...) >>> >>> There's a small README file that explains a bit how it's organized and >>> how to >>> test it (I have to update it too ;/, we moved to a newer version of >>> jenkins-job-builder last week and the parameters to run it have changed >>> a bit) >>> >>> So for this job, you can write everything up on a single yaml file under >>> jobs/confs/yaml/system/ with a name like >>> system_gerrit-patches-whatever.yaml >>> >>> There you can just create a job section with a shell builder that does >>> the >>> calling. >>> >>> You'll need also to include the jenkins scm,check first if you can use >>> one of >>> the already defined under scm for it, if not, feel free to add the new >>> one you >>> need there. >>> >>> We can start just with creating that file and the basic structure of it, >>> and >>> move from there once reviewing on gerrit once the patch is there, what >>> do you >>> think? >>> >>> >>> On 03/30, Vishnu Sreekumar wrote: >>> > Hi David, >>> > >>> > Hope you had a good vacation! >>> > >>> > So I write a yaml template and push it to the repository? I don't have >>> > access to the jenkins job builder. Do I need to commit the yaml file >>> to a >>> > specific folder or anwhere in this tree [1] is ok? >>> > >>> > [1] >>> > >>> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs;h=284a9e1579cdd0b2828b6e3b258b3e5800269a46;hb=refs/heads/master >>> > >>> > Thanks, >>> > Vishnu >>> >>> -- >>> David Caro >>> >>> Red Hat S.L. >>> Continuous Integration Engineer - EMEA ENG Virtualization R&D >>> >>> Tel.: +420 532 294 605 >>> Email: dc...@redhat.com >>> Web: www.redhat.com >>> RHT Global #: 82-62605 >>> >> >> >
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra