And also, feel free to move it to check-patch.sh code as well.
Including this in vdsm seem like the best option.
Can you point me to the source of this job?
On Tue, Jul 19, 2016 at 6:19 PM, Eyal Edri <eedri(a)redhat.com> wrote:
>
> This isn't new, it was running for a few years, just on old jenkins,
> Maybe you just noticed it.
>
> Allon & Dan are familiar with that job and it already found in the past
> real issues.
> If you want to remove/disable it, I have no problem - just make sure
> you're synced with all VDSM people that requested this job in the first
> place.
>
> On Tue, Jul 19, 2016 at 6:02 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
>>
>> Hi all,
>>
>> Since yesterday, vdsm_master_verify-error-codes_created job is running
>> on master.
>>
>> I guess that this was a unintended change in jenkins - please revert this
>> change.
>>
>> If someone want to add a job for vdsm master, it must be approved by
>> vdsm maintainers first.
>>
>> The best would be to run everything from the automation scripts, so
>> vdsm maintainers have full control on the way patches are checked.
>>
>> Thanks,
>> Nir
>> _______________________________________________
>> Infra mailing list
>> Infra(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
>
> --
> Eyal Edri
> Associate Manager
> RHEV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)