CI build for yosemitev2

[Velumani T-ERS,HCLTech]

Classification: Public
Hi Andrew,

Thanks for your response. I am working on the hardware CI for yosemitev2 and will keep you posted.

Can we enable build failure gating for yosemitev2 (not hardware CI) in the current system. Sometimes the new gerrit merges may cause build breaks to the YosemiteV2 machine.

Regards,
Velu

From: Andrew Geissler <geissonator at gmail.com>
Sent: Monday, January 4, 2021 6:57 AM
To: Velumani T-ERS,HCLTech <velumanit at hcl.com>
Cc: openbmc at lists.ozlabs.org; Patrick Williams <patrickw3 at fb.com>; Sai Dasari <sdasari at fb.com>; bradleyb at fuzziesquirrel.com
Subject: Re: CI build for yosemitev2

[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don't click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]



On Dec 21, 2020, at 9:32 AM, Velumani T-ERS,HCLTech <velumanit at hcl.com<mailto:velumanit at hcl.com>> wrote:

Classification: Public

Hi Andrew Geissler,

We have ported many features of openbmc to facebook/yosemitev2 machine and the build is verified from the openbmc/master working fine. Could you please help us to add the Yosemitev2 machine in the CI build verification. This will help us to ensure there are no build break during new patch push.

Hi Velumani, glad to see a new system added to openbmc!

Getting a new system into CI doesn't have the most defined process but
I think in general it has to fall under one of these due to our constraints
in compute power for CI[1]:

1) Propose an existing system in CI to replace (and the benefits of that)
2) Donate a jenkins compute node to openbmc CI
3) Convince the community that your system provides additional meta-*
    layer coverage (or some other critical benefit) that would be worth
    the additional hit to the existing CI infrastructure.

You could also look into hosting your own jenkins which builds
and scores the gerrit reviews. See this wiki for more info:
https://github.com/openbmc/openbmc/wiki/Adding-a-System-to-Hardware-Continuous-Integration<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fopenbmc%2Fwiki%2FAdding-a-System-to-Hardware-Continuous-Integration&data=04%7C01%7Cvelumanit%40hcl.com%7C7fe9662c2ab64877f21808d8b04fdbbd%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637453204330453150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2Fv6lgngN6gN6YNCpwwlP9UE0U3YcXj6Q1t7KpYnY08M%3D&reserved=0>

[1]: https://github.com/openbmc/openbmc/wiki/OpenBMC-Infrastructure-Workgroup#current-infrastructure<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fopenbmc%2Fwiki%2FOpenBMC-Infrastructure-Workgroup%23current-infrastructure&data=04%7C01%7Cvelumanit%40hcl.com%7C7fe9662c2ab64877f21808d8b04fdbbd%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637453204330453150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5xLzvnySyLNyGZzb1Ws1BvC0RzYF1QidXZLRngxzGys%3D&reserved=0>

Andrew



Regards,
Velu

::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210112/f21d8c87/attachment-0001.htm>