- 24 11月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
Not fully solved, since the scannedDirs field can still grow to be large, but at least clearing files/dirsNotIncluded. Also imposing a 5s timeout on the scan regardless of file count, and defining a user-customizable bound.
-
- 23 11月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
-
- 22 11月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
[JENKINS-25691] Might have prevented the need for: https://github.com/jenkinsci/maven-plugin/pull/33
-
- 21 11月, 2014 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
ssh-slaves plugin can leverage this to try to obtain the state of the slave JVM via SSH. Reference: ZD-23093
-
由 Kohsuke Kawaguchi 提交于
Reference: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8051847 Reference: ZD-23093
-
由 Kohsuke Kawaguchi 提交于
Reference: ZD-23093
-
- 20 11月, 2014 1 次提交
-
-
由 Fernando Boaglio 提交于
-
- 19 11月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
- 18 11月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
Caused a failure in hudson.plugins.promoted_builds.conditions.ManualConditionTest.testManualPromotionProcessViaWebClient when run against 1.580.1.
-
- 17 11月, 2014 8 次提交
-
-
由 Stephen Connolly 提交于
Allow Projects to take the Queue.Item's actions into consideration when determining their default authentication
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
- Also tidy up some holes in locking strategy that can cause builds to be scheduled on executors that are about to be interrupted or nodes in the process of being removed
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 14 11月, 2014 1 次提交
-
-
由 intelradoux 提交于
The "it.value" don't exist, so we need to set the defaultParameterValue. It help me display correctly parameter for my multilauncher plugin. Note that other ParameterDefinition use the default value to display parameter, so IMO it is safe to do this.
-
- 13 11月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
AtomicFileWriter.commit should use Util.deleteFile so as to get a more meaningful error message in case the deletion fails. The following is not helpful in terms of diagnosing the root problem: java.io.IOException: Unable to delete /…/jobs/demo/builds/…/workflow/3.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:179) at org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage.saveActions(SimpleXStreamFlowNodeStorage.java:106) at …
-
- 12 11月, 2014 3 次提交
-
-
由 Cyrille Le Clerc 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
The use case that led me here was to use this from workflow which relies primarily on Java serialization
-
- 11 11月, 2014 2 次提交
-
-
由 Nicolas De Loof 提交于
-
由 Jesse Glick 提交于
-
- 10 11月, 2014 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 08 11月, 2014 4 次提交
-
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
IIUC, the issue here is that the request in question contains both a valid session cookie AND basic authentication header, and that path results in a failure because BasicHeaderProcessor expects one of BasicHeaderAuthenticators to validate the basic authentication header (without knowing that there's already a valid Authentication object that came from the HTTP session, yet no BasicHeaderAuthenticator actually processes this because BasicHeaderRealPasswordAuthenticator backs away from doing that. I think the corect fix is for BasicHeaderRealPasswordAuthenticator to get rid of authenticationIsRequired check. This check instead belongs to BasicHeaderProcessor, where it should be used to check if any BasicHeaderAuthenticator should be consulted or not. The problem with having this logic in BasicHeaderRealPasswordAuthenticator is that this is just an implementation of an extension point, and thus it needs to be removable. As it stands right now in this fix, if this impl is removed, JENKINS-25144 will be back again.
-
由 Christof Schoell 提交于
return authentication object instead of null if authentication is not required - otherwise valid login fails with basic authentication
-
由 Oleg Nenashev 提交于
jenkins.model.Jenkins::getInstance() method is marked as @CheckForNull, but the most of Jenkins code does not actually check the return value. It leads to tons of static analysis errors, hence it is hard to analyze the code. The change also adds annotations to old methods like Hudson::getInstance() Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
- 07 11月, 2014 2 次提交
-
-
由 Oliver Gondža 提交于
-
由 Jesse Glick 提交于
-
- 06 11月, 2014 3 次提交
-
-
由 Oliver Gondža 提交于
-
由 Oliver Gondža 提交于
-
由 Jesse Glick 提交于
[JENKINS-2786] Makes no sense for Computer.currentComputer to return MasterComputer when not on an executor thread.
-
- 05 11月, 2014 3 次提交
-
-
由 Holger Voormann 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
This matches fb65a2c3c8584a9ac4daa49ecbce7a540dc7f5a5 in remoting.
-