The bash/ruby SDK code that checks if hot_deploy and force_clean_build are enabled uses the latest deployment's metadata.json to determine these values. During a build, when pre-repo-archive is invoked, we haven't created a new deployment directory yet, nor have we written the metadata for the new build. As a result, the methods in the bash/ruby SDK are looking at the previous deployment's values. We might want to consider creating the new deployment directory before we call pre-repo-archive, write the metadata, and then call pre-repo-archive. If we do this, we should also probably keep the code in build() that is writing the metadata, as jenkins uses this as its initial entry point for building and doesn't use the same post_receive/pre-repo-archive flow.
*** Bug 1023902 has been marked as a duplicate of this bug. ***
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/b74208323503ade928ea0358e2be4009258208b9 Bug 1022271
The above github-bot comment was supposed to be for 1022271. Sorry for any confusion.
Wow can't get that right. I meant it was for 1022272.
https://github.com/openshift/origin-server/pull/4014
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/85d23839c182246d32abcbf428ed97d112189e40 Bug 1022271 Write hot_deploy, force_clean_build, git_ref, git_sha1 to deployment metadata file as part of prereceive and use metadata file's values afterwards in postreceive, build, prepare, distribute, activate.
Tested on devenv_3959. The code is checked in. The option "hot-deploy" and "force-clean-build" works. The dup bug 1023902 does not occur. Mark the bug as verified.