kmx git

Commit	Date	Message
29cc8386	2018-08-18T23:50:10	appveyor: add all build tree into artifacts in case of failure This will help in investigations of win32 failures... P.S. looks like there is no better way, since "artifacts.*.publish_on_failure" hadn't been implemented yet (while was requiested in 2015).
bdd53128	2018-08-01T03:01:43	appveyor: disable almost all configurations (except autotools/cmake basic) Since we have FREE plan, we have a lot of limits on our builds, so let's reduce their amount to make them run/start faster (I hope).
e01b9937	2017-03-08T23:48:30	appveyor: remove -DEVENT__ENABLE_VERBOSE_DEBUG=ON build See-also: c199df7bc78824ff579ff34c5f9f922034e8fa31 ("travis-ci: remove -DEVENT__ENABLE_VERBOSE_DEBUG=ON (too much useless logs)")
efcfa046	2017-01-29T18:13:07	Bump version in master to 2.2.0-alpha-dev And according to f8d80a285cf941505277d9060d0357b5b7e543d2 ("Bump version to 2.1.3-alpha-dev") numeric version have 1 at the end, since it means "-dev".
9b63b5d4	2017-01-22T18: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-20T16: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-02T00: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-13T17: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-08T17: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-08T15: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-07T23:51:21	appveyor: check -DUNICODE -D_UNICODE according to ReleaseChecklist (cmake only) Link: https://github.com/libevent/libevent/wiki/ReleaseChecklist
18108574	2016-08-07T21: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-07T20:52:41	appveyor: drop shallow_clone, since we use tags for detecting version in cmake
8f950155	2016-06-19T14: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-12T00:27:01	Use autotools for appveyor until cmake is fixed.
107d565d	2015-05-11T12: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-05T20:21:04	Forgot to install OpenSSL for appveyor
5f89c37e	2015-02-05T19: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

29cc8386

2018-08-18T23:50:10

appveyor: add all build tree into artifacts in case of failure This will help in investigations of win32 failures... P.S. looks like there is no better way, since "artifacts.*.publish_on_failure" hadn't been implemented yet (while was requiested in 2015).

bdd53128

2018-08-01T03:01:43

appveyor: disable almost all configurations (except autotools/cmake basic) Since we have FREE plan, we have a lot of limits on our builds, so let's reduce their amount to make them run/start faster (I hope).

e01b9937

2017-03-08T23:48:30

appveyor: remove -DEVENT__ENABLE_VERBOSE_DEBUG=ON build See-also: c199df7bc78824ff579ff34c5f9f922034e8fa31 ("travis-ci: remove -DEVENT__ENABLE_VERBOSE_DEBUG=ON (too much useless logs)")

efcfa046

2017-01-29T18:13:07

Bump version in master to 2.2.0-alpha-dev And according to f8d80a285cf941505277d9060d0357b5b7e543d2 ("Bump version to 2.1.3-alpha-dev") numeric version have 1 at the end, since it means "-dev".

9b63b5d4

2017-01-22T18: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-20T16: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-02T00: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-13T17: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-08T17: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-08T15: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-07T23:51:21

appveyor: check -DUNICODE -D_UNICODE according to ReleaseChecklist (cmake only) Link: https://github.com/libevent/libevent/wiki/ReleaseChecklist

18108574

2016-08-07T21: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-07T20:52:41

appveyor: drop shallow_clone, since we use tags for detecting version in cmake

8f950155

2016-06-19T14: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-12T00:27:01

Use autotools for appveyor until cmake is fixed.

107d565d

2015-05-11T12: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-05T20:21:04

Forgot to install OpenSSL for appveyor

5f89c37e

2015-02-05T19: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**

kc3-lang/libevent/appveyor.yml

appveyor.yml

Log