public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: rfc@edk2.groups.io, michael.d.kinney@intel.com,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	'Bret Barkelew' <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-rfc] [RFC] UnitTestFrameworkPkg cmocka submodule alternatives
Date: Thu, 17 Dec 2020 15:48:38 +0100	[thread overview]
Message-ID: <e7e23a40-668c-7d0c-6e0d-1559b063e819@redhat.com> (raw)
In-Reply-To: <BL0PR11MB323609CCD293B8B11C3FE8B2D2C50@BL0PR11MB3236.namprd11.prod.outlook.com>

On 12/16/20 19:45, Michael D Kinney wrote:
> Hello,
> 
> We have had at least three incidents in the last year where the link to the
> cmocka submodule in the UnitTestFrameworkPkg has not been available, and this
> impacted the EDK II CI system.  The following submodule link is the one that
> is not reliable:
> 
> 	https://git.cryptomilk.org/projects/cmocka.git
> 
> We have identified two potential mirrors of this repo:
> 
> 	https://github.com/neverware-mirrors/cmocka.git
> 	https://gitlab.com/cmocka/cmocka.git
> 
> The following patch provided a temporary fix for the EDK II CI agents, but
> does not help other consumers of the edk2 repository.
> 
> 	https://github.com/tianocore/edk2/commit/be746104d1766a8c363e74d6063144657820d688
> 
> I have seen one suggestion that TianoCore create its own
> mirror of cmocka.  This does require monitoring and maintenance
> by the  TianoCore community.  I would prefer to use a well
> maintained mirror in github as long as we do not observe any
> issues with the support of that mirror.
> 
> I propose we update the submodule in the UnitTestFrameworkPkg
> to use the https://github.com/neverware-mirrors/cmocka.git mirror.
> By using a mirror in github, we remove one external dependency.
> 
> Please provide feedback and comments on this proposal.  If there
> are no objections, then we will proceed with a patch review for
> this update.

We could create our own fork under the <https://github.com/tianocore>
organization.

It does not require much extra maintenance or monitoring, in my opinion.
We only need to advance our fork to the actual master HEAD when we
intend to advance our submodule reference in edk2 as well. As long as
the submodule reference in edk2 does not move, the actual master HEAD of
the cmocka project may very well be ahead of our fork (mirror), without
causing issues.

I don't know who or what the <https://github.com/neverware-mirrors>
organization is, and I'd prefer not fetching code from them automatically.

Thanks
Laszlo


  parent reply	other threads:[~2020-12-17 14:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 18:45 [RFC] UnitTestFrameworkPkg cmocka submodule alternatives Michael D Kinney
2020-12-17  0:58 ` 回复: [edk2-devel] " gaoliming
2020-12-17 14:48 ` Laszlo Ersek [this message]
2020-12-17 15:54   ` [edk2-rfc] " Laszlo Ersek
2020-12-17 16:01     ` Rebecca Cran
2020-12-17 18:44       ` [EXTERNAL] " Bret Barkelew
2020-12-19 18:58 ` Michael D Kinney
2020-12-19 19:07   ` Bret Barkelew
2020-12-20  1:06   ` [edk2-rfc] " Rebecca Cran
2020-12-21  1:18     ` 回复: [edk2-devel] " gaoliming
2020-12-21 20:14       ` Michael D Kinney
2020-12-21 20:42         ` Rebecca Cran
     [not found]         ` <1652D609A7BB8C97.24251@groups.io>
2020-12-21 20:44           ` Rebecca Cran
2020-12-22  0:41             ` 回复: " gaoliming
2021-02-15  0:43   ` [edk2-devel] " Rebecca Cran
2021-04-06 20:22     ` Michael D Kinney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7e23a40-668c-7d0c-6e0d-1559b063e819@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox