jasder
/
antlr
1
0
Fork 1
Code Issues Pull Requests Releases 1 Wiki Activity
antlr/appveyor.yml

22 lines
1.3 KiB
YAML
Raw Normal View History

tweak appveyor to have correct version
2020-11-25 06:39:52 +08:00
version: '4.9.1-SNAPSHOT+AppVeyor.{build}'
Add cache entries to appveyor.yml. These cache the Maven and nuget package directories.
2017-10-29 05:45:34 +08:00
cache:
- '%USERPROFILE%\.m2'
- '%USERPROFILE%\.nuget\packages -> **\project.json'
tweak appveyor to have correct version
2020-11-25 06:39:52 +08:00
image: Visual Studio 2017
Fix the AppVeyor tests. For some reason, possibly the new images that AppVeyor rolled out on Oct 22, our AppVeyor tests now fail immediately, with msbuild complaining that there are multiple solutions in the repository. Address this by not using the default AppVeyor build section, but calling msbuild ourselves explicitly in the build_script section. This way, we can specify which .slns we want to build. I have specified the runtime and runtime-testsuite Antlr4.vs2013.slns; the other ones didn't work for me in this configuration. Also, these builds were previously running with low / zero logging. As far as I can tell, this gave AppVeyor no way to know whether the build has succeeded or not. It certainly gives no way to diagnose any failures that do occur. I have dialed the logging up on everything. Also, remove the os declaration. That appears to be well out of date, and isn't on AppVeyor's list of images any more. I presume that we've been using their default image for some time.
2017-10-25 15:07:23 +08:00
build: off
PHP Target
2019-09-14 20:36:37 +08:00
install:
- git submodule update --init --recursive
[PHP] Fix AppVeyor tests Install PHP to C:\tools\php. This fixes the AppVeyor tests, because they were looking in C:\tools\php73, but the Chocolatey package has recently moved to 7.4.
2019-12-18 01:53:59 +08:00
- cinst -y php --params "/InstallDir:C:\tools\php"
- cinst -y composer
pin dart version to 2.8.4 to get unit tests passing
2020-08-19 04:36:32 +08:00
- cinst -y dart-sdk --version=2.8.4
Appveyor w/ semantic version
2016-09-26 07:53:27 +08:00
build_script:
Fix the AppVeyor tests. For some reason, possibly the new images that AppVeyor rolled out on Oct 22, our AppVeyor tests now fail immediately, with msbuild complaining that there are multiple solutions in the repository. Address this by not using the default AppVeyor build section, but calling msbuild ourselves explicitly in the build_script section. This way, we can specify which .slns we want to build. I have specified the runtime and runtime-testsuite Antlr4.vs2013.slns; the other ones didn't work for me in this configuration. Also, these builds were previously running with low / zero logging. As far as I can tell, this gave AppVeyor no way to know whether the build has succeeded or not. It certainly gives no way to diagnose any failures that do occur. I have dialed the logging up on everything. Also, remove the os declaration. That appears to be well out of date, and isn't on AppVeyor's list of images any more. I presume that we've been using their default image for some time.
2017-10-25 15:07:23 +08:00
- mvn -DskipTests install --batch-mode
#2021 nuget artifact in appveyor
2017-11-12 21:30:50 +08:00
- msbuild /target:restore /target:rebuild /property:Configuration=Release /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:detailed runtime/CSharp/runtime/CSharp/Antlr4.dotnet.sln
Fix the AppVeyor tests. For some reason, possibly the new images that AppVeyor rolled out on Oct 22, our AppVeyor tests now fail immediately, with msbuild complaining that there are multiple solutions in the repository. Address this by not using the default AppVeyor build section, but calling msbuild ourselves explicitly in the build_script section. This way, we can specify which .slns we want to build. I have specified the runtime and runtime-testsuite Antlr4.vs2013.slns; the other ones didn't work for me in this configuration. Also, these builds were previously running with low / zero logging. As far as I can tell, this gave AppVeyor no way to know whether the build has succeeded or not. It certainly gives no way to diagnose any failures that do occur. I have dialed the logging up on everything. Also, remove the os declaration. That appears to be well out of date, and isn't on AppVeyor's list of images any more. I presume that we've been using their default image for some time.
2017-10-25 15:07:23 +08:00
- msbuild ./runtime-testsuite/target/classes/CSharp/runtime/CSharp/Antlr4.vs2013.sln /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:detailed
tweak appveyor to have correct version
2020-11-25 06:39:52 +08:00
after_build:
#2021 nuget artifact in appveyor
2017-11-12 21:30:50 +08:00
- msbuild /target:pack /property:Configuration=Release /verbosity:detailed runtime/CSharp/runtime/CSharp/Antlr4.dotnet.sln
Appveyor w/ semantic version
2016-09-26 07:53:27 +08:00
test_script:
fix appveyor build for es6
2020-10-10 22:42:00 +08:00
- mvn install -Dantlr-php-php="C:\tools\php\php.exe" -Dantlr-dart-dart="C:\tools\dart-sdk\bin\dart.exe" -Dantlr-dart-pub="C:\tools\dart-sdk\bin\pub.bat" -Dantlr-dart-dart2native="C:\tools\dart-sdk\bin\dart2native.bat" -Dantlr-python2-python="C:\Python27\python.exe" -Dantlr-python3-python="C:\Python35\python.exe" --batch-mode
#2021 nuget artifact in appveyor
2017-11-12 21:30:50 +08:00
artifacts:
tweak appveyor to have correct version
2020-11-25 06:39:52 +08:00
- path: 'runtime\**\*.nupkg'
#2021 nuget artifact in appveyor
2017-11-12 21:30:50 +08:00
name: NuGet