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=-->
<li class=bug>
Revert ampersand encoding which can cause backwad incompatibility issue
(<a href="https://github.com/jenkinsci/jenkins/pull/683">pull 683</a>)
</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.504>What's new in 1.504</a> <!--=DATE=--></h3>
<li class='major bug'>
Maven 3.0.5 upgrade.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16965">issue 16965</a>)
<li class=bug>
Not all log messages were being captured at <code>/log/all</code>.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16952">issue 16952</a>)
<li class=bug>
Incorrect or missing XML encoding declaration on some REST API pages.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16881">issue 16881</a>)
<li class=bug>
Fixed: Human readable file size method returns ",00" for files with byte length 0
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16630">issue 16630</a>)
Jesse Glick
committed
<li class=bug>
“Build” from job context menu produced a confusing warning page.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16844">issue 16844</a>)
Christoph Kutzinski
committed
<li class=bug>
Maven2 builds with non-standard test plugins failed.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16928">issue 16928</a>)
<li class=rfe>
Started bundling XStream 1.4.4
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-12542">issue 12542</a>)
<li class=rfe>
Significant improvement in Traditional Chinese localizations.
(<a href="https://github.com/jenkinsci/jenkins/pull/716">pull 716</a>)
</div><!--=END=-->
<h3><a name=v1.503>What's new in 1.503</a> (2013/02/26)</h3>
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
<ul class=image>
<li class=bug>
${ITEM_FULLNAME} variable was not working for Maven projects on Windows,
so introduced ${ITEM_FULL_NAME} instead.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-12251">issue 12251</a>)
<li class=bug>
Lock contention issue in build history view.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16831">issue 16831</a>)
<li class=bug>
Fixed the HTTP request thread saturation problem with Winstone.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16474">issue 16474</a>)
<li class=bug>
Script evaluation script error on IE.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16561">issue 16561</a>)
<li class=bug>
surefire-reports not detected for android-maven-plugin
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16776">issue 16776</a>)
<li class=bug>
maven-failsafe-plugin tests not recognized anymore
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16696">issue 16696</a>)
<li class=bug>
UI waiting on a queue lock to display cause of queue blockage.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16833">issue 16833</a>)
<li class=bug>
UpdateCenter REST API chokes if there was a plugin installation failure.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16836">issue 16836</a>)
<li class=bug>
Missing build title in /rssAll when build has no test result.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16770">issue 16770</a>)
<li class=bug>
Changed the way matrix axis values are exposed as env variables
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-11577">issue 11577</a>)
<li class=bug>
Maven 3 builds ignored quiet (-q) and debug (-X) options
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16843">issue 16843</a>)
<li class=rfe>
JNLP slave installers can now work transparently with secured Jenkins.
(SECURITY-54 / despite the ticket marker, this is not a security vulnerability)
<li class=rfe>
"Discard old build records" behavior is now pluggable, allowing plugins to define custom logic.
</ul>
<h3><a name=v1.502>What's new in 1.502</a> (2013/02/16)</h3>
<li class='major bug'>
Miscellaneous security vulnerability fixes. See the advisory for more details.
(SECURITY-13,16,46,47,54,55,59,60,61)
<li class='major bug'>
Builds disappear from build history after completion.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-15156">issue 15156</a>)
<li class=bug>
Plugin Manager’s Filter field did not work. Regression in 1.500.
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16651">issue 16651</a>)
<li class=bug>
DISCOVER-able jobs break the build queue widget
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16682">issue 16682</a>)
<li class=rfe>
Extension point to provide access to workspace even when node is offline
(<a href="https://issues.jenkins-ci.org/browse/JENKINS-16454">issue 16454</a>)
<li class=rfe>
Extension point to listen BuildStep execution
<h3><a name=v1.501>What's new in 1.501</a> (2013/02/10)</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>)
<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.
Loading
Loading full blame...