aiden
/
depot_tools
mirror of https://chromium.googlesource.com/chromium/tools/depot_tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
chrome/4147
chrome/3987
chrome/3865
chrome/3904
infra/config
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6a1494e5d7'
${ noResults }
depot_tools/cipd.bat

68 lines
1.8 KiB
Batchfile
Raw Normal View History Unescape Escape

Add cipd bootstrap scripts to depot_tools. This takes advantage of powershell on windows for a cleanish duplicate of the posix version. R=dnj@chromium.org, vadimsh@chromium.org BUG=663843 Change-Id: Ib23a044ff912e3239b58848a26143eb6575826d5 Reviewed-on: https://chromium-review.googlesource.com/414228 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
9 years ago
@echo off
:: Copyright (c) 2016 The Chromium Authors. All rights reserved.
:: Use of this source code is governed by a BSD-style license that can be
:: found in the LICENSE file.
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
setlocal
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
set CIPD_BACKEND=https://chrome-infra-packages.appspot.com
set VERSION_FILE="%~dp0cipd_client_version"
set CIPD_BINARY="%~dp0.cipd_client.exe"
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
if not exist %CIPD_BINARY% (
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
call :CLEAN_BOOTSTRAP
goto :EXEC_CIPD
)
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
call :SELF_UPDATE >nul 2>&1
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
if %ERRORLEVEL% neq 0 (
echo CIPD client self-update failed, trying to bootstrap it from scratch... 1>&2
call :CLEAN_BOOTSTRAP
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
)
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
:EXEC_CIPD
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
if %ERRORLEVEL% neq 0 (
echo Failed to bootstrap or update CIPD client 1>&2
)
if %ERRORLEVEL% equ 0 (
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
"%CIPD_BINARY%" %*
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
)
Clear Zone.Identifier to allow depot_tools.zip bootstrap BUG=680274 Change-Id: I47fd8d7a5380aca49c873006c4f66732b21bee37 Reviewed-on: https://chromium-review.googlesource.com/427323 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
9 years ago
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
endlocal & (
[cipd] Do not rewrite ERRORLEVEL cipd.bat is called from bootstrap/win/win_tools.bat. ERRORLEVEL in win_tools.bat script should not mean return code of cipd.bat. Bug: none Change-Id: Ia425d5054fa9c1e1f84b4a10decc265669911646 Reviewed-on: https://chromium-review.googlesource.com/987954 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
8 years ago
set EXPORT_ERRORLEVEL=%ERRORLEVEL%
[cipd] Run client in .bat to preserve STDIN. Currently, the PowerShell execution does not allow STDIN to be read by the CIPD client. Fix this by using PowerShell to acquire the client, but batch to actually invoke the client. This removes some indirection and allows STDIN to function as expected. BUG=None TEST=local - Ran w/ and w/out ".cipd_client.exe" locally, observed install and fallthrough. - Ran w/ an error code, observed exit code being preserved. - Ran "auth-login", was able to paste token. Change-Id: I4efafa7dc80aa093de0fbf5dfd188c299fa104db Reviewed-on: https://chromium-review.googlesource.com/563602 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
8 years ago
)
[cipd] Do not rewrite ERRORLEVEL cipd.bat is called from bootstrap/win/win_tools.bat. ERRORLEVEL in win_tools.bat script should not mean return code of cipd.bat. Bug: none Change-Id: Ia425d5054fa9c1e1f84b4a10decc265669911646 Reviewed-on: https://chromium-review.googlesource.com/987954 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
8 years ago
exit /b %EXPORT_ERRORLEVEL%
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
:: Functions below.
::
:: See http://steve-jansen.github.io/guides/windows-batch-scripting/part-7-functions.html
:: if you are unfamiliar with this madness.
:CLEAN_BOOTSTRAP
:: To allow this powershell script to run if it was a byproduct of downloading
:: and unzipping the depot_tools.zip distribution, we clear the Zone.Identifier
:: alternate data stream. This is equivalent to clicking the "Unblock" button
:: in the file's properties dialog.
[cipd] Take cipd.ps1 out of %PATH%. Having it in %PATH% means that powershell users will accidentally run 'cipd.ps1' when they should be running 'cipd.bat'; This would cause them to get requests for input parameters (like the backend URL) which they have no idea how to supply. R=agable@chromium.org, nodir@chromium.org, vadimsh@google.com Bug: 1073529 Change-Id: I62a3bd9e00229a2047293dba1ba480d28f77bf63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2161645 Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Robbie Iannucci <iannucci@chromium.org>
6 years ago
echo.>%~dp0.cipd_impl.ps1:Zone.Identifier
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
powershell -NoProfile -ExecutionPolicy RemoteSigned ^
[cipd] Take cipd.ps1 out of %PATH%. Having it in %PATH% means that powershell users will accidentally run 'cipd.ps1' when they should be running 'cipd.bat'; This would cause them to get requests for input parameters (like the backend URL) which they have no idea how to supply. R=agable@chromium.org, nodir@chromium.org, vadimsh@google.com Bug: 1073529 Change-Id: I62a3bd9e00229a2047293dba1ba480d28f77bf63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/2161645 Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Auto-Submit: Robbie Iannucci <iannucci@chromium.org>
6 years ago
-Command "%~dp0.cipd_impl.ps1" ^
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
-CipdBinary "%CIPD_BINARY%" ^
-BackendURL "%CIPD_BACKEND%" ^
-VersionFile "%VERSION_FILE%" ^
<nul
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
if %ERRORLEVEL% equ 0 (
:: Need to call SELF_UPDATE to setup .cipd_version file.
call :SELF_UPDATE
)
exit /B %ERRORLEVEL%
:SELF_UPDATE
[cipd] Check CIPD client hash during updates on Windows. This is Windows counterpart to https://chromium-review.googlesource.com/1171957 Also cleanup code style in cipd.ps1 script. It appears the common convention for global variables in PowerShell is $GlobalVar and for locals is $localVar. R=nodir@chromium.org, iannucci@chromium.org BUG=870166 Change-Id: Ib8ffbad85497db31f7f5d44fdca6ed843e56f220 Reviewed-on: https://chromium-review.googlesource.com/1175248 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
7 years ago
"%CIPD_BINARY%" selfupdate ^
-version-file "%VERSION_FILE%" ^
-service-url "%CIPD_BACKEND%"
[cipd] Try to bootstrap CIPD from scratch if selfupdate fails. When updating the CIPD client to be identified by SHA256 hash, old clients (that have no idea about SHA256) fail during 'selfupdate'. We'll roll our SHA256 support in two stages: 1. Deploy new client that understand SHA256 using its SHA1 name, so self-update from old clients works. 2. Deploy same (or newer) client using its SHA256 name. This would work since the client doing the self-update already understands SHA256 at this point. But we can't guarantee that ALL depot_tools deployments will update through stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly in (2), failing on 'selfupdate'. This CL makes sure they can recover from this state by rebootstraping the client from scratch (this works with SHA256 hashes). R=nodir@chromium.org, iannucci@chromium.org BUG=821194 Change-Id: I27dece19e0305b5b2d6f8b0130631c1bf5f6499c Reviewed-on: https://chromium-review.googlesource.com/1149454 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
7 years ago
exit /B %ERRORLEVEL%