Permalink
Commits on Mar 20, 2011
  1. [FIXED JENKINS-6128] NPE during run - fingerprint cleanup thread

    ssogabe committed Mar 20, 2011
        A job without a firstBuild is not causing an NPE anymore.
Commits on Mar 19, 2011
  1. removed unused import

    kutzi committed Mar 19, 2011
  2. i18n & l10n(ja) for title.

    ssogabe committed Mar 19, 2011
  3. prevent NPE

    olamy committed Mar 19, 2011
  4. i18n &l10n(ja)

    ssogabe committed Mar 19, 2011
  5. fixed runtimw exception

    ssogabe committed Mar 19, 2011
  6. more details in the log

    olamy committed Mar 19, 2011
  7. changelog for 9084

    olamy committed Mar 19, 2011
  8. [FIXED JENKINS-9084] Regression in jenkins .401 maven plugin - deploy…

    olamy committed Mar 19, 2011
    … to repository post-task
    
    logic to get remote settings.xml file, test in this order (as maven do)
    1. configured alternateSettings
    2. ~/.m2/settings.xml
    3. $M2_HOME/conf/settings.xml
  9. [FIXED JENKINS-9050] Improved the error diagnostics when a remote met…

    kohsuke committed Mar 19, 2011
    …hod call fails to deserialize.
  10. Merge branch 'ja'

    ssogabe committed Mar 19, 2011
  11. added japanese localization.

    ssogabe committed Mar 19, 2011
  12. [FIXED JENKINS-9062] Fixed a bug in persisting user configuration tha…

    kohsuke committed Mar 19, 2011
    …t causes NPE in some plugins
  13. Merge branch 'oss'

    kohsuke committed Mar 19, 2011
  14. Integrated a module that retains an RSA key pair as an identity.

    kohsuke committed Mar 19, 2011
    This is a proof of concept to core modulizarion (by binary integration.)
    A module is built like a plugin but it's packaged to the war as a
    WEB-INF/lib/*.jar, not as a plugin.
    
    Compared to plugins, jars integrated in this way do not double-package
    dependency jars, and they are not visible to the users. I plan to try a
    few of these and if it's useful, this could be an useful mechanism for
    modularizing core.
Commits on Mar 18, 2011
  1. [FIXED JENKINS-9102] Changed buildListTable column name from Date to …

    abayer committed Mar 18, 2011
    …Time Since, to reflect actual content.
  2. doc improvement

    kohsuke committed Mar 18, 2011
Commits on Mar 17, 2011
  1. Merge remote branch 'origin'

    Olav Reinert
    Olav Reinert committed Mar 17, 2011
  2. [FIXED JENKINS-9011]: openSUSE: HOME path problem

    Olav Reinert
    Olav Reinert committed Mar 17, 2011
    Added a configuration option to control initialization of the
    environment of the Jenkins server process.
  3. openSUSE: Jenkins sysconfig permissions.

    Olav Reinert
    Olav Reinert committed Mar 17, 2011
  4. Merge remote branch 'origin'

    Olav Reinert
    Olav Reinert committed Mar 17, 2011
  5. [FIXED JENKINS-8748]: openSUSE: required JDK

    Olav Reinert
    Olav Reinert committed Mar 17, 2011
    For openSUSE it doesn't make sense to require a specific flavor of JRE
    for Jenkins. Even if the RPM explicitly requires the Oracle JDK, thus
    causing it to be installed together with Jenkins, some previously installed
    JRE may still be used to run Jenkins, due to the update-alternatives(8) setting.
    The JRE to use is a sysadmin issue, and not usually part of the RPM spec.
    
    I have not been able to reproduce the scenario described by David.
    Installing Jenkins on fresh installs of openSUSE since v11.1 pulls in openJDK
    1.6 with it, with which Jenkins runs just fine. Even on Live CDs.