- 24 3月, 2014 1 次提交
-
-
由 Harald Albers 提交于
-
- 22 3月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-19544] When OldDataMonitor is reported a Run, just remember the ID rather than holding a strong reference.
-
由 Jesse Glick 提交于
[JENKINS-19544] Whether or not we manage to save an object with old data, be sure to remove it from the list, and continue with other objects. Otherwise a bug like JENKINS-20950 can prevent *anything* from being saved, and holds references to all the old data.
-
- 21 3月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Protect the common thread pool against poorly written tasks that do not restore original context classloader. Reference: RM-2329 in CloudBees
-
- 20 3月, 2014 5 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
list-jobs should print names, not display names, since people expect to be able to feed the results into other CLI commands.
-
由 Jesse Glick 提交于
-
- 19 3月, 2014 3 次提交
-
-
由 Jesse Glick 提交于
See comments in ce7e6390; and note reverted 71f3acfc.
-
由 Kohsuke Kawaguchi 提交于
This reverts commit 71f3acfc. Test regressions
-
由 Kohsuke Kawaguchi 提交于
Not sure why it didn't in ce7e6390.
-
- 18 3月, 2014 4 次提交
-
-
由 Jesse Glick 提交于
-
由 Oleg Nenashev 提交于
The fix allows to explicitly disable automatic page refreshes in the @view extensions. Resolves https://issues.jenkins-ci.org/browse/JENKINS-21190Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
- 15 3月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
-
- 14 3月, 2014 4 次提交
-
-
由 Jesse Glick 提交于
There seems to be no way to export this over the REST API without incurring serious performance penalties.
-
由 Kohsuke Kawaguchi 提交于
-
由 phoenix384 提交于
-
由 phoenix384 提交于
-
- 13 3月, 2014 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 12 3月, 2014 7 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
See javadoc for discussion why this possibly redundant use is desirable
-
由 Kohsuke Kawaguchi 提交于
I think the cleanest place to do this is as a filter of UserDetailsService. The problem is that SecurityRealm defines loadUserByName method, which AbstractPasswordBasedSecurityRealm overrides
-
由 Kohsuke Kawaguchi 提交于
So ApiTokenFilter no longer needs to do that.
-
由 Kohsuke Kawaguchi 提交于
Jenkins now remembers the authorities (read group memberships) that the user had carried when he/she last time interactively logged in. This information is exposed via User.impersonate(), which is used when using Jenkins SSH, Jenkins CLI, or access via API tokens. Previously this was impossible for a subset of SecurityRealms that does not allow us to read group membership information without successful login (such as Active Directory, OpenID, etc.) For security reasons, if the backend determines that the user does not exist (as opposed to the backend who cannot tell if the user exists or not), then the impersonation will fail. I need to check AD plugin is reporting a failure correctly in this case, before marking as JENKINS-20064 fixed.
-
由 Kohsuke Kawaguchi 提交于
An unexpected failure in processing remember me cookie should be handled gracefully. In particular, possibly problematic cookie should be removed, or else the browser will keep bombarding the server with the same cookie, and will never be able to get through. It's much better to just drop the cookie.
-
由 Kohsuke Kawaguchi 提交于
-
- 11 3月, 2014 7 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Michal Srb 提交于
-
由 christ66 提交于
-
由 christ66 提交于
-
由 Jesse Glick 提交于
(Left the upstream pseudo-trigger out of this, as it is pretty hackish and might not generalize well—requires Publisher’s to make any sense.)
-
- 09 3月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
* Use model-links with context menu * Show the display name of the linked job * If the build isn't available, but the job is, still link to the job
-
- 08 3月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
If the result needs to be SUCCESS, it needs to be called 'stable', not 'successful' -- the latter is UNSTABLE or better. References: - PermalinkProjectAction (lastStableBuild for SUCCESS, lastSuccessfulBuild for UNSTABLE or better) - Last Successful list view column (includes unstable builds), Last Stable column (doesn't)
-