public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Andrew Fish <afish@apple.com>, Laszlo Ersek <lersek@redhat.com>,
	"Leif Lindholm" <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [Patch v3 22/22] Readme.md: Add CI build status badges
Date: Wed, 6 Nov 2019 00:21:11 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E537E8A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191029195517.20028-23-michael.d.kinney@intel.com>

Mike:
  How to know Ubuntu OS version?

Thanks
Liming
>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>Michael D Kinney
>Sent: Wednesday, October 30, 2019 3:55 AM
>To: devel@edk2.groups.io
>Cc: Andrew Fish <afish@apple.com>; Laszlo Ersek <lersek@redhat.com>; Leif
>Lindholm <leif.lindholm@linaro.org>
>Subject: [edk2-devel] [Patch v3 22/22] Readme.md: Add CI build status
>badges
>
>https://bugzilla.tianocore.org/show_bug.cgi?id=2315
>
>Update Readme.md with status badges from the most recent
>EDK II Continuous Integration(CI) build.
>
>Cc: Andrew Fish <afish@apple.com>
>Cc: Laszlo Ersek <lersek@redhat.com>
>Cc: Leif Lindholm <leif.lindholm@linaro.org>
>Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
>---
> Readme.md | 29 ++++++++++++++++++++++-------
> 1 file changed, 22 insertions(+), 7 deletions(-)
>
>diff --git a/Readme.md b/Readme.md
>index 27e4ce0771..37183c3265 100644
>--- a/Readme.md
>+++ b/Readme.md
>@@ -3,6 +3,19 @@
> A modern, feature-rich, cross-platform firmware development environment
> for the UEFI and PI specifications from www.uefi.org.
>
>+## Build Status
>+
>+| Host Type | Toolchain | Branch | Build Status | Test Status | Code Coverage
>|
>+| :-------- | :-------- | :---- | :----- | :---- | :--- |
>+| Windows | VS2019 | master | [![Build
>Status](https://dev.azure.com/tianocore/edk2-ci-
>play/_apis/build/status/Edk2%20Windows%20VS2019%20CI?branchName=m
>aster)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=14&branchName=master) | [![Azure DevOps
>tests](https://img.shields.io/azure-devops/tests/tianocore/edk2-ci-
>play/14.svg)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=14&branchName=master) | [![Code
>Coverage](https://img.shields.io/badge/coverage-coming_soon-
>blue)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=14&branchName=master)|
>+| Ubuntu | GCC5 | master | [![Build
>Status](https://dev.azure.com/tianocore/edk2-ci-
>play/_apis/build/status/Edk2%20Ubuntu%20GCC5%20CI?branchName=maste
>r)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=15&branchName=master) | [![Azure DevOps
>tests](https://img.shields.io/azure-devops/tests/tianocore/edk2-ci-
>play/15.svg)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=15&branchName=master)  | [![Code
>Coverage](https://img.shields.io/badge/coverage-coming_soon-
>blue)](https://dev.azure.com/tianocore/edk2-ci-
>play/_build/latest?definitionId=15&branchName=master) |
>+
>+[More CI Build information](ci/readme.md)
>+
>+## License Details
>+
>+[![License](https://img.shields.io/badge/license-BSD--2--Clause--Patent-
>blue)](License.txt)
>+
> The majority of the content in the EDK II open source project uses a
> [BSD-2-Clause Plus Patent License](License.txt).  The EDK II open source
>project
> contains the following components that are covered by additional licenses:
>@@ -20,7 +33,8 @@ contains the following components that are covered by
>additional licenses:
> The EDK II Project is composed of packages.  The maintainers for each
>package
> are listed in [Maintainers.txt](Maintainers.txt).
>
>-# Resources
>+## Resources
>+
> * [TianoCore](http://www.tianocore.org)
> * [EDK II](https://github.com/tianocore/tianocore.github.io/wiki/EDK-II)
> * [Getting Started with EDK
>II](https://github.com/tianocore/tianocore.github.io/wiki/Getting-Started-
>with-EDK-II)
>@@ -29,7 +43,8 @@ are listed in [Maintainers.txt](Maintainers.txt).
> * [How To
>Contribute](https://github.com/tianocore/tianocore.github.io/wiki/How-To-
>Contribute)
> * [Release
>Planning](https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-
>Release-Planning)
>
>-# Code Contributions
>+## Code Contributions
>+
> To make a contribution to a TianoCore project, follow these steps.
> 1. Create a change description in the format specified below to
>    use in the source control commit log.
>@@ -57,7 +72,7 @@ To make a contribution to a TianoCore project, follow
>these steps.
>    Contributions using other licenses might be accepted, but further
>    review will be required.
>
>-# Developer Certificate of Origin
>+## Developer Certificate of Origin
>
> Your change description should use the standard format for a
> commit message, and must include your `Signed-off-by` signature.
>@@ -104,7 +119,7 @@ By making a contribution to this project, I certify that:
>     this project or the open source license(s) involved.
> ```
>
>-# Sample Change Description / Commit Message
>+## Sample Change Description / Commit Message
>
> ```
> From: Contributor Name <contributor@example.com>
>@@ -115,14 +130,14 @@ Full-commit-message
> Signed-off-by: Contributor Name <contributor@example.com>
> ```
>
>-## Notes for sample patch email
>+### Notes for sample patch email
>
> * The first line of commit message is taken from the email's subject
>   line following `[Repository/Branch PATCH]`. The remaining portion of the
>   commit message is the email's content.
> * `git format-patch` is one way to create this format
>
>-## Definitions for sample patch email
>+### Definitions for sample patch email
>
> * `Repository` is the identifier of the repository the patch applies.
>   This identifier should only be provided for repositories other than
>@@ -141,7 +156,7 @@ Signed-off-by: Contributor Name
><contributor@example.com>
> * `Signed-off-by` is the contributor's signature identifying them
>   by their real/legal name and their email address.
>
>-# Submodules
>+## Submodules
>
> Submodule in EDK II is allowed but submodule chain should be avoided
> as possible as we can. Currently EDK II contains two submodules
>--
>2.21.0.windows.1
>
>
>


  parent reply	other threads:[~2019-11-06  0:21 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 19:54 [Patch v3 00/22] Enable Phase 1 of EDK II CI Michael D Kinney
2019-10-29 19:54 ` [Patch v3 01/22] Maintainers.txt: Add continuous integration(CI) directories Michael D Kinney
2019-10-30  2:34   ` Leif Lindholm
2019-10-31  9:03     ` Laszlo Ersek
2019-10-29 19:54 ` [Patch v3 02/22] .gitignore: Ignore python compiled files, extdeps, and vscode Michael D Kinney
2019-10-30  2:29   ` Leif Lindholm
2019-10-31  4:43     ` Michael D Kinney
2019-10-31  9:02       ` Laszlo Ersek
2019-11-04 16:02         ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-29 19:54 ` [Patch v3 03/22] requirements.txt: Add python pip requirements file Michael D Kinney
2019-10-30  2:27   ` Leif Lindholm
2019-10-30  2:52     ` [edk2-devel] " Sean
2019-10-30  3:03       ` Leif Lindholm
2019-10-31  4:39         ` Michael D Kinney
2019-10-31  4:58           ` Leif Lindholm
2019-10-31  7:18             ` Sean
2019-10-31  8:59     ` Laszlo Ersek
2019-10-29 19:54 ` [Patch v3 04/22] BaseTools/tools_def.template: Add RC_PATH define Michael D Kinney
2019-11-05  8:18   ` Liming Gao
2019-11-07  0:32     ` Michael D Kinney
2019-10-29 19:55 ` [Patch v3 05/22] BaseTools: Add YAML files with path env and tool extdeps Michael D Kinney
2019-10-29 19:55 ` [Patch v3 06/22] BaseTools: Add BaseTools plugins to support CI Michael D Kinney
2019-10-29 19:55 ` [Patch v3 07/22] .pytool/Plugin: Add CI plugins Michael D Kinney
2019-10-29 19:55 ` [Patch v3 08/22] CryptoPkg: Add YAML file for CI builds Michael D Kinney
2019-10-29 19:55 ` [Patch v3 09/22] FatPkg: " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 10/22] FmpDevicePkg: " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 11/22] MdeModulePkg: " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 12/22] MdePkg: " Michael D Kinney
2019-11-05  8:22   ` Liming Gao
2019-11-05 17:04     ` Michael D Kinney
2019-11-06  0:20       ` Liming Gao
2019-11-06  0:29         ` Michael D Kinney
2019-10-29 19:55 ` [Patch v3 13/22] NetworkPkg: " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 14/22] PcAtChipsetPkg: Add YAML files " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 15/22] SecurityPkg: " Michael D Kinney
2019-10-29 19:55 ` [Patch v3 16/22] ShellPkg: Add YAML file " Michael D Kinney
2019-11-05  2:19   ` Gao, Zhichao
2019-10-29 19:55 ` [Patch v3 17/22] UefiCpuPkg: " Michael D Kinney
2019-10-31  8:55   ` Laszlo Ersek
2019-10-29 19:55 ` [Patch v3 18/22] SignedCapsulePkg: Use BaseCryptLibNull to reduce package CI time Michael D Kinney
2019-11-05  8:23   ` [edk2-devel] " Liming Gao
2019-11-05 17:05     ` Michael D Kinney
2019-10-29 19:55 ` [Patch v3 19/22] .pytool: Add CISettings.py and Readme.md Michael D Kinney
2019-10-29 19:55 ` [Patch v3 20/22] .azurepipelines: Add Azure Pipelines YML configuration files Michael D Kinney
2019-10-29 19:55 ` [Patch v3 21/22] .merify: Add Megify YML pull request rules configuration file Michael D Kinney
2019-10-29 19:55 ` [Patch v3 22/22] Readme.md: Add CI build status badges Michael D Kinney
2019-10-30  2:58   ` Leif Lindholm
2019-10-31  4:42     ` Michael D Kinney
2019-11-06  0:21   ` Liming Gao [this message]
2019-11-06  0:34     ` [edk2-devel] " Michael D Kinney
2019-10-31  9:54 ` [edk2-devel] [Patch v3 00/22] Enable Phase 1 of EDK II CI Laszlo Ersek
2019-11-01  5:03   ` Michael D Kinney
2019-11-01 22:39     ` Laszlo Ersek
2019-11-01 23:22       ` Laszlo Ersek
2019-11-02  0:32       ` Michael D Kinney
2019-11-02 10:49         ` Laszlo Ersek

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E537E8A@SHSMSX104.ccr.corp.intel.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