Thanks Andy for the answers. You can find my answers & comments below. Hope this helps BR Guillaume
-----Message d'origine----- De : Andrew Grimberg <agrimb...@linuxfoundation.org> Envoyé : mercredi 15 novembre 2023 15:27 À : LAMBERT Guillaume INNOV/NET <guillaume.lamb...@orange.com>; Robert Varga <n...@hq.sk>; OpenDaylight Discuss <discuss@lists.opendaylight.org>; OpenDaylight Dev <d...@lists.opendaylight.org>; t...@lists.opendaylight.org Objet : Re: [OpenDaylight TSC] Gerrit verify changes On 11/14/23 07:50, guillaume.lamb...@orange.com wrote: --[snip]-- > > Note the relation chain of > > https://git.opendaylight.org/gerrit/c/transportpce/+/108417 blocked by > > Jenkins poor SLA at the moment it was pushed. > > It is now ready but we ended up with this particular change that was > > ready before the migration and that is not mergeable anymore because of the > > absence of the GHA verified +1 It now that blocks the rest of the chain... > Please note that 'recheck' and 'remerge' comment triggers work on the GHA > jobs as well, including the required one. I just did a 'recheck' on your > linked change and it passed the GHA in less than a minute. As such, this > change is now unblocked, though Jenkins did remove its vote as it restarted > it's verify job, but I > see that you voted a Verified+1 so it's still > submittable. Noticed. It seems to work quite well. Thank you for having taken care of it. Do you think it would be possible to create a specific trigger similar to "recheck" only for GHA to avoid relaunching all Jenkins job ? > > What are the guarantees that the GHA SLA be better ? > > If not, it will just worsen this kind of issue. > We can't give an SLA on another vendors system outside of what they already > offer. What we can state is that in general jobs are more responsive and > faster. That being said, just like any CI system, they run into issues. I > know y'all don't usually see to many with Jenkins and we know that GHA tends > to have a bit > >more stability issues than our Jenkins setups, it is on the > whole a better CI platform for most types of jobs given the following: > * quick job response > * large catalog of pre-made actions that can be utilized > * easy ability to put many portions of workflows into a parallel job > configuration > * Workflows live with the repository itself instead of in a separate repo > (thought this does mean that you can end up with conformance drift across > projects but that can be mitigated with: > * Resuable workflows work very similar to JJB templates allowing > standardization of jobs but with the flexibility of keeping some jobs on > older versions if needed Thanks for this precious feedback. I understand there is a good chance it may improve the situation, which is good news. Though, I don't think it changes the problem underneath. If the SLA cannot be guaranteed, we still may face downtimes. And with such an enforcement on GHA verified +1 , there would be no way for committers to force a merge, even if they performed all tests locally to ensure it is safe. Personally, for this sole reason, I am reluctant to migrate all jobs from Jenkins to GHA. But anyway, let's assume we do it. Is there any pointer on how to migrate current Jenkins profile to GHA ? As you may know, we intensively use the tox profile since tox offers a convenient portable solution that allows us to do concurrency. >-Andy- -- Andrew J Grimberg Senior Manager, Release Engineering The Linux Foundation NOTICE: The Linux Foundation supports their employees with flexible work hours. If you recieve mail from me outside of standard business hours please be aware that I do not expect a response until the next standard business day. ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9036): https://lists.opendaylight.org/g/Discuss/message/9036 Mute This Topic: https://lists.opendaylight.org/mt/102585993/21656 Group Owner: discuss+ow...@lists.opendaylight.org Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
