- May 23, 2012
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
The actual fix was in c86aa679
-
Kohsuke Kawaguchi authored
The previous implementation was always appending the per-configuration unique suffix, making it impossible for different configuration builds to share workspaces. In this fix, we introduce a secondary field to control the workspace of sub-builds (which can be either absolute or relative to the matrix head workspace.)
-
- May 22, 2012
-
-
Olivier Lamy authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
exposed data about installed plugins, installable plugins, update center jobs, etc., to the REST API
-
Kohsuke Kawaguchi authored
-
- May 16, 2012
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
- May 14, 2012
-
-
Kohsuke Kawaguchi authored
-
- May 09, 2012
-
-
David Reiss authored
Previously, the untar code tries to set the last modified time and mode on every untarred file. However, if the tar contains a broken symlink, or a symlink that points to a file that has not been untarred yet, the time/mode setting would fail on the broken symlink. Symlinks don't have meaningful modified times or modes of their own, so only set these values on non-symlinks. Rename the file "a" in the test to expose the bug.
-
- May 08, 2012
-
-
Kohsuke Kawaguchi authored
-
- May 07, 2012
-
-
Kohsuke Kawaguchi authored
-
- May 06, 2012
-
-
Seiji Sogabe authored
-
- May 05, 2012
-
-
Fred G authored
-
Kohsuke Kawaguchi authored
-
- May 04, 2012
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
If a resource with 'Set-Cookie' header is cached (either by intermediary like HTTP proxy and reverse proxy, or by the browser), it'll cause identity swap / session mix-up as discussed in this ticket. I suspect this was caused by HttpSessionContextIntegrationFilter2, which is the only code path that attempts to create a session when a request to a static resource is made. So I'm disabling the creation of session in HttpSessionContextIntegrationFilter2. This in turn requires that we have sessions already created when the authentication was successful and people need to login (or else the login will have no effect.) We already do so in layout.jelly, so any request that renders a Jenkins page would have a session, but I've also added it in AuthenticationProcessingFilter2, which ensures that a successful login does have a session.
-
- May 03, 2012
-
-
Olivier Lamy authored
-
- Apr 30, 2012
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
- Apr 26, 2012
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Reynald Borer authored
When a client uses the buildWithParameters API and request a json output, return the job definition as a json string instead of doing a redirect on the job page.
-
Rob Petti authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
- Apr 25, 2012
-
-
Kohsuke Kawaguchi authored
Conflicts: changelog.html
-
Kohsuke Kawaguchi authored
(cherry picked from commit 2e5a7bf4)
-
Kohsuke Kawaguchi authored
-
- Apr 24, 2012
-
-
Kohsuke Kawaguchi authored
This reverts commit 9a1ad74b. The bits aren't yet synchronized to central apparently. Conflicts: changelog.html
-
Christoph Thelen authored
This is also related to [JENKINS-9778].
-
Kohsuke Kawaguchi authored
-
Jerome Lacoste authored
[FIXED JENKINS-8214] Added a DISCOVER permission to allow anonymous users to be presented the login screen when accessing job URLs
-
Vojtech Juranek authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-