- 12 5月, 2016 12 次提交
-
-
由 Ing. Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
The logic is moved from template back to Java and modified to fix the issue. The argorithm is rewritten for better legibility.
-
由 Oleg Nenashev 提交于
-
由 Oliver Gondža 提交于
[JENKINS-32777] Cover 'delete-builds' CLI by tests
-
由 Daniel Beck 提交于
-
由 Kohsuke Kawaguchi 提交于
Conflicts: changelog.html
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
- 11 5月, 2016 9 次提交
-
-
由 Ing. Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
Slighty optimized and better legible asserts
-
由 Ing. Pavel Janousek 提交于
-
由 Oleg Nenashev 提交于
[JENKINS-34710] - PluginWrapper should not throw IOException if somebody enables the enabled plugin (#2327)
-
由 Alex Earl 提交于
* Remove CVS historical code - JENKINS-4610 * Fix whitespace issue
-
由 Pavel Janousek 提交于
reload-configuration covered by test-cases
-
由 pagio81 提交于
More details: https://issues.jboss.org/browse/WFLY-4782
-
由 Baptiste Mathus 提交于
-
- 10 5月, 2016 4 次提交
-
-
由 Oliver Gondža 提交于
-
由 Oleg Nenashev 提交于
[JENKINS-34674,JENKINS-34675] - Handling of the default update site ID
-
由 Baptiste Mathus 提交于
As detailed by @stephenc: > So there is `getInstanceOrNull()` which is for use in Jenkins core or > in code that plugins add that may escape the Jenkins singleton > lifecycle. > > In regular plugins `getInstance()` will never return null as the > lifecycle does not instantiate them until after there is a Jenkins > singleton and the plugins will be stopped before there is no > singleton. > > The `getActiveInstance()` is therefore equivalent to `getInstance()` > and should never have been born. > > The only way a plugin can get a `null` from `Jenkins.getInstance()` is > if you install an `atExit()` handler, use a `PhantomReference` type > thing, or directly manipulate the servlet container in some way or > other. A correctly written plugin should unwind any of those things > when it is stopped or a method bound to the termination lifecycle. If > there are some cases (for which I cannot anticipate a good coder being > able to write a correct termination lifecycle method to fix) where the > code cannot be unhooked... then in those cases the plugin should use > `getInstanceOrNull()` and know how to respond to the `null` that could > not be avoided.
-
由 Daniel Beck 提交于
[JENKINS-34328] CLI command disconnect-node extracted from core to CLI
-
- 09 5月, 2016 9 次提交
-
-
由 Carlos Sanchez 提交于
[JENKINS-34683] - Do not print stack trace if plugin is missing dependencies
-
由 Kanstantsin Shautsou 提交于
Workflow users may want to catch specific Exceptions without stracktrace in future.
-
由 Manuel Recena 提交于
-
由 Daniel Beck 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jean-Philippe Briend 提交于
* Add French translation on New Item screen * Add French translation to Manage Jenkins page * Add French translation to GlobalToolConfiguration page * Add missing French translation to Manage Jenkins page * Correct translations typos and PR remarks
-
由 Oleg Nenashev 提交于
-
- 08 5月, 2016 3 次提交
-
-
由 Tom Fennelly 提交于
HttpSession listener ExtensionPoint
-
由 Oleg Nenashev 提交于
-
由 Oleg Nenashev 提交于
[FIXED JENKINS-34675] - Prevent hanging of the WebUI if the default Update Site ID cannot be resolved. Also hardens the Java code a bit.
-
- 06 5月, 2016 3 次提交
-
-
由 Daniel Beck 提交于
[JENKINS-34601] Fix help file for node name attribute
-
由 Daniel Beck 提交于
[FIX JENKINS-31611] Restrict access to plugin pages
-
由 Daniel Beck 提交于
-