You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2019/09/17 18:39:05 UTC

[GitHub] [lucene-solr] lw-nick opened a new pull request #888: SOLR-13774 add lucene/solr openjdk compatibility matrix to ref guide.

lw-nick opened a new pull request #888: SOLR-13774 add lucene/solr openjdk compatibility matrix to ref guide.
URL: https://github.com/apache/lucene-solr/pull/888
 
 
   <!--
   Before creating a pull request, please file an issue in the ASF Jira system for Lucene or Solr:
   
   * https://issues.apache.org/jira/projects/LUCENE
   * https://issues.apache.org/jira/projects/SOLR
   
   You will need to create an account in Jira in order to create an issue.
   
   The title of the PR should reference the Jira issue number in the form:
   
   * LUCENE-####: <short description of problem or changes>
   * SOLR-####: <short description of problem or changes>
   
   LUCENE and SOLR must be fully capitalized. A short description helps people scanning pull requests for items they can work on.
   
   Properly referencing the issue in the title ensures that Jira is correctly updated with code review comments and commits. -->
   
   
   # Description
   
   Create a reusable build system to run Lucene/Solr ant test source code suite against different versions of OpenJDK binaries. Generate a table with the results of BUILD SUCCESSFUL or BUILD FAILED and incorporate the output into the Ref Guide here: solr/solr-ref-guide/src/solr-system-requirements.adoc
   
   # Solution
   
   The build system is written in Python and Bash. Several scripts configure the environment, download all the Solr sources for each version, and OpenJDK binaries from jdk.java.net. Java versions are included in the submitted documentation. Python multiprocessing is used to parallelize concurrent Solr+OpenJDK ant test runs. Params for JVM concurrency are passed through scripts to ant tasks as well giving fin-grained concurrency control. Tests that resulted in BUILD SUCCESSFUL are passed as "Y" and those resulting in BUILD FAILED are failed as "N".
   
   # Tests
   
   Test suites run as described in solution. For validating syntax of submitted documentation in this PR Asciidoctor was run to convert to HTML that was inspected visually.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request title.
   - [x] I am authorized to contribute this code to the ASF and have removed any code I do not have a license to distribute.
   - [ ] I have developed this patch against the `master` branch.
   - [ ] I have run `ant precommit` and the appropriate test suite.
   - [ ] I have added tests for my changes.
   - [x] I have added documentation for the [Ref Guide](https://github.com/apache/lucene-solr/tree/master/solr/solr-ref-guide) (for Solr changes only).
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org