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
[BEAM-1513] Skip slower verifications if '-Dquick' specified. Enable them otherwise #2048
Conversation
R: @dhalperi |
CC: @jbonofre |
Refer to this link for build results (access rights to CI server needed): |
c5c0037
to
0e4f13a
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Thanks for the change. I'm reviewing. |
@@ -48,24 +48,23 @@ | |||
</profile> | |||
<profile> | |||
<id>release</id> | |||
<activation> | |||
<property> | |||
<name>!quick</name> |
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.
I would not condition release profile with quick property. Imagine if the release manager does mvn release:prepare -Dquick
it would not be good.
Further more, the user still have to do mvn clean install -Prelease
to enable all verification right ? I would activate all verifications by default and disable only with -Dquick
.
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.
If someone performing a release will specify -Dquick
wouldn't that be human error? The same is true if they would specify any other flags which they should not.
Regarding the second question, this change indeed makes the verifications (checkstyle, rat, findbugs) enabled by default and disabled only with -Dquick
.
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.
Fair enough.
I'm just testing a new time. |
0e4f13a
to
e1f4c03
Compare
Rebased on master |
Thanks. Updating and merging. |
Refer to this link for build results (access rights to CI server needed): |
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.
LGTM. Merging.
For the record, I would mention |
Refer to this link for build results (access rights to CI server needed): |
Hold on -- this was sent to @dhalperi for review and was merged before he had a chance to take a look. @jbonofre, @aviemzur, can we please reset this? @dhalperi, I'd kindly ask to review according to the resolution on the mailing list and let's address comments in the followup pull request please? Thanks! |
I read this thread https://lists.apache.org/thread.html/48383f94a0ec3f5bae6276d77f9826ee7676ac24273e3b74ec792fe1@%3Cdev.beam.apache.org%3E as building a consensus that checks should be off by default, and relesae profile should be opt in. It seems like the following people were in favor of that: and the following people wanted to change as this proposal: That I believe is everyone who rang into the specific discussion on-or-around Feb 10. So in other words, I think this PR is mostly against the will of the community. |
Sure, if the majority is against, let's revert. |
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
[BEAM-<Jira issue #>] Description of pull request
mvn clean verify
. (Even better, enableTravis-CI on your fork and ensure the whole test matrix passes).
<Jira issue #>
in the title with the actual Jira issuenumber, if there is one.
Individual Contributor License Agreement.