search

inexorgame-obsolete / deprecated-cube-engine-inexor

UNMAINTAINED: Please have a look at the vulkan-renderer
https://inexor.org
zlib License
11 stars 1 forks source link

[conan] Move recipes and packages to our new Bintray repo #415

Closed Croydon closed 7 years ago

Croydon commented 7 years ago

After the move we need to update our build instructions in the wiki and in build scripts to actually use our Bintray repository.

The auto-moved current ones are read-only and we shouldn't rely on them anymore.

Croydon commented 7 years ago

This is done now.

Important

Since Bintray works with repositories the logic changed a bit.

Conan slang: recipes = build instructions package = built and ready to use (binary) packages

1) As I added to the build instructions: Developers needs to explicit add our repository. If they want to make sure that they benefit from our prebuilds packages they should do this prioritized before the default repositories (this does --insert which is short for --insert=0; smaller number = higher priority).

2) Because of the repositories it actually got a bit more complicated to use recipes/packages from other people. To keep it to a minium which repositories people need to setup, we will upload ALL recipes we rely on and the respective packages for all compilers+compiler versions+configurations+operating systems we are official supporting to our own repository. Actually, this does NOT increase build time in ci-prebuilds, since, for testing purposes, we already build everything and in inexor-core it actually brings the build time DOWN, since all recipes will have packages, in opposition to now, where many foreign recipes don't have packages for more up-to-date compiler versions. We still don't maintain these foreign recipes of course.

The upload pattern changes: All packages with "stable" in its names will get uploaded. Therefore the branch naming is now important. "testing" should only get used for actually, non-production testing and if we explicit don't want to have uploaded packages like it is the case with CEF. (So we can now use the inexorgame username for the CEF recipe as well).

3) Before new Conan recipes gets pushed for usage to the master branch of inexor-core, they could and maybe should get mass-tested. This can be easily done by creating a branch in ci-prebuilds (DON'T forget to change the branch name of the recipe you are testing to "testing" or our Conan repository gets a lot of garbage). I will add instructions to the ci-prebuilds repository, once I have merged the trigger-logic into master.