Re: [ovirt-devel] Jenkins jobs ownership

Having said that, I would be perfectly fine with a single repository that tracks the release configuration, but only if it also held the git repository link and hash/branch name that is supposed to be released. It would be in some way a "distgit repo". Something like Sandro has for builds. [ovirt-4.0.x-ci] git://gerrit.ovirt.org/project.git#ovirt-4.0.x git://gerrit.ovirt.org/project2.git#v4.0.x git://github.com/Me/repo#master [ovirt-4.0.6] git://gerrit.ovirt.org/project.git#ovirt-4.0.6 git://gerrit.ovirt.org/project2.git#v4.0.6 http://github.com/Me/repo/releases/x.y.z.zip Any release would then be reviewed by the CI team and that would be fine for me. It would allow any branch name or versioning convention and would not pollute the sources. It would also be gerrit agnostic. Martin On Sun, Feb 5, 2017 at 10:17 AM, Martin Sivak <msivak(a)redhat.com&gt; wrote: > Hi, > >> The fact that this is specified in the 'jenkins' repo **does not place >> this outside the maintainers` responsibility**. > > >> We actually have an initiative to move this information to the project >> repos. I've started with asking on devel list about how to specify >> this as part of Standard-CI [1]. But have received little topical >> response so far. >> [1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html > > You've got enough responses already to propose a different schema than > fixed branch names. Just give us a config file. Seriously, stop > reinventing the wheel and take a look at how others are doing it > (distgit, travis, tito, ...). > > Martin > >> >> -- >> Barak Korren >> bkorren(a)redhat.com >> RHCE, RHCi, RHV-DevOps Team >> https://ifireball.wordpress.com/ >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel