kc3-lang/libevent/appveyor.yml

Branch :


Log

Author Commit Date CI Message
9b63b5d4 2017-01-22 18:21:57 Bump version to 2.1.8-stable everywhere P.S. in referenced commit I made a mistake and instead of *-rc* I wrote *-beta*. See-also: f4489b8323cda0bf8eed7c1353911a852d7a947c ("Bump version to 2.1.7-beta everywhere")
108b5fef 2017-01-20 16:31:17 Run tests in parallel (they are lightweight), on CI and vagrant boxes By default 20 parllel jobs, but one caveat for travis-ci, osx boxes there slower and have less resources then linux (discovered during testing), so limit number of parallel jobs to 4 there, and also install travis_wait, so that travis-ci will not fail the build when there is no output for 10 minutes, since for osx boxes it is very likely. Refs: travis-ci/travis-ci@7202
f4489b83 2016-11-02 00:31:31 Bump version to 2.1.7-beta everywhere - cmake basic - cmake detecting from git -- event_fuzzy_version_from_git() - autotools - win32 - appveyor
51019e94 2016-07-13 17:40:48 Bump version to 2.1.6-beta everywhere - cmake basic - cmake detecting from git -- event_fuzzy_version_from_git() - autotools - win32 - appveyor
6fcfa25d 2016-08-08 17:25:11 appveyor/autotools: link with openssl by passing LDFLAGS/CFLAGS This never works, hence green tests in production. and now it works: https://ci.appveyor.com/project/azat/libevent/build/2.1.5.100/job/eib4xqfb7d3ruo16 (look by /"evthread_win32.c")
4634b85b 2016-08-08 15:34:57 appveyor: image already had openssl installed Fixes messages like "Version mismatch for openssl: compiled with 1000201f but running with 1000208f" [1]. According to next link: http://help.appveyor.com/discussions/questions/1132-openssl-installation-issues Refs: appveyor/ci#576 [1]: https://ci.appveyor.com/project/azat/libevent/build/2.1.5.95/job/dcy9cfoj3rfo4gdh
e9acc441 2016-08-07 23:51:21 appveyor: check -DUNICODE -D_UNICODE according to ReleaseChecklist (cmake only) Link: https://github.com/libevent/libevent/wiki/ReleaseChecklist
18108574 2016-08-07 21:30:04 appveyor: ignore failure of mingw-get Since according to doc [1], appveyour will fail the build on every powershell's exception: "PowerShell script is considered successful if it finishes without exception." [1]: https://www.appveyor.com/docs/build-configuration#powershell
ac90133c 2016-08-07 20:52:41 appveyor: drop shallow_clone, since we use tags for detecting version in cmake
8f950155 2016-06-19 14:15:41 appveyor: support cmake & autotools using build matrix (like travis-ci has) This will allow us to avoid possible compilation regressions, and also some failures in different environments (for example because of different sizeof(size_t)). For example we can avoid next issues: - #361 - #314 - #311 (And I'm pretty sure that this is not complete list) And of course it reduce job for maintainers. But it also have one downside, appveyor doesn't have such concurrency like travis-ci, so it can take a while to finish the whole build, but we can resolve this later, or reduce build matrix to only one for autotools and one for cmake. Fixes: #364
1cc2e295 2015-05-12 00:27:01 Use autotools for appveyor until cmake is fixed.
107d565d 2015-05-11 12:47:40 Fix the link for appveyor OpenSSL installer (WIN32) * change and move the openssl self installer off to a site we own - the old link was 404, probably due to being replaced with a newer non-vuln version. But since we are only using this installer to auto-build with on appveyor (not as a release), then having a file we don't change and own seems to be a better solution. * reduce verbosity
26164a56 2015-02-05 20:21:04 Forgot to install OpenSSL for appveyor
5f89c37e 2015-02-05 19:24:19 Add support for appveyor.com windows CI This does the same thing as Travis-CI but for windows. @nmathewson Go to: https://ci.appveyor.com/login -> Login using Github Click **+New Project** -> Choose **Github** to the left -> Find **Libevent** in the list and click **Add**