Containerize CI, Conan packages building triggering and more...

[Croydon]

DON'T EVEN DARE TO MERGE THIS IF YOU ARE NOT ME

Using Docker in our CI has several advantages, including but not limited to:

• being independent from our CI hoster, e.g. Travis has very often old software, we can pretty much use every version of Ubuntu or any other Linux based OS, including any compatible packages for these OS/versions
• make LOCAL CI debugging A LOT easier, the only thing needed is Docker installed locally, then you have pretty much 100% the same testing environment
• being able to generate Conan packages and test building + running tests on more compiler/version than ever before + being able to expend it easily

Things I need to do before(?) merging:

• [x] check if git tag creating is still working
• [x] check if Windows Conan packages are fine
• [x] install conan-community as another repository (to pull in recipes we actually use from there as well)
• [x] RENAME BRANCH NAMES FOR MASTER

Things I would like to do at some point after merging this:

• get all Conan packages we use in our own Conan repository (or this gets a problem when we use packages which aren't in our repo or conan center or conan transit)
  • automate this steps, which additional information writing in dependencies.py
  • => auto import of new (version of) packages from external Conan recipes we use (+ as a consequences packages generating)
• making local debugging even easier (e.g. right now you would need to give a lot of parameters to the .sh file in order to run it successfully)
• add more compiler/versions (new versions get released quicker than characters can get killed off in Game Of Thrones)

This is not perfect yet but already waaaaay better than the currect setup, so let's finally merge this.

PS: Sorry for typos and gramma, it's late 😄

[aschaeffer]

How do I test it?

[Fohlen]

Noting down that https://github.com/Cleafy/sxkdvm will allow OSX to be run via Docker as well!

[Croydon]

How do I test it?

As I said it is complicated as hell right now, which I want to simplify in future pull requests. You would need to do

sudo docker pull inexorgame/ci-docker:gcc070clang040 (for gcc 7 or clang)

then go to the root of the git repo and execute:

sudo docker run -v $(pwd)':'/inexor --net=host -it inexorgame/ci-docker':'${docker_tag} /inexor/${RELATIVE_PATH}tool/travis.sh target_script /${RELATIVE_PATH} ${TARGET} ${CONAN_COMPILER} ${CONAN_COMPILER_VERSION} ${CMAKE_CC} ${CMAKE_CXX} ${TRAVIS_COMMIT} ${TRAVIS_BRANCH} ${TRAVIS_JOB_NUMBER} ${NIGHTLY} ${NIGHTLY_USER} ${NIGHTLY_PASSWORD} ${FTP_DOMAIN} ${TRAVIS_TAG} ${TRAVIS_PULL_REQUEST} ${TRAVIS_REPO_SLUG}

and place a valid value for every single parameter.

So..yeah... I will simplify that 😄

Noting down that https://github.com/Cleafy/sxkdvm will allow OSX to be run via Docker as well!

I highly doubt that this is legal.. macOS is not free to get, so this is maybe, just maybe legal when you already run macOS and have a license by buying a mac device.

For macOS CI we should just use plain Travis.

[Croydon]

@a-teammate @aschaeffer I want to merge this tomorrow finally. It's stable enough to mass compile + test our conan packages which is good enough for a first step.

Please have a general look and approve :P

[Croydon]

@a-teammate Please have a second look

[Croydon]

AppVeyor fails for this pull request, because some depedencies need to get rebuild which only happens on push to master.