Closes #3571

Closes #3564

Invoking the maintainer intended COPYRIGHTYEAR check for everyone
in the PR pipeline is too invasive, especially at the turn of the
year when many files get affected. Remove and leave it as a tool
for maintainers to verify patches before commits.

This reverts f7bdf4b2.

After discussion with: Daniel Stenberg

The extended warning for checking incorrect COPYRIGHTYEAR is quite
expensive to run, so rather than expecting every developer to do it
we ensure it's turned on locally for Travis.

on Linux. To make sure the test suite runs with its newly build tool and
doesn't require an external one present.

Bug: #3198
Closes #3200

... using clang

Closes #3190

Closes #3182

This is required for gnutls-serv, which enables a few more tests.

Closes https://github.com/curl/curl/pull/2958

Closes #3144

and remove BOM from projects/wolfssl_override.props

Closes #3126

Due to an issue with travis
(https://github.com/travis-ci/travis-ci/issues/9956) we've been using
Xcode 9.2 for darwinssl builds for a while. Now xcode 10 is offered as
an alternative and as it builds curl+darwinssl fine that seems like a
better choice.

Closes #3062

... since the gcc-8 ones seem to fail frequently.

Follow-up from b8520719

Closes #2886

Since they started to fail almost 100% since a few days.

Closes #2876

Closes https://github.com/curl/curl/pull/2869

... when curl is built from distribution tarball

Closes #2856

Follow-up to 2de63ab1 and
0b87c963.

Closes https://github.com/curl/curl/pull/2862

... as building on 10.13.x before 10.13.4 leads to link errors.

Assisted-by: Nick Zitzmann
Fixes #2835
Closes #2845

... to make sure the examples are all checked.

Closes #2811

... since default uses the threaded one and we test the c-ares build
already.

Closes #2689

... run a few more tortured based and run all tests event-based.

Closes #2664

Detected using the `codespell` tool (version 1.13.0).

Also secure and fix an URL.

Closes #2558

Assisted-by: Dan Fandrich

Closes #2528

Closes #2531

It seems to not be detected by default anymore (which is a bug I
believe)

Closes #2541

closes #2471

Extra-eye-on-this-by: Marcel Raad

Closes #2478

This works now and precise is in the process of being decommissioned.

Closes https://github.com/curl/curl/pull/2476

This is a workaround for an unsolved travis issue that is causing CI
instances to sporadically fail due to 'unable to connect' issues during
apt stage.

Ref: https://github.com/travis-ci/travis-ci/issues/8507
Ref: https://github.com/travis-ci/travis-ci/issues/9112#issuecomment-376305909

Update clang to version 3.9 and GCC to version 6.

Closes https://github.com/curl/curl/pull/2345

... to verify it builds and works fine.

Ref: https://curl.haxx.se/mail/lib-2017-09/0031.html

Closes #1872

.. since now mac osx image expects pip2 or pip3, and doesn't know pip:

0.01s$ pip install --user cpp-coveralls
/Users/travis/.travis/job_stages: line 57: pip: command not found

Ref: https://github.com/travis-ci/travis-ci/issues/8829

Closes https://github.com/curl/curl/pull/2133

Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>

Uses a separate build without --enable-debug and no valgrind.

The debug option causes far too many warnings in boringssl's headers
(C++ comments, trailing commas etc).  Valgrind triggers some false
positive errors in thread-local data used by boringssl.

Closes #2118

We don't expect any steps to fail in travis. Exit the script if they do.

Closes #1966