Branch: refs/heads/master
  Home:   https://github.com/jenkinsci/jenkins-test-harness
  Commit: 830184eb21af4f65a9e79d673261a1612a7413c1
      
https://github.com/jenkinsci/jenkins-test-harness/commit/830184eb21af4f65a9e79d673261a1612a7413c1
  Author: James Nord <jnord+git...@cloudbees.com>
  Date:   2020-01-20 (Mon, 20 Jan 2020)

  Changed paths:
    M src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
    M src/main/java/org/jvnet/hudson/test/JavaNetReverseProxy.java
    M src/main/java/org/jvnet/hudson/test/JenkinsRule.java

  Log Message:
  -----------
  [JENKINS-60821] let Jetty configure its own defaults

Jetty knows better than us, so let Jetty configure its own defaults for
the ThreadPool (min 8 max 200) and #acceptor/selector threads.

This applies feedback from eclipse/jetty.project#4492

We loos the thread naming - but all the jetty threads in the servers
where called "Jetty Thread Pool"-something so we did not isolate them
between the reverse proxy and the JenkinsRule or HudsonTestCase so the
fact they are now called qtp-something is pretty much ok.  Nothing else
seems to use Jetty's QueuedThreadPool in Jenkins so any thread starting
qtp is pretty much going to be the jetty thread pool - and it matches
more what you would get when running jenkins with java -jar...


  Commit: 5bdfd1e08aec9edd7d48a34ddd4d101d88c8d709
      
https://github.com/jenkinsci/jenkins-test-harness/commit/5bdfd1e08aec9edd7d48a34ddd4d101d88c8d709
  Author: James Nord <jnord+git...@cloudbees.com>
  Date:   2020-01-20 (Mon, 20 Jan 2020)

  Changed paths:
    M src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
    M src/main/java/org/jvnet/hudson/test/JavaNetReverseProxy.java
    M src/main/java/org/jvnet/hudson/test/JenkinsRule.java

  Log Message:
  -----------
  More feedback from Jetty

Use a QTP with the defaults and call setName() instead

Uses a unique name per pool so you can identify the various
pools/servers


  Commit: 9dd29659bfc27a2d3053436b1fa1b2ad5665548b
      
https://github.com/jenkinsci/jenkins-test-harness/commit/9dd29659bfc27a2d3053436b1fa1b2ad5665548b
  Author: James Nord <jnord+git...@cloudbees.com>
  Date:   2020-01-21 (Tue, 21 Jan 2020)

  Changed paths:
    M src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
    M src/main/java/org/jvnet/hudson/test/JavaNetReverseProxy.java
    M src/main/java/org/jvnet/hudson/test/JenkinsRule.java

  Log Message:
  -----------
  [JENKINS-60821] remote 'Thread Pool' from the thread pool name

As pointed out by @jglick it should be obvious from the name that the
thread is in a thread pool (has a #xx after it) - so just remove it.


  Commit: 93e9b64a89d3048896f77d62fba84fff715b932b
      
https://github.com/jenkinsci/jenkins-test-harness/commit/93e9b64a89d3048896f77d62fba84fff715b932b
  Author: Mark Waite <mark.earl.wa...@gmail.com>
  Date:   2020-01-22 (Wed, 22 Jan 2020)

  Changed paths:
    M src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
    M src/main/java/org/jvnet/hudson/test/JavaNetReverseProxy.java
    M src/main/java/org/jvnet/hudson/test/JenkinsRule.java

  Log Message:
  -----------
  Merge pull request #197 from jtnord/jetty-threads

[JENKINS-60821] let Jetty configure its own defaults


Compare: 
https://github.com/jenkinsci/jenkins-test-harness/compare/091f119ecfc4...93e9b64a89d3

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/jenkins-test-harness/push/refs/heads/master/091f11-93e9b6%40github.com.

Reply via email to