#
6cfa1a42 |
| 28-Apr-2023 |
Dan Fandrich |
CI: use another glob syntax for matching files on Appveyor The previous globbing syntax was not matching files recursively in directories, so try appending a /* to more closely match the
CI: use another glob syntax for matching files on Appveyor The previous globbing syntax was not matching files recursively in directories, so try appending a /* to more closely match the examples at https://www.appveyor.com/docs/how-to/filtering-commits/
show more ...
|
#
fe61f015 |
| 24-Apr-2023 |
Dan Fandrich |
CI: don't run CI jobs if only another CI was changed A few paths were missed in the last commit, as well as a job added since then. Followup-to 395b9175
|
#
395b9175 |
| 11-Mar-2023 |
Dan Fandrich |
CI: don't run CI jobs if only another CI was changed Also skip builds on non-Windows platforms when only Windows build files have changed. This should reduce the number of usele
CI: don't run CI jobs if only another CI was changed Also skip builds on non-Windows platforms when only Windows build files have changed. This should reduce the number of useless builds and the associated waiting time and chance of spurious failures, freeing resources for new PRs. Closes #10742
show more ...
|
#
2bc1d775 |
| 02-Jan-2023 |
Daniel Stenberg |
copyright: update all copyright lines and remove year ranges - they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - save
copyright: update all copyright lines and remove year ranges - they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - saves us from pointless churn - git keeps history for us - the year range is kept in COPYING checksrc is updated to allow non-year using copyright statements Closes #10205
show more ...
|
#
9f3d3bfb |
| 17-Oct-2022 |
Marc Hoersken |
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Revi
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
show more ...
|
#
86f2d8f6 |
| 14-Oct-2022 |
Viktor Szakats |
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here,
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
show more ...
|
#
30035dfd |
| 09-Sep-2022 |
Daniel Stenberg |
appveyor: enable websockets
|
#
c5c6e867 |
| 24-Aug-2022 |
Marc Hoersken |
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional.
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional. Reviewed-by: Daniel Stenberg Closes #9360
show more ...
|
#
52484bf3 |
| 25-Aug-2022 |
Marc Hoersken |
CI/appveyor: disable TLS in msys2-native autotools builds Schannel cannot be used from msys2-native Linux-emulated builds. Reviewed-by: Marcel Raad Reviewed-by: Daniel Stenberg
CI/appveyor: disable TLS in msys2-native autotools builds Schannel cannot be used from msys2-native Linux-emulated builds. Reviewed-by: Marcel Raad Reviewed-by: Daniel Stenberg Follow up to #9367 Closes #9370
show more ...
|
#
ad9bc597 |
| 17-May-2022 |
max.mehl |
copyright: make repository REUSE compliant Add licensing and copyright information for all files in this repository. This either happens in the file itself as a comment header or in the
copyright: make repository REUSE compliant Add licensing and copyright information for all files in this repository. This either happens in the file itself as a comment header or in the file `.reuse/dep5`. This commit also adds a Github workflow to check pull requests and adapts copyright.pl to the changes. Closes #8869
show more ...
|
#
a34a8480 |
| 09-Apr-2022 |
Marcel Raad |
appveyor: add Cygwin build Closes https://github.com/curl/curl/pull/8693
|
Revision tags: curl-7_76_1, curl-7_76_0, curl-7_75_0, curl-7_74_0, curl-7_73_0, tiny-curl-7_72_0, curl-7_72_0, curl-7_71_1, curl-7_71_0, curl-7_70_0, curl-7_69_1, curl-7_69_0, curl-7_68_0, curl-7_67_0, curl-7_66_0, curl-7_65_3, curl-7_65_2, curl-7_65_1, curl-7_65_0, curl-7_64_1 |
|
#
84be9996 |
| 02-Mar-2019 |
Marcel Raad |
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
|
#
f7376547 |
| 13-Feb-2022 |
Jay Satiro |
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files u
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
show more ...
|
#
22d33956 |
| 15-Mar-2022 |
Philip H <47042125+pheiduck@users.noreply.github.com> |
CI: Do not use buildconf. Instead, just use: autoreconf -fi Closes #8596
|
#
1fa09990 |
| 05-Mar-2022 |
Daniel Stenberg |
misc: update copyright year ranges
|
#
c07a71e7 |
| 10-Jan-2022 |
Marcel Raad |
appveyor: use VS 2017 image for the autotools builds The newer images don't have all required MSYS2 packages. Fixes https://github.com/curl/curl/issues/8248 Closes https://githu
appveyor: use VS 2017 image for the autotools builds The newer images don't have all required MSYS2 packages. Fixes https://github.com/curl/curl/issues/8248 Closes https://github.com/curl/curl/pull/8265
show more ...
|
#
51df1c8e |
| 10-Jan-2022 |
Marcel Raad |
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
|
#
9108da2c |
| 22-Nov-2021 |
Daniel Stenberg |
cmake: private identifiers use CURL_ instead of CMAKE_ prefix Since the 'CMAKE_' prefix is reserved for cmake's own private use. Ref: https://cmake.org/cmake/help/latest/manual/cmake-var
cmake: private identifiers use CURL_ instead of CMAKE_ prefix Since the 'CMAKE_' prefix is reserved for cmake's own private use. Ref: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html Reported-by: Boris Rasin Fixes #7988 Closes #8044
show more ...
|
#
9121032f |
| 29-Oct-2021 |
Marc Hoersken |
CI/runtests.pl: restore -u flag, but remove it from CI runs This makes it possible to use -u again for local testing, but removes the flag from CI config files and make targets.
CI/runtests.pl: restore -u flag, but remove it from CI runs This makes it possible to use -u again for local testing, but removes the flag from CI config files and make targets. Reviewed-by: Daniel Stenberg Partially reverts #7841 Closes #7921
show more ...
|
#
74d46aee |
| 08-Oct-2021 |
Marc Hoersken |
CI: more use of test-ci make target and verbose output Replace test-nonflaky with test-ci and enable verbose output in all remaining CIs except Zuul which is customized a lot. R
CI: more use of test-ci make target and verbose output Replace test-nonflaky with test-ci and enable verbose output in all remaining CIs except Zuul which is customized a lot. Reviewed-by: Daniel Stenberg Reviewed-by: Jay Satiro Follow up to #7785 Closes #7832
show more ...
|
#
ab1671ca |
| 27-Sep-2021 |
Marc Hoersken |
CI/makefiles: introduce dedicated test target Make it easy to use the same set of test flags throughout all current and future CI builds. Reviewed-by: Jay Satiro Follow
CI/makefiles: introduce dedicated test target Make it easy to use the same set of test flags throughout all current and future CI builds. Reviewed-by: Jay Satiro Follow up to #7690 Closes #7785
show more ...
|
#
02c9802f |
| 27-Sep-2021 |
Marc Hoersken |
CI: align make and test flags in various config files 1. Use Makefile target to run tests in autotools builds on AppVeyor. 2. Disable testing of SCP protocol on native Windows environmen
CI: align make and test flags in various config files 1. Use Makefile target to run tests in autotools builds on AppVeyor. 2. Disable testing of SCP protocol on native Windows environments. 3. Remove redundant parameters -a -p from target test-nonflaky. 4. Don't use -vc parameter which is reserved for debugging. Replaces #7591 Closes #7690
show more ...
|
#
60efeb1e |
| 02-Jun-2021 |
Marc Hoersken |
runtests: add option -u to error on server unexpectedly alive Let's try to actually handle the server unexpectedly alive case by first making them visible on CI builds as failures.
runtests: add option -u to error on server unexpectedly alive Let's try to actually handle the server unexpectedly alive case by first making them visible on CI builds as failures. This is needed to detect issues with killing of the test servers completely including nested process chains with multiple PIDs per test server (including bash and perl). On Windows/cygwin platforms this is especially helpful with debugging PID mixups due to cygwin using its own PID space. Reviewed-by: Daniel Stenberg Closes #7180
show more ...
|
#
e052bbcd |
| 15-Apr-2021 |
Daniel Stenberg |
ci: adapt to configure requiring an explicit TLS choice
|
#
4d2f8006 |
| 04-Nov-2020 |
Daniel Stenberg |
curl.se: new home Closes #6172
|