- 29 3月, 2013 7 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
To reproduce SUREFIRE-974 prior to this fix, pick an arbitrary group class to (not) exclude: mvn -f test/pom.xml -Dtest=CoreJellyTest -DexcludedGroups=hudson.ExtensionPoint test
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
Instead, it shows a small 'v' icon to the right that needs to be clicked to open a context menu.
-
- 28 3月, 2013 8 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-17330] FilePath.installIfNecessaryFrom should avoid routing download over remoting channel.
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
Otherwise you get nonsense like this: Cannot delete this build, because it is #3 depends on this
-
由 Jesse Glick 提交于
confirmDelete (and confirmDeleteAll) already say why a build cannot be deleted (and prevent you from proceeding), so no need to hide the Delete link in this case.
-
由 Jesse Glick 提交于
-
- 27 3月, 2013 1 次提交
-
-
由 Jesse Glick 提交于
-
- 26 3月, 2013 24 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
Conflicts: changelog.html
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
Revert "[JENKINS-17337] Added test for NPE.(cherry picked from commit 1bf958af)" This reverts commit 18b5f4f1. It looks like this change depends on other test harness related changes. It doesn't build on this branch.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
[JENKINS-17337] Added test for NPE.(cherry picked from commit 1bf958af)
-
由 Jesse Glick 提交于
[FIXED JENKINS-3265] Hotfix for regression in matrix project loading from 25084f52.(cherry picked from commit 3370e6ed)
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
[FIXED JENKINS-7291] Permit flyweight tasks to run on master even when it has zero configured executors. Always adding Computer for master as a fallback The original proposed fix for JENKINS-7291 creates a Computer object transitively. This seems unwise as it violates the design of Computer as stated in the javadoc, and for example we can end up creating two Computers for the master. I think a better fix is to create a Computer for the master all the time, even if there's no executors configured. The discrimination in Queue.makeBuildable would ensure that such phantom Computer is only used as a last resort (statistically speaking). I've also tweaked executors.jelly a bit. I simplified it somewhat based on the idea that "if there's only one computer to show, the context is likely making it obvious". (I must be missing the intricacy in the current code.) Originally developed in a branch at 2c5b57fcc1f39ed39057254e802f4183db5aa0dc then squashed for clarity.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
as I was playing with it to understand what those logics mean.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-