@MarcoFalke Could you provide some additional context? With this PR merged tests would still run in both Appveyor and Travis, right? What is the plan? :-)

The plan is to be flexible, to be able to switch away from travis any time without much hassle. Also, this makes it easier to run the ci locally.

Concept ACK.

Fixed typo in doc and added a note on how to run the ci locally

I'm now seeing an error running this:

configure.ac:40: installing 'build-aux/missing'
src/Makefile.am: installing 'build-aux/depcomp'
travis_fold:end:autogen

travis_fold:start:configure
configure: loading site script /Users/michael/github/bitcoin/depends/x86_64-unknown-linux-gnu/share/config.site
configure: loading cache config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for x86_64-unknown-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
configure: error: source directory already configured; run "make distclean" there first
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Bitcoin Core configure 0.18.99, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ../configure --cache-file=config.cache --disable-dependency-tracking --prefix=/Users/michael/github/bitcoin/depends/x86_64-unknown-linux-gnu --bindir=/Users/michael/github/bitcoin/out/x86_64-unknown-linux-gnu/bin --libdir=/Users/michael/github/bitcoin/out/x86_64-unknown-linux-gnu/lib

It says source directory already configured; run "make distclean" there first. Have you tried that?

Specifically cd /Users/michael/github/bitcoin && make distclean.

The ci is generally assuming the the folder is a fresh git clone. If needed, that can be changed later on, but better not part of this pull.

It says source directory already configured; run "make distclean" there first. Have you tried that?

Shouldn't that all be handled by the script? If not, then some docs about why you can't run the tests twice in a row would be handy.

Done

I don't think docker on windows can run Ubuntu containers

Rebased without any changes due to overly sensitive merge conflict detection on GitHub. git range-diff should be empty: git range-diff bitcoin/master fa9404d76d faeacf3269

I don't think docker on windows can run Ubuntu containers

It can since https://docs.docker.com/docker-for-windows/wsl-tech-preview/

aaron@pcdodo:~$ uname -a
Linux pcdodo 4.19.57-microsoft-standard #1 SMP Wed Jul 3 20:47:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
aaron@pcdodo:~$ docker run ubuntu echo "I  love Windows"; lsb_release -a
I  love Windows
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

Actually it was already possible to use ubuntu docker containers on Windows but now it possible directly on top of the Windows Subsystem for Linux kernel.

Thanks ACK fa9404d - Maybe @sipsorcery or @NicolasDorier might also want to test here, then we'd have all OS's covered?

@fanquake I looked over the PR and successfully ran my appveyor build with the PR merged. Doesn't seem to be anything Windows related in this PR? Ony travis and shell scripts. Or did you testing the script changes with the WSL/Mingw builds on Windows?

Thanks @sipsorcery. I also thought it was possible to run on Windows.

Or did you testing the script changes with the WSL/Mingw builds on Windows?

Yea I just meant checking out this PR, and testing/running the scripts, to make sure they were working in your Windows development setups.