-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
Jenkins 2.218
As per Jetty Issue#4492 which was created to report the failure to process requests we have been told that our code is wrong.
Jesse Glick verified the fix in cloudbees-workflow-template-plugin#9 commit 0c4eb98d
We need to
- see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔
- make sure other uses of Jetty in Jenkins are safe
- winstone ✔
- maven-hpi-plugin (run mojoe etc) ✔
- causes
-
JENKINS-60857 Wildcard certificates rejected by Winstone after Jetty update
-
- Closed
-
- is caused by
-
JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
-
- Resolved
-
- links to
[JENKINS-60821] Check and update any Jetty code with custom threadpool
Link |
New:
This issue is caused by |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492)] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [ https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96]6 [(https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe)] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. slack: [https://cloudbees.slack.com/archives/CBXU9VCGL/p1579285074024500?thread_ts=1579193579.070300&cid=CBXU9VCGL] |
New:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492)] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. |
Description |
Original:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492)] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. |
New:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. |
Description |
Original:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. |
New:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins * winstone * maven-hpi-plugin (run mojoe etc) ✔ |
Description |
Original:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins * winstone * maven-hpi-plugin (run mojoe etc) ✔ |
New:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins are safe * winstone ✔ * maven-hpi-plugin (run mojoe etc) ✔ |
Description |
Original:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins are safe * winstone ✔ * maven-hpi-plugin (run mojoe etc) ✔ |
New:
As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe] We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins are safe * winstone ✔ * maven-hpi-plugin (run mojoe etc) ✔ |
Remote Link | New: This issue links to "winstone PR#90 (Web Link)" [ 24313 ] |
Remote Link | New: This issue links to "jenkins-test-harness PR#197 (Web Link)" [ 24314 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Fixed but Unreleased [ 10203 ] |