- Jul 23, 2011
-
-
alanharder authored
-
Kohsuke Kawaguchi authored
-
Jerome Lacoste authored
-
Jerome Lacoste authored
-
Jerome Lacoste authored
-
Kohsuke Kawaguchi authored
To be really correct, the crumb API call should be using the encoding specified in the HTTP response header, but doing so involves various header parsing, which is cumbersome. Since we know Jenkins always serve the API call in UTF-8 encoding, here I'm baking that assumption in.
-
Jerome Lacoste authored
-
Jerome Lacoste authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
allow advanced users to tweak this value, as someone reported in IRC that '@' in token is problematic for his environment.
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
- Jul 20, 2011
-
-
Vojtech Juranek authored
-
Vojtech Juranek authored
-
- Jul 19, 2011
-
-
Christoph Kutzinski authored
-
- Jul 18, 2011
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Christoph Kutzinski authored
-
- Jul 17, 2011
-
-
Kohsuke Kawaguchi authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
removed unused imports; fixed some generics warnings; added note about current XStream's StringConverter behaviour
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
honored correctly.
-
Kohsuke Kawaguchi authored
-
- Jul 16, 2011
-
-
Christoph Kutzinski authored
-