-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure RPMs are only build from clean git trees #13000
Ensure RPMs are only build from clean git trees #13000
Conversation
hack/build-rpm-release.sh
Outdated
@@ -18,6 +18,9 @@ fi | |||
|
|||
os::log::info 'Building Origin release RPMs with tito...' | |||
os::build::get_version_vars | |||
if [[ "${OS_GIT_TREE_STATE}" == "drity" ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, typo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
The `tito` process for building RPMs will not incorporate any changes that are not committed in the git tree, so if we notice that the git three state is dirty during the RPM build, we should fail early and ask the user to commit their changes first before re-trying the build. Signed-off-by: Steve Kuznetsov <[email protected]>
d76d3f4
to
cec748f
Compare
Evaluated for origin test up to cec748f |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/303/) (Base Commit: 774a283) |
[merge] |
@openshift-bot, the last build failed from the following flakes:
re[merge] |
Evaluated for origin merge up to cec748f |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/351/) (Base Commit: cf7e336) (Image: devenv-rhel7_5941) |
The
tito
process for building RPMs will not incorporate any changesthat are not committed in the git tree, so if we notice that the git
three state is dirty during the RPM build, we should fail early and
ask the user to commit their changes first before re-trying the build.
Signed-off-by: Steve Kuznetsov [email protected]
/cc @smarterclayton
[test]