Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-18247

Add CircleCI config files for J11+J17

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 5.0-alpha1, 5.0
    • CI
    • None
    • Quality Assurance
    • Normal
    • All
    • None
    • Hide

      Summary:

      • Added separate CircleCI configuration files for JDK11+17 plus created a respective generate_11_and_17.sh script. The differentiator for all new files is they all end up with "_11_and_17" suffix as part of their names. The new script operates the new config files in the way generate.sh operates on the old JDK8+11 configuration files. Why I chose to do it that way? - I believe this will make it easy when the time to switch to 11+17 come.
      • Updated the readme. I would appreciate constructive feedback from reviewers if it reads well or it is unclear and confusing.
      • Currently we miss upgrade tests because we do not have JDK11 upgrade tests yet
      • The simulator still does not support JDK17 so I added only JDK11 simulator tests
      • Current table of all test failures with respective ticket numbers will be posted on CASSANDRA-16895 after this one gets committed.
      • I also plan to send email update to @dev when this gets committed. It will inform people that the new configuration is available.

      Patch - https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc

      CI run #2318:

      started new run of j11_cqlsh_dtests_py311 here - there was a git clone issue in the previous run; this one completed all good

      Other JDK11 tests completed successfully

      JDK17 seems good that it ran all tests we wanted with the resources we wanted and the right JDK. I will make a write up of the failures as per my earlier suggestion.

      Show
      Summary: Added separate CircleCI configuration files for JDK11+17 plus created a respective generate_11_and_17.sh script. The differentiator for all new files is they all end up with "_11_and_17" suffix as part of their names. The new script operates the new config files in the way generate.sh operates on the old JDK8+11 configuration files. Why I chose to do it that way? - I believe this will make it easy when the time to switch to 11+17 come. Updated the readme. I would appreciate constructive feedback from reviewers if it reads well or it is unclear and confusing. Currently we miss upgrade tests because we do not have JDK11 upgrade tests yet The simulator still does not support JDK17 so I added only JDK11 simulator tests Current table of all test failures with respective ticket numbers will be posted on CASSANDRA-16895 after this one gets committed. I also plan to send email update to @dev when this gets committed. It will inform people that the new configuration is available. Patch - https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc CI run #2318 : started new run of j11_cqlsh_dtests_py311 here - there was a git clone issue in the previous run; this one completed all good Other JDK11 tests completed successfully JDK17 seems good that it ran all tests we wanted with the resources we wanted and the right JDK. I will make a write up of the failures as per my earlier suggestion.

    Description

      Based on the direction of this discussion, I would like to propose CircleCI config files which can be used to test current trunk with JDK 17 (after I blindly remove the scripted UDFs in another ticket, to be opened soon)

      Attachments

        Issue Links

          Activity

            People

              e.dimitrova Ekaterina Dimitrova
              e.dimitrova Ekaterina Dimitrova
              Ekaterina Dimitrova
              Brandon Williams, Michael Semb Wever
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m