0.17.0-beta1
Pre-release
Pre-release
0.17.0-beta1 (24-Apr-2018)
- The filesystem is not shared anymore with the docker containers, every container will upload their own packages/recipe, so it is not needed to share the conan home. The remotes and all the needed configuration is passed as environment variables.
- The
shared_option_name
of theadd_common_builds
is now automatically managed when the recipe contains ashared
option. - Better
remotes
configuration, supporting remote naming and use SSL parameter.- As parameter of
ConanMultiPackager
, remotes can be a list of strings separated by,
of a tuple containingURL
,use ssl
andremote name
:
remotes = "https://api.bintray.com/conan/conan-community/conan,https://api.bintray.com/conan/other/conan2" remotes = [("https://api.bintray.com/conan/conan-community/conan", True, "remote1"), ("https://api.bintray.com/conan/other/conan2", False, "remote2")]
- As environment variable:
CONAN_REMOTES="url1@True@remote_name, url2@False@remote_name2"
CONAN_UPLOAD
/upload
. - As parameter of
- Feature: If the remote (both upload remote or remotes in general) exists in the current installation with the same URL it will be kept and the current remote name will be used.
- Improvements in the login/password at remote level:
login_username="my_user"
login_username = {"remote1": "my_user", "my_artifactory": "other_user"}
- New parameter: always_update_conan_in_docker, when True "conan package tools" and "conan" will be installed and upgraded in the docker image in every build execution (and the docker image commit will be skipped)
- Conan package tools calling directly the
conan python api
. - The "pip install" invocation takes into account the
CONAN_DOCKER_USE_SUDO
to use sudo or not. - Docker use of
CONAN_TEMP_TEST_FOLDER
to avoid creating the builds in thetest_package
folder in case of a local usage of conan package tools. - General code refactor, reducing technical debt, significant increased of the test suite.