From dcd609e00376621597e63d3638a8a0b44e9f2017 Mon Sep 17 00:00:00 2001 From: Jesse Pretorius Date: Tue, 13 Jun 2017 10:28:07 +0100 Subject: [PATCH] Add release note for idempotent repo build Change-Id: I711b9aab2486045662d4a966a96a3e0a7d31fae0 --- ...empotent-wheel-build-4c527045bec09fd5.yaml | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 releasenotes/notes/idempotent-wheel-build-4c527045bec09fd5.yaml diff --git a/releasenotes/notes/idempotent-wheel-build-4c527045bec09fd5.yaml b/releasenotes/notes/idempotent-wheel-build-4c527045bec09fd5.yaml new file mode 100644 index 0000000..69b1df7 --- /dev/null +++ b/releasenotes/notes/idempotent-wheel-build-4c527045bec09fd5.yaml @@ -0,0 +1,22 @@ +--- +upgrade: + - 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-install`` + completes the installation of required packages. The tag + ``repo-build-wheels`` completes the wheel build process. The tag + ``repo-build-venvs`` completes the venv build process. Finally, the + tag ``repo-build-index`` completes the manifest preparation and + indexing of the os-releases and links folders.