rocksdb/appveyordailytests.yml

version: 1.0.{build}
before_build:
- md %APPVEYOR_BUILD_FOLDER%\build
- cd %APPVEYOR_BUILD_FOLDER%\build
- cmake -G "Visual Studio 12 Win64" -DOPTDBG=1 ..
- cd ..
build:
  project: build\ALL_BUILD.vcxproj
  parallel: true
  verbosity: minimal
test:
test_script:
- ps: build_tools\run_ci_db_test.ps1
notifications:
  - provider: Email
    to:
      - svmtrocksdb@microsoft.com
    subject: "Build {{status}}"
    message: "{{message}}, {{commitId}}, ..."
    on_build_success: false
    on_build_failure: true
    on_build_status_changed: true
Improve CI build and build switches Add an optimized build config switch for faster test runs Change compiler options to introduce more opitmizations and be more inline with MS internal switches. Make appveyor build to utilize all the avaiable cores on the VM (parallel) Introduce new appveyor configuration for daily test runs as it would take too long to run db_test after each checkin even in paralell. With some exclusions we make it in 38 minutes. We currently fail to install ramdisk during the build. Add a powershell script to faicilitate paralell run for db_test cases. 9 years ago			`version: 1.0.{build}`
			`before_build:`
			`- md %APPVEYOR_BUILD_FOLDER%\build`
			`- cd %APPVEYOR_BUILD_FOLDER%\build`
			`- cmake -G "Visual Studio 12 Win64" -DOPTDBG=1 ..`
			`- cd ..`
			`build:`
			`project: build\ALL_BUILD.vcxproj`
			`parallel: true`
			`verbosity: minimal`
			`test:`
			`test_script:`
			`- ps: build_tools\run_ci_db_test.ps1`
Improve CI build and fix Windows build breakage Is there a way to enforce CMake additions for internal changes that seem to come w/o a PR? 9 years ago			`notifications:`
			`- provider: Email`
			`to:`
			`- svmtrocksdb@microsoft.com`
			`subject: "Build {{status}}"`
			`message: "{{message}}, {{commitId}}, ..."`
			`on_build_success: false`
			`on_build_failure: true`
			`on_build_status_changed: true`