[ovirt-devel] Heads up: dropping fcraw jobs from jenkins

[Barak Korren]

On 12 March 2018 at 16:44, Sandro Bonazzola <sbonazzo at redhat.com> wrote:

>
>
>
>
> 2018-03-12 15:36 GMT+01:00 Eyal Edri <eedri at redhat.com>:
>
>>
>>
>> On Mon, Mar 12, 2018 at 3:11 PM, Yedidyah Bar David <didi at redhat.com>
>> wrote:
>>
>>> On Mon, Mar 12, 2018 at 12:50 PM, Nir Soffer <nsoffer at redhat.com> wrote:
>>> > On Thu, Mar 8, 2018 at 4:00 PM Sandro Bonazzola <sbonazzo at redhat.com>
>>> wrote:
>>> >>
>>> >> Following today call, I'm going to push a patch for dropping all
>>> rawhide
>>> >> jobs from jenkins.
>>> >> This should help avoiding distractions and reducing patches blocked by
>>> >> rawhide issues.
>>> >
>>> >
>>> > Hi Sandro,
>>> >
>>> > I worked hard to get ioprocess and ovirt-imageio working on fcraw, so
>>> this
>>> > change will create extra work for me to fix the regressions later when
>>> we
>>> > enable fcraw again.
>>> >
>>> > Please revert the change for the ovirt-imageio and ioprocess projects.
>>>
>>> I'd like too to keep fcraw, for otopi, now pushed
>>> https://gerrit.ovirt.org/88816 .
>>>
>>> Perhaps for the time being it's best if other projects' maintainers do
>>> the same, if they want to, and commit to fixing issues in fcraw quickly
>>> (I hope I do...).
>>>
>>
>> Maybe its a good oppertunity to move the projects to V2, so the settings
>> will be done inside the project itself and not in Jenkisn repo.
>> Also, maintainers needs to understand that if fcraw build is failing no
>> other distro will be deployed to tested ( as communicated numerous times
>> already ), so if you're not sure fcraw will work
>> keep it on check-patch only and don't add build-artifacts jobs.
>>
>
> Can you point to the documentation for V2?
>

The 1st one is on-the-house ;) Want us to send patches to move otopi to v2?

Docs are being worked on but in essence V2 makes the UX for gerrit projects
similar to the way things have worked for GitHub projects for a while now
[1].

V2 does provide way more then what is documented there (you need more to be
able to cover complex scenarios like supporting specific sets of
architectures in specific distributions), but what we have there is enough
to get the basic ideas and do initial work.

[1]:
http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub/#the-automationyaml-file

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20180313/beb69623/attachment-0001.html>