Skip to content
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-6009 add Java 11 to PR pipeline #2806

Conversation

onichols-pivotal
Copy link
Contributor

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?

  • [n/a] Does gradlew build run cleanly?

  • [n/a] Have you written or updated unit tests to verify your changes?

  • [n/a] 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.

@onichols-pivotal
Copy link
Contributor Author

@rhoughton-pivot please review

@@ -158,7 +161,7 @@ jobs:
status: pending
- do:
- put: concourse-metadata-resource
- task: create_instance
- task: create_instance-{{java_test_version.name}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we changing the task names (create_instance, rsync_xyz, archive_results, etc), if we aren't doing jdk8 and jdk11 as separate tasks in the same job?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not absolutely necessary as long as 8 and 11 jobs are split, so the main reason is just for consistency with the develop pipeline, to make it more explicit as you're looking at results which results you're looking at, and for future-proofing if 8 and 11 jobs ever get combined back together in the future.

@onichols-pivotal
Copy link
Contributor Author

I verified this change in a test pipeline. Now awaiting on consensus from the Geode dev community on whether this change is actually desired or not.

@dickcav dickcav merged commit 9b2a423 into apache:develop Nov 9, 2018
@onichols-pivotal onichols-pivotal deleted the GEODE-6009-add-java-11-to-PR-pipeline branch August 27, 2020 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants