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
GEODE-5600 - Run createVersionPropertiesFile on SHA change #2457
Conversation
Found during testing, relating to GEODE-5694, remove the zip artifacts for better signing behavior Authored-by: Robert Houghton <rhoughton@pivotal.io>
@pivotal-jbarrett @smgoller @nabarunnag This changes the signing behavior a little bit, as relates to ZIP artifacts. Please check it out. |
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.
There are some remnants of the other changes in the previous attempt at GEODE-5600 that should be removed in favor of this approach. Notably:
- The properties
sourceRevision
andsourceRepository
are not longer used ingradle.properties
and should be removed. - In the
pull-request/jinja.template.yml
, two instances ofSOURCE_REPOSITORY
no longer need to be passed to the test/build scripts.
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.
Asside from the changes that @PurelyApplied asked for I approve this change.
Signed-off-by: Patrick Rhomberg <prhomberg@pivotal.io>
Spurious failure
passed upon rerun. See failing: vs passing: |
Found during testing, relating to GEODE-5694, remove the zip artifacts for better signing behavior
Authored-by: Robert Houghton rhoughton@pivotal.io
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop
)?Is your initial contribution a single, squashed commit?
Does
gradlew build
run cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.