Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73283

Run PCT with a Jetty 12 EE 9 test harness when core is Jetty 12 EE 9

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • _unsorted
    • None
    • 3334.v18e2a_2f48356

      This is a straightforward extension of JENKINS-73282: once a test harness is available that supports both Jetty 12 EE 8 and Jetty 12 EE 9, extend JENKINS-73282's dynamic upgrade logic to use that version when the core postdates Jetty 12 EE 9 or later. Unfortunately we also have to deal with https://github.com/jenkinsci/plugin-pom/issues/936 here as well. If the plugin parent POM precedes a fix for that issue, then on cores that postdate Jetty 12 EE 9 we will also need to work around that issue by passing -DoverrideVersions=jakarta.servlet:jakarta.servlet-api:5.0.0 to PCT. If the fix for https://github.com/jenkinsci/plugin-pom/issues/936 hasn't been released at the time of implementation of this ticket, we can detect in PCT whether or not we need to apply the latter workaround by checking the version of jakarta.servlet:jakarta.servlet-api before running the test. If it is 4.x but the core postdates EE 9, the workaround is needed; otherwise, the workaround is not needed.

            basil Basil Crow
            basil Basil Crow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: