From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv To: Rebecca Cran ,devel@edk2.groups.io From: "Sean" X-Originating-IP: 50.47.106.228 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 14 May 2019 16:23:18 -0700 References: In-Reply-To: Message-ID: <24730.1557876198223366119@groups.io> Content-Type: multipart/alternative; boundary="8219DPboLk1uHQIWAhSD" --8219DPboLk1uHQIWAhSD Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Take a look at the proposed content and how it is used.=C2=A0 We even have = examples of calling from DevOps and i don't think Jenkins would be any diff= erent.=C2=A0 I don't think we are trying to duplicate CI functionality.=C2= =A0 We are providing the "last mile" so that those CI engines can run EDK = specific tests and tools.=C2=A0 Standard CI engines have no concept of pack= ages, DSC, FDF, INFs, firmware, etc. --8219DPboLk1uHQIWAhSD Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Take a look at the proposed content and how it is used.  We even have = examples of calling from DevOps and i don't think Jenkins would be any diff= erent.  I don't think we are trying to duplicate CI functionality.&nbs= p; We are providing the "last mile" so that those CI engines can run EDK sp= ecific tests and tools.  Standard CI engines have no concept of packag= es, DSC, FDF, INFs, firmware, etc.   --8219DPboLk1uHQIWAhSD--