Newer
Older
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
We record noteworthy changes in this file, which then becomes http://jenkins-ci.org/changelog
- Record your changes between "TRUNK-BEGIN" and "TRUNK-END".
(except in rare cases when you are making changes in the RC branch,
in which case it goes to the rc section)
- There are four CSS classes to denote the kind of changes.
"rfe" for enhancement and "bug" for bug fixes,
plus "major" to indicate major RFE/bugfix.
- Link to bugs in the issue tracker, e-mail thread in the archive, and so on if you can.
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Changelog</title>
<link rel="stylesheet" TYPE="text/css" href="changelog.css">
<!--[if IE]>
<style type="text/css">div.rate-offset { bottom: 0.2em !important; left: 5em !important; }</style>
<![endif]-->
<script type="text/javascript" src="/rate/rate.js"></script>
</head>
<body>
<div align="right">Legend:
<span class="iconlegend">
<img src="images/rfe2.gif" alt="major RFE">major enhancement <img src="images/rfe.gif" alt="RFE">enhancement
<img src="images/bug2.gif" alt="major bug">major bug fix <img src="images/bug.gif" alt="bug">bug fix
</span><span style="visibility:hidden">xxxxx</span>
</div>
<div id="ratings" style="display:none; font-size:120%;
border:1px solid black; background-color:#eee; padding:0.5em; margin-bottom:1em">
Help other Jenkins users by letting the community know which releases you've used,
and whether they had any significant issues. <br>
Legend: <br>
<img src="http://ci.jenkins-ci.org/images/16x16/health-80plus.gif" width="16" height="16"
alt="Sunny"> = I use it on my production site without major issues. <br>
<img src="http://ci.jenkins-ci.org/images/16x16/health-40to59.gif" width="16" height="16"
alt="Cloudy"> = I don't recommend it. <br>
<img src="http://ci.jenkins-ci.org/images/16x16/health-00to19.gif" width="16" height="16"
alt="Lightning"> = I tried it but rolled back to a previous version. <br>
View ratings below, and click one of the icons next to your version to provide your input.
</div>
<a href="" onClick="document.getElementById('trunk').style.display=document.getElementById('rc').style.display='block';return false">
Upcoming changes</a>
<a href="" style="padding-left:3em" onClick="return loaddata(this)">Community ratings</a>
<!-- Record your changes in the trunk here. -->
<div id="trunk" style="display:none"><!--=TRUNK-BEGIN=-->
<ul class=image>
<li class=>
</ul>
</div><!--=TRUNK-END=-->
<!-- these changes are controlled by the release process. DO NOT MODIFY -->
<div id="rc" style="display:none;"><!--=BEGIN=-->
<h3><a name=v1.501>What's new in 1.501</a> <!--=DATE=--></h3>
<li class='major bug'>
Reverted change in 1.500 causing serious regression in HTTPS reverse proxy setups.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16368">issue 16368</a>)
<li class='major bug'>
Getting test results from custom test mojos failed build.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16573">issue 16573</a>)
Christoph Kutzinski
committed
<li class='major bug'>
Restored Java 5 compatibility.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16554">issue 16554</a>)
<li class=bug>
Bogus “Build Record Root Directory” inadequately diagnosed.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16457">issue 16457</a>)
<li class=bug>
Plugin icons in the sidebar were not being properly cached.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16530">issue 16530</a>)
<li class='major bug'>
Broadly as well as deeply nested build causes overwhelmed the UI after 1.482.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-15747">issue 15747</a>)
<li class=bug>
API typo <code>DependecyDeclarer</code> corrected.
<li class=bug>
Avoid eagerly loading builds in <b>Changes in dependency</b> or culprit list.
(<a href="https://github.com/jenkinsci/jenkins/pull/689">pull 689</a>)
<li class=bug>
Run parameters do not support folders.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16462">issue 16462</a>)
<li class=bug>
Fixed RememberMe cookie signature generation.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16278">issue 16278</a>)
<li class=bug>
Fixed NullPointerException when copying from existing Maven job
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16499">issue 16499</a>)
</div><!--=END=-->
<h3><a name=v1.500>What's new in 1.500</a> (2013/01/26)</h3>
<li class=bug>
Since 1.494, when signing up as a new user in the private security realm the email address was left unconfigured and a stack trace printed.
<li class=rfe>
Enable transparent log decompression support.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-13655">issue 13655</a>)
<li class=rfe>
Display authorities at <code>/user/*</code> for convenience.
(<a href="https://github.com/jenkinsci/jenkins/pull/577">pull 577</a>)
<li class=bug>
Slow rendering of view pages in large installations due to eager check whether the “People” link would show anything.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16244">issue 16244</a>)
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
<li class=bug>
Reduced size of memory leak in render-on-demand functionality used e.g. in configuration pages.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16341">issue 16341</a>)
<li class=bug>
Improving responsiveness of <b>People</b> page.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16342">issue 16342</a>)
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16397">issue 16397</a>)
<li class=bug>
Exception printed to log while adding <b>Build other projects</b> post-build step.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16444">issue 16444</a>)
<li class=bug>
<code>BindException</code> when using <code>--daemon</code> with JMX.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-14529">issue 14529</a>)
<li class=bug>
Improved logging and error output from SSHD in Jenkins.
<li class=rfe>
Linking to the <code>/threadDump</code> page from <code>/systemInfo</code> so it is discoverable.
<li class='major bug'>
Rekeying operation (from SECURITY-49 fix in 1.498) failed on Windows.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16319">issue 16319</a>)
<li class=bug>
JNLP slave index page failed to explain how to pass <code>-jnlpCredentials</code>.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16273">issue 16273</a>)
<li class=bug>
Links should preserve used protocol
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16368">issue 16368</a>)
<li class=bug>
Don't report the same plugin twice in the update center if the filtering is in effect.
<li class=bug>
Accept any plugin with a 'test' goal as a test plugin in Maven jobs
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-8334">issue 8334</a>)
<li class=rfe>
Avoid unnecessary downloads if automatically installed tools are up-to-date
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16215">issue 16215</a>)
<h3><a name=v1.499>What's new in 1.499</a> (2013/01/13)</h3>
<ul class=image>
<li class=bug>
Fixed <tt>NoClassDefFoundError: Base64</tt> with the <tt>-jnlpCredentials</tt> option.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-9679">issue 9679</a>)
</ul>
<h3><a name=v1.498>What's new in 1.498</a> (2013/01/07)</h3>
<ul class=image>
<li class='major bug'>
The master key that was protecting all the sensitive data in <tt>$JENKINS_HOME</tt> was vulnerable.
(SECURITY-49)
</ul>
<h3><a name=v1.497>What's new in 1.497</a> (2013/01/06)</h3>
<ul class=image>
<li class=bug>
Delete the oldest build but it still come up on HistoryWidget
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16194">issue 16194</a>)
</ul>
<h3><a name=v1.496>What's new in 1.496</a> (2012/12/30)</h3>
<li class=bug>
Aborting download of workspace files make Jenkins unstable
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-7114">issue 7114</a>)
<li class=bug>
Unstable main build of maven projects leads to post steps being executed even if configured not to
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-14102">issue 14102</a>)
<li class=bug>
Channel is already closed exception during threadDump
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16193">issue 16193</a>)
<h3><a name=v1.495>What's new in 1.495</a> (2012/12/24)</h3>
<li class=bug>
Fixed <tt>java.lang.NoSuchMethodError: hudson.model.RunMap.put(Lhudson/model/Run;)Lhudson/model/Run;</tt>
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-15487">issue 15487</a>)
Stephen Connolly
committed
<li class=bug>
Saving the update center list after the metadata has been fetched results in
the metadata being persisted twice
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-15889">issue 15889</a>)
<li class=rfe>
When using container-managed security, display unprotected root actions in the configuration screen for convenience.
<li class=rfe>
Display class loading statistics in <code>/computer/<i>name</i>/systemInfo</code>.
<li class=rfe>
Added <tt>list-plugins</tt> CLI command.
<li class=rfe>
Added <tt>console</tt> CLI command that dumps console output from a build.
<h3><a name=v1.494>What's new in 1.494</a> (2012/12/16)</h3>
Jesse Glick
committed
<li class=bug>
Using file parameters could cause build records to not load.
Loading
Loading full blame...