- 05 6月, 2012 4 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 30 5月, 2012 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 29 5月, 2012 7 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 28 5月, 2012 2 次提交
-
-
由 olivier lamy 提交于
-
由 olivier lamy 提交于
-
- 26 5月, 2012 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Integrated a new version of Stapler that provides debug logging for the problem. See the ticket for more details of how to enable this probe.
-
- 25 5月, 2012 8 次提交
-
-
由 Seiji Sogabe 提交于
Update Spanish
-
由 Kohsuke Kawaguchi 提交于
Further reduce the scope of the lock to only cover jobNames access, which is mandatory. if ig.doCreateItem requires synchronization, that's a job of ig.doCreateItem implementation, not that of ListView.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
It uses Diffie Hellman to come up with one-time session key, then have the server sign this session key to allow the client to verify that there's no man in the middle.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
Plexus compiler 1.8.6 that maven-compiler-plugin 2.4 has a static field to store a reference to the Javac class in tools.jar In JDK that I use (6u26), Javac has a static field that stores what appears to be a cache of jar files (ZipFileIndex.zipFileIndexCache). And in addition, Maven instantiates a separate ClassRealm to host plugin jar files when a project has any build extensions. The combined result is that during a build, we end up having multiple copies of URLClassLoader that loads tools.jar, and each ends up caching jar files it was used. This puts a pressure to permgen (although I couldn't pinpoint which portions of those caches use permgen), resulting in OOME. In Plexus compiler 1.9, Olivier added a new feature to control the caching/reuse of Javac compiler. While this apparently was done primarily for fixing concurrency issues in multi-threaded builds, it is also a useful mechanism to prevent the retention of Javac classes. So I pushed the SNAPSHOT version of maven-compiler-plugin as 2.5-jenkins-1 and tweaking POM to use it.
-
- 24 5月, 2012 8 次提交
-
-
由 Manolo Carrasco 提交于
-
由 Olivier Lamy 提交于
Fixed grammatical error in build page message. Thnaks!
-
由 Kohsuke Kawaguchi 提交于
In the end, proper fix requires having a filter that tracks GZipOutputStream.
-
由 Kohsuke Kawaguchi 提交于
-
由 Carl Quinn 提交于
-
由 Carl Quinn 提交于
-
由 Kohsuke Kawaguchi 提交于
Until now, Jenkins.overallNodeProvisioner was tracking an inconsistent pair of numbers. On one hand, it was tracking all the executors in the system, but then it was also only tracking the # of free-roaming label-unassigned jobs as the queue length. So if all your slaves are set with Node.Mode.EXCLUSIVE and you have some free-roaming jobs, then it'll never tickle NodePrivisioner. In other words, the # of executors weren't reflecting the actual # of executors that can execute what's counted as the queue length. See the problem report at https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/bUwGEgOwv4Q To fix this, I introduced another LoadStatistics that only counts the # of executors that can execute free-roaming jobs, and # of free-roaming jobs as the queue length. In this way, two pairs of numbers are consistent. This now allows us to use overallLoadStatistics for really the entire system, including all executors and the total queue length. This is primarily for administrators to see the resource utilization, and it is not useful for NodeProvisioner input because it's mixing too many different things. The semantics change in OverallLoadStatistics.queueLength allows us to deprecate its totalQueueLength field.
-
由 Kohsuke Kawaguchi 提交于
-
- 23 5月, 2012 9 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Fall back in non-JNA case wasn't working.
-
由 Dave Hunt 提交于
-
由 Kohsuke Kawaguchi 提交于
404 for nearby configuration builds can make the life of automated client script more complicated, so opt for redirection.
-
由 lvotypko 提交于
-
由 Vincent Latombe 提交于
Backward compatibility is preventing the View.READ permission to apply correctly. It actually overrides the View.READ instead of complementing it. This change only applies default READ right if the View.READ is not available, and the user has View.CONFIGURE + the view is not empty.
-
由 Fred G 提交于
-
由 Kohsuke Kawaguchi 提交于
See https://github.com/jenkinsci/jenkins/pull/474 for the original conversation
-
由 Eric Dalquist 提交于
Include the file system path that was checked in the low disk space error message
-
由 Kohsuke Kawaguchi 提交于
-