Skip to content
  1. Jan 14, 2012
    • Sami Tikka's avatar
      OS X installer can run Jenkins as user "jenkins" · f8f48607
      Sami Tikka authored
      User has to choose a custom installation.
      There are two choices:
      - Start at boot as "daemon" (enabled by default)
      - Start at boot as "jenkins" (disabled by default)
      
      If user disables the first and enable the latter, the installer
      will create a new user "jenkins" and new group "jenkins"
      (if they do not exist), chown JENKINS_HOME to jenkins:jenkins
      and set up launchd job to run Jenkins as "jenkins"
      
      Also fixed some permission errors that PackageMaker complains about
      when building the package.
      
      Also PackageMaker xml file reformatted to be more readable
      f8f48607
  2. Jan 13, 2012
  3. Jan 11, 2012
    • Kohsuke Kawaguchi's avatar
      [FIXED CLOUDBEES-2296] · 70838bfa
      Kohsuke Kawaguchi authored
      Fixed a bug in Winstone where a failure during request processing can
      put Winstone out of sync with the next request.
      70838bfa
  4. Jan 10, 2012
  5. Jan 09, 2012
  6. Jan 08, 2012
  7. Jan 06, 2012
  8. Jan 05, 2012
  9. Jan 04, 2012
  10. Jan 03, 2012
  11. Dec 31, 2011
  12. Dec 27, 2011
  13. Dec 26, 2011
  14. Dec 25, 2011
  15. Dec 24, 2011
  16. Dec 20, 2011
  17. Dec 17, 2011
    • Kohsuke Kawaguchi's avatar
      [FIXED JENKINS-11204] · a41fb84e
      Kohsuke Kawaguchi authored
      Don't let the partially loaded Jenkins cause a possible data loss.
      a41fb84e
    • Kohsuke Kawaguchi's avatar
    • Kohsuke Kawaguchi's avatar
      [CLOUDBEES-2018] fixing the root cause. · dcbdbcc5
      Kohsuke Kawaguchi authored
      At some point after this code was originally written, I/O in remoting
      became asynchronous. So we need to sync with that before we swap out
      the new log output stream, or else you cut off stuff at the wrong
      moment.
      
      Normally the command transfer in remoting is slow enough that
      you get more or less synchronized output anyway, which is why
      this poblem remained unnoticed.
      
      But if the uncliamed buffer gets large, write operation will take a long
      time, which makes this issue more likely to show up.
      
      This fix address this problem by doing a proper sync.
      The recycling of ByteArrayOutputStream is also disabled because it makes
      synchronization tricky.
      dcbdbcc5