Commit Graph

24 Commits

Author SHA1 Message Date
parrt 86610fd4b4 tweak appveyor to have correct version 2020-11-24 14:39:52 -08:00
Eric Vergnaud a741dba79f fix appveyor build for es6 2020-10-10 22:42:00 +08:00
Eric Vergnaud 21cb5df94f fix appveyor build for es6 2020-10-10 22:26:36 +08:00
Eric Vergnaud 654b92779c Disable Node tests in AppVeyor for now 2020-10-10 14:38:32 +08:00
Eric Vergnaud 76355cebbf fix appveyor build of es6 2020-10-10 12:43:13 +08:00
Eric Vergnaud 12c4bcc408 fix appveyor for es6 2020-10-10 12:28:17 +08:00
Eric Vergnaud d622c53b04 fix appveyor for es6 2020-10-10 11:12:58 +08:00
Eric Vergnaud 40b9d4503d fix appveyor build of es6 2020-10-10 10:22:59 +08:00
Larry Li c8571060f0 pin dart version to 2.8.4 to get unit tests passing 2020-08-19 06:36:32 +10:00
Larry Li 37d4336035 fix appveyor 2020-01-20 21:26:21 +11:00
Larry Li 2a15af7579 fix appveyor 2020-01-20 00:23:22 +11:00
Ewan Mellor ce59e171cb
[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-17 09:53:59 -08:00
Marcos Passos 789d746636 PHP Target 2019-09-14 09:39:58 -03:00
Rostislav Listerenko 9ec6c665d5 #2021 nuget artifact in appveyor 2017-11-13 08:47:15 +03:00
Ewan Mellor a465f777ea
Add cache entries to appveyor.yml.
These cache the Maven and nuget package directories.
2017-10-29 11:50:14 -07:00
Ewan Mellor e90662ba10
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 12:03:32 -07:00
Ewan Mellor 0097838b8a
Update AppVeyor version number to 4.7.1-SNAPSHOT. 2017-10-12 16:49:03 -07:00
Terence Parr 11bcd168fb Update appveyor.yml 2016-11-21 14:40:46 -08:00
Terence Parr d6f95111fc Update appveyor.yml 2016-11-21 14:39:20 -08:00
Burt Harris 80a75894c8 eliminte trailing whitespace
from last line of appvayor.yml
2016-09-26 15:37:50 -07:00
Burt Harris 7ebfabc175 Addomg verbosity: minimal fpr appveyor 2016-09-26 08:39:59 -07:00
Burt Harris e71ebef3ec Adding -q to mvn command line for appveyor 2016-09-26 08:28:52 -07:00
Burt Harris 7e2213dde7 appveyor.yml cpaitialization 2016-09-25 19:26:49 -07:00
Burt Harris d9047112f5 Appveyor w/ semantic version 2016-09-25 16:53:27 -07:00