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

9 lines
649 B
YAML
Raw Normal View History

Update AppVeyor version number to 4.7.1-SNAPSHOT.
2017-10-13 07:49:03 +08:00
version: '4.7.1-SNAPSHOT+AppVeyor.{build}'
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
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
- msbuild runtime/CSharp/runtime/CSharp/Antlr4.vs2013.sln /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:detailed
- msbuild ./runtime-testsuite/target/classes/CSharp/runtime/CSharp/Antlr4.vs2013.sln /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:detailed
Appveyor w/ semantic version
2016-09-26 07:53:27 +08:00
test_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 install -Dantlr-python2-python="C:\Python27\python.exe" -Dantlr-python3-python="C:\Python35\python.exe" -Dantlr-javascript-nodejs="C:\Program Files (x86)\nodejs\node.exe" --batch-mode