- 04 4月, 2012 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 03 4月, 2012 13 次提交
-
-
由 Kohsuke Kawaguchi 提交于
made sure that even if a bug similar to what was just fixed in the previous commit re-surfaces, we still won't kill the master JVM by eating its memory
-
由 Kohsuke Kawaguchi 提交于
Previously, a forked life cycle resulted in MavenBuildProxy2.start/end callbacks. When a module X build forks a life cycle and comes back to building module X, end callback from the fork completion made Jenkins believe that it's not building any module, when Maven is actually coming back to building module X. So if the sequence of mojos that follow the forked mojo produces a lot of output, it can saturate memory (and even if it doesn't, Jenkins fails to capture the entire log for a module.) This fix also addresses the synchronization problem, so that when we do split the log, we make sure all the output from Maven prior to that indeed arrived to the master.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 02 4月, 2012 6 次提交
-
-
由 Vojtech Juranek 提交于
Commented out getActions() as returns new copy of action list and thus breaks e.g. JUnitResultArchiver, which adds actions directly to the list (build.getActions().add(action)).
-
由 Vojtech Juranek 提交于
-
由 Vojtech Juranek 提交于
-
由 Vojtech Juranek 提交于
Conflicts: changelog.html
-
由 Vojtech Juranek 提交于
-
由 Kohsuke Kawaguchi 提交于
The trick for backward compatibility is in the default implementation that grants View.READ to those who have access to items.
-
- 01 4月, 2012 4 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 slavino 提交于
-
-
由 lvotypko 提交于
-
- 31 3月, 2012 2 次提交
-
-
由 Seiji Sogabe 提交于
-
由 Seiji Sogabe 提交于
-
- 30 3月, 2012 3 次提交
-
-
由 Richard Mortimer 提交于
Use a ping timeout of 3/4 of the ping interval instead of the default 4 minute timeout. This happens to workaround an issue in the remoting PingThread implementation which causes the ping to busy wait for the timeout period instead of keeping the channel alive.
-
由 Andrew Bayer 提交于
Fixed JENKINS-13129: Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
-
由 Andrew Bayer 提交于
[FIX JENKINS-12994] Quiet period is blocking other jobs in queue
-
- 29 3月, 2012 1 次提交
-
-
由 Olivier Lamy 提交于
Added another hyperlink to the console output of a blocked matrix build configuration. thanks
-
- 28 3月, 2012 9 次提交
-
-
由 Kohsuke Kawaguchi 提交于
There's some expected performance gain since people often deploy $JENKINS_HOME over NFS.
-
由 Kohsuke Kawaguchi 提交于
-
由 Vincent Latombe 提交于
-
由 Vincent Latombe 提交于
Queue#maintain() was returning too soon
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 27 3月, 2012 1 次提交
-
-
由 Alex Lehmann 提交于
[Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup changed bundled plugin detection, added unit test
-