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>,
	"Zhang, Shenglei" <shenglei.zhang@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Update CI steps
Date: Fri, 3 Apr 2020 04:37:40 +0000	[thread overview]
Message-ID: <f2060e746144460a99c01aa67db369dd@intel.com> (raw)
In-Reply-To: <20200401082442.22596-1-shenglei.zhang@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Zhang, Shenglei
> Sent: Wednesday, April 1, 2020 4:25 PM
> To: devel@edk2.groups.io
> Cc: Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: [edk2-devel] [PATCH] .azurepipelines: Update CI steps
> 
> From: Sean Brogan <sean.brogan@microsoft.com>
> 
> Update CI steps to build base tools after setup and update,
> as basetools might have dependencies that need to be resolved.
> 
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
> ---
>  .azurepipelines/templates/pr-gate-steps.yml | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/.azurepipelines/templates/pr-gate-steps.yml b/.azurepipelines/templates/pr-gate-steps.yml
> index a969661dea15..3fcc1e88d804 100644
> --- a/.azurepipelines/templates/pr-gate-steps.yml
> +++ b/.azurepipelines/templates/pr-gate-steps.yml
> @@ -39,11 +39,6 @@ steps:
>      arguments: -c .pytool/CISettings.py -p ${{ parameters.build_pkgs }} --pr-target origin/$(System.PullRequest.targetBranch) --output-
> csv-format-string "##vso[task.setvariable variable=pkgs_to_build;isOutpout=true]{pkgcsv}" --output-count-format-string
> "##vso[task.setvariable variable=pkg_count;isOutpout=true]{pkgcount}"
>    condition: eq(variables['Build.Reason'], 'PullRequest')
> 
> -# build basetools
> -- template: basetools-build-steps.yml
> -  parameters:
> -    tool_chain_tag: ${{ parameters.tool_chain_tag }}
> -
>  # install spell check prereqs
>  - template: spell-check-prereq-steps.yml
> 
> @@ -62,6 +57,13 @@ steps:
>      arguments: -c .pytool/CISettings.py -p $(pkgs_to_build) -t ${{ parameters.build_targets}} -a ${{ parameters.build_archs}}
> TOOL_CHAIN_TAG=${{ parameters.tool_chain_tag}}
>    condition: and(gt(variables.pkg_count, 0), succeeded())
> 
> +# build basetools
> +#   do this after setup and update so that code base dependencies
> +#   are all resolved.
> +- template: basetools-build-steps.yml
> +  parameters:
> +    tool_chain_tag: ${{ parameters.tool_chain_tag }}
> +
>  - task: CmdLine@1
>    displayName: Build and Test ${{ parameters.build_pkgs }} ${{ parameters.build_archs}}
>    inputs:
> --
> 2.18.0.windows.1
> 
> 
> 


      reply	other threads:[~2020-04-03  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  8:24 [PATCH] .azurepipelines: Update CI steps Zhang, Shenglei
2020-04-03  4:37 ` Liming Gao [this message]

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=f2060e746144460a99c01aa67db369dd@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