public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <sean.brogan@microsoft.com>
To: Purma, Kondal R <kondal.r.purma@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Tue, 11 Jun 2019 23:02:23 -0700	[thread overview]
Message-ID: <26138.1560319343440492230@groups.io> (raw)
In-Reply-To: <CDE22BE72013164481A002CCC5712FA0C787E573@ORSMSX108.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

Both of these RFCs listed flake8 because that is what we have today and it should be relatively easy to get parity.  I am super happy to have you add/propose/provide pr with additional test capability like Pylint.  Thats one of the goals of adding this to tianocore.

You can see what we are basing this on here:
https://dev.azure.com/projectmu/mu%20pip/_build?definitionId=10

And you can see how the build works in the Azure DevOps yaml file:
https://dev.azure.com/projectmu/mu%20pip/_apps/hub/ms.vss-build-web.ci-designer-hub?pipelineId=10&nonce=BIDKbQdfN9%2BmJevdri5mWw%3D%3D&branch=master ( https://dev.azure.com/projectmu/mu%20pip/_apps/hub/ms.vss-build-web.ci-designer-hub?pipelineId=10&nonce=BIDKbQdfN9%2BmJevdri5mWw%3D%3D&name=spbrogan&branch=master )

[-- Attachment #2: Type: text/html, Size: 952 bytes --]

  reply	other threads:[~2019-06-12  6:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  2:55 RFC for Edk2-ToolEnv Sean
2019-05-14  4:01 ` [edk2-devel] " rebecca
2019-05-14  7:37   ` Sean
2019-05-14 22:24     ` rebecca
2019-05-14 23:23       ` Sean
2019-05-14 23:34         ` rebecca
2019-05-23  2:39           ` Michael D Kinney
2019-05-23  6:46             ` Sean
2019-05-23 17:14               ` Michael D Kinney
2019-06-11 18:55                 ` Purma, Kondal R
2019-06-12  6:02                   ` Sean [this message]
2019-06-28 22:13                     ` Sean
2019-06-28 22: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=26138.1560319343440492230@groups.io \
    --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