[ovirt-devel] Jenkins jobs ownership

[Yaniv Kaul]

On Sat, Feb 4, 2017 at 4:28 PM, Eyal Edri <eedri at redhat.com> wrote:

>
>
> On Fri, Feb 3, 2017 at 3:59 PM, Sandro Bonazzola <sbonazzo at redhat.com>
> wrote:
>
>> Hi,
>>
>> I'm taking a discussion starting in gerrit to the mailing lists for
>> broader audience discussion.
>> In https://gerrit.ovirt.org/69268 it has been asked:
>>
>> 8<---------------------------------------------------------
>> Sandro, can someone from you team fix this?
>>
>> It does not make sense that ovirt-imageio maintainers will babysit this
>> code base. This must be the responsibility of your team. We have separate
>> projects for this; we maintain ovirt-imageio, your team maintain the
>> jenkins project.
>>
>> If you want us to maintain this, this code must move into ovirt-imageio
>> repository, so we have full control of it.
>> ---------------------------------------------------->8
>>
>> So I'd like to make clear a couple of things.
>>
>> Integration team is not committing to maintain the hundreds of jenkins
>> jobs currently existing alone.
>>
>> Integration team is also not committing monitoring them.
>>
>> integration team is not maintaining Jenkins project. Jenkins project is
>> used by developers who need their tests and builds to be executed in
>> Jenkins. you're free to run your tests wherever you feel more comfortable
>> and build packages in your preferred build service (copr, koji, openbuild,
>> Jenkins, centos cbs,...) provided that on release day the source code is
>> correctly tagged in gerrit and tarball available on resources.ovirt.org.
>> If the rpms are not available within CentOS Virt SIG and Fedora main
>> repository or in a copr repository referenced by ovirt-release rpm, you're
>> also required to provide rpms and src.rpms to be published within oVirt yum
>> repository.
>>
>> As release engineering manager, I try to fix Jenkins issues whenever I
>> can for those jobs which are needed to get the release built and published
>> so in this specific case, I will probably end up with taking over the patch
>> and get it to merged state just because fc23 is EOL and as release
>> engineering we don't want fc23 packages being shipped anymore.
>>
>> If you want to use Jenkins, you're allowed to. oVirt infra team is
>> maintaining the Jenkins server infrastructure and the Standard CI framework
>> to make it easier to write tests and build scripts.
>> If you need help on that area, please open a ticket on
>> infra-support at ovirt.org.
>>
>> I'm here for any further question or open discussion.
>>
>
> I completely agree with Sandro.
>
> Its not the responsibility of infra team or integration team to make sure
> a certain oVirt project is building / compiling / testing for any supported
> OS, this lays solely on the maintainer or the team developing the project.
> As Sandro mentioned, the infra team is providing simple tools for building
> / testing / publishing any oVirt project which uses the standard CI and
> continues to evolve and simplify the process even more
> so it will be very easy for anyone to add those.
>
> If the current tools / framework is missing something or mis-behaving, you
> can also contact the infra team or open a ticket as Sandro mentioned above
> and we'll do our best to find the best solution for it.
>

Perhaps there's a 'handover' process that is missing, so when the initial
script/job is written it'll be passed properly to the maintainer?
Y.


>
>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>> _______________________________________________
>> Infra mailing list
>> Infra at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170204/87bfa124/attachment.html>