As this is my first look inside Jenkins codebase I not sure it's correct
but perhaps artifacts for modulebuilds should be deleted just as logs
are deleted. see https://issues.jenkins-ci.org/browse/JENKINS-17508
I did not fully test it yet, all unit tests ran fine, but didn't succeed
to run jobs inside Jenkins, due to classloader issues while running
Jenkins in Jetty, to verify deletion
adds test that looks in jobs archive with 2 builds when LogRotator set as build discarder with settings to keep only 1 build with artifacts, test searches for jars in archive for build one and build two expecting no jars in build 1 and expecting jars in build 2
add documentation to testcase.
also testing the removal of build if LogRotator is configured to discard
old builds and not only artifacts (Not needed for the issue, but an
extra test is not a luxury )
JENKINS-17508 updated the test to use @Rule and no longer extend from the old HudsonTestCase (shouldn't that one be marked deprecated?), add @ Bug and @ For as jesse suggested
JENKINS-17508 removed usage of deprecated elements in test
add global maven config to define default settings providers
changed the filepath#toUri call to #getRemote as per comment of @jglick
Merge pull request #759 from redlab/JENKINS-17508

[FIXED JENKINS-17508] Artifacts not being deleted by LogRotator
[JENKINS-17508] Noting.
Diagnosis for test failure.
https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/850/testReport/jenkins.security/RekeySecretAdminMonitorTest/testBasicWorkflow/
com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 400 Bad Request for http://localhost:60027//administrativeMonitor/jenkins.security.RekeySecretAdminMonitor/scan
	at com.gargoylesoftware.htmlunit.WebClient.throwFailingHttpStatusCodeExceptionIfNecessary(WebClient.java:549)
	at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:333)
	at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:357)
	at com.gargoylesoftware.htmlunit.html.HtmlForm.submit(HtmlForm.java:196)
	at org.jvnet.hudson.test.HudsonTestCase.submit(HudsonTestCase.java:1178)
	at jenkins.security.RekeySecretAdminMonitorTest.testBasicWorkflow(RekeySecretAdminMonitorTest.java:112)
java.lang.Exception: Invalid request submission
	at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:79)
	at jenkins.security.RekeySecretAdminMonitor.doScan(RekeySecretAdminMonitor.java:117)
Add extension point to rewrite JUnit test names

This adds an extension point, TestNameTransformer, which is called to transform JUnit test case names.
This is useful for JVM languages like scala which are more flexible than java with identifier naming.
Scala, for example, allows you to write test names between back ticks, and then encodes the name using valid java identifiers.
This extension point would allow a plugin to transform those names back in to readable names when they are displayed on the test result page.
If an optional component cannot be loaded, print a polite one-line message, not a big scary stack trace.
(To reproduce: BuildNowTextPropertyTest from cloudbees-template warns about FolderProxyGroupContainer.)
Merge pull request #769 from dnadolny/master

[FIXED JENKINS-17478] Add extension point to rewrite JUnit test names
try using defaulting of dropdownDescriptorSelector
[FIXED JENKINS-17723] add test cases to verify defaulting global settings providers
[FIXED JENKINS-17858] allow <f:dropdownDescriptorSelector> to be defaulting to a specifig instance
Merge pull request #772 from imod/default-maven-settings

FIXES JENKINS-17723 - Default maven settings
Good change !
Update changelog.html

changelog entry for JENKINS-17723
Merge pull request #771 from imod/dropdownDescriptorSelector-defaulting-to-instance

[FIXED JENKINS-17858] allow <f:dropdownDescriptorSelector> to be defaulting to an instance