Pike Series Release Notes¶
16.0.0¶
New Features¶
- The repo server file system structure has been updated to allow for multiple Operating systems running multiple architectures to be run at the same time and served from a single server without impacting pools, venvs, wheel archives, and manifests. The new structure follows the following pattern $RELEASE/$OS_TYPE-$ARCH and has been applied to os-releases, venvs, and pools. 
Upgrade Notes¶
- The entire repo build process is now idempotent. From now on when the repo build is re-run, it will only fetch updated git repositories and rebuild the wheels/venvs if the requirements have changed, or a new release is being deployed. 
- The git clone part of the repo build process now only happens when the requirements change. A git reclone can be forced by using the boolean variable - repo_build_git_reclone.
- The python wheel build process now only happens when requirements change. A wheel rebuild may be forced by using the boolean variable - repo_build_wheel_rebuild.
- The python venv build process now only happens when requirements change. A venv rebuild may be forced by using the boolean variable - repo_build_venv_rebuild.
- The repo build process now only has the following tags, providing a clear path for each deliverable. The tag - repo-build-installcompletes the installation of required packages. The tag- repo-build-wheelscompletes the wheel build process. The tag- repo-build-venvscompletes the venv build process. Finally, the tag- repo-build-indexcompletes the manifest preparation and indexing of the os-releases and links folders.
Deprecation Notes¶
- The variable - repo_build_pip_extra_indexhas been removed. The replacement list variable- repo_build_pip_extra_indexesshould be used instead.
Other Notes¶
- From now on, external repo management (in use for RDO/UCA for example) will be done inside the pip-install role, not in the repo_build role. 
