Browse Source

Remove unused and failing script (#5220)

* Remove unused and failing script

* Removing/changing other pointers to 'hctcheckin'
Brian Favela 2 years ago
parent
commit
2bd4ee7ca4
5 changed files with 3 additions and 51 deletions
  1. 1 1
      CONTRIBUTING.md
  2. 2 2
      README.md
  3. 0 46
      utils/hct/hctcheckin.cmd
  4. 0 1
      utils/hct/hcthelp.cmd
  5. 0 1
      utils/hct/hctstart.cmd

+ 1 - 1
CONTRIBUTING.md

@@ -34,7 +34,7 @@ You will need to complete a Contributor License Agreement (CLA) before your pull
 
 
 You can complete the CLA by going through the steps at the [Contribution License Agreement site](https://cla.microsoft.com). Once we have received the signed CLA, we'll review the request. You will only need to do this once.
 You can complete the CLA by going through the steps at the [Contribution License Agreement site](https://cla.microsoft.com). Once we have received the signed CLA, we'll review the request. You will only need to do this once.
 
 
-Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests. The hctcheckin command is your friend.
+Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests. The hcttest command is your friend.
 
 
 Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the team, and only those that meet an extremely high bar for both quality and design/roadmap appropriateness will be merged into the source.
 Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the team, and only those that meet an extremely high bar for both quality and design/roadmap appropriateness will be merged into the source.
 
 

+ 2 - 2
README.md

@@ -82,9 +82,9 @@ To build, run this command on the HLSL Console.
 
 
     hctbuild
     hctbuild
 
 
-You can also clean, build and run tests with this command.
+You can also run tests with this command.
 
 
-    hctcheckin
+    hcttest
 
 
 
 
 To see a list of additional commands available, run `hcthelp`
 To see a list of additional commands available, run `hcthelp`

+ 0 - 46
utils/hct/hctcheckin.cmd

@@ -1,46 +0,0 @@
-@echo off
-
-if "%1"=="/?" goto :showhelp
-if "%1"=="-?" goto :showhelp
-if "%1"=="-help" goto :showhelp
-if "%1"=="--help" goto :showhelp
-
-if "%HLSL_SRC_DIR%"=="" (
-  echo Missing source directory - consider running hctstart.
-  exit /b 1
-)
-
-setlocal ENABLEDELAYEDEXPANSION
-
-echo Running hctcheckin for the current architecture.
-
-call %HLSL_SRC_DIR%\utils\hct\hctclean.cmd
-if errorlevel 1 (
-  echo Failed to clean binaries, stopping hctcheckin.
-  exit /b 1
-)
-call %HLSL_SRC_DIR%\utils\hct\hctbuild.cmd -parallel
-if errorlevel 1 (
-  echo Failed to build binaries, stopping hctcheckin.
-  exit /b 1
-)
-
-call %HLSL_SRC_DIR%\utils\hct\hcttest.cmd
-if errorlevel 1 (
-  echo Failed to test binaries, stopping hctcheckin.
-  exit /b 1
-)
-
-echo Ready to check in.
-cscript //Nologo %HLSL_SRC_DIR%\utils\hct\hctspeak.js /say:"checkin tasks successfully completed"
-
-endlocal
-
-goto :eof
-
-:showhelp
-echo Runs the clean, build and test steps.
-echo.
-echo hctcheckin
-echo.
-goto :eof

+ 0 - 1
utils/hct/hcthelp.cmd

@@ -3,7 +3,6 @@ echo HLSL console tools
 echo.
 echo.
 echo   hctbld       - sets the current directory to HLSL_BLD_DIR
 echo   hctbld       - sets the current directory to HLSL_BLD_DIR
 echo   hctbuild     - builds the product and test binaries
 echo   hctbuild     - builds the product and test binaries
-echo   hctcheckin   - builds and tests to make sure a checkin is good
 echo   hcthelp      - prints this help message
 echo   hcthelp      - prints this help message
 echo   hctspeak     - says something - useful to call out after a long command
 echo   hctspeak     - says something - useful to call out after a long command
 echo   hctshortcut  - creates a desktop shortcut
 echo   hctshortcut  - creates a desktop shortcut

+ 0 - 1
utils/hct/hctstart.cmd

@@ -60,7 +60,6 @@ echo Setting up macros for this console - run hcthelp for a reference.
 echo.
 echo.
 doskey hctbld=pushd %HLSL_BLD_DIR%
 doskey hctbld=pushd %HLSL_BLD_DIR%
 doskey hctbuild=%HLSL_SRC_DIR%\utils\hct\hctbuild.cmd $*
 doskey hctbuild=%HLSL_SRC_DIR%\utils\hct\hctbuild.cmd $*
-doskey hctcheckin=%HLSL_SRC_DIR%\utils\hct\hctcheckin.cmd $*
 doskey hctclean=%HLSL_SRC_DIR%\utils\hct\hctclean.cmd $*
 doskey hctclean=%HLSL_SRC_DIR%\utils\hct\hctclean.cmd $*
 doskey hcthelp=%HLSL_SRC_DIR%\utils\hct\hcthelp.cmd $*
 doskey hcthelp=%HLSL_SRC_DIR%\utils\hct\hcthelp.cmd $*
 doskey hctshortcut=cscript.exe //Nologo %HLSL_SRC_DIR%\utils\hct\hctshortcut.js $*
 doskey hctshortcut=cscript.exe //Nologo %HLSL_SRC_DIR%\utils\hct\hctshortcut.js $*