Merge pull request #274 from jenkinsci/old-baselines-cleanup

Remove the obsolete baselines section from README

Author: oleg-nenashev

README.md

@@ -84,109 +84,6 @@ be detected when using `-Dbenchmark`, however, `FooBar` will be ignored.
 
 See also: [documentation for JMH benchmarks](https://github.com/jenkinsci/jenkins-test-harness/blob/master/docs/jmh-benchmarks.adoc)
 
-## Baselines
-
-It is handy to be able to select different Jenkins baselines with a Maven profile.
-To set this up, you must edit your `~/.m2/settings.xml` to include some new entries in the `<profiles>` section.
-For example:
-
-```xml
-<profile>
-    <id>jenkins-289</id>
-    <properties>
-        <jenkins.version>2.89.2</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-273</id>
-    <properties>
-        <jenkins.version>2.73.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-260</id>
-    <properties>
-        <jenkins.version>2.60.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-246</id>
-    <properties>
-        <jenkins.version>2.46.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-232</id>
-    <properties>
-        <jenkins.version>2.32.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-219</id>
-    <properties>
-        <jenkins.version>2.19.4</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-27</id>
-    <properties>
-        <jenkins.version>2.7.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-651</id>
-    <properties>
-        <jenkins.version>1.651.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-642</id>
-    <properties>
-        <jenkins.version>1.642.4</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-625</id>
-    <properties>
-        <jenkins.version>1.625.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-609</id>
-    <properties>
-        <jenkins.version>1.609.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-596</id>
-    <properties>
-        <jenkins.version>1.596.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-580</id>
-    <properties>
-        <jenkins.version>1.580.3</jenkins.version>
-    </properties>
-</profile>
-<profile>
-    <id>jenkins-565</id>
-    <properties>
-        <jenkins.version>1.565.3</jenkins.version>
-        <jenkins-test-harness.version>1.565.3</jenkins-test-harness.version>
-    </properties>
-</profile>
-```
-
-Now for example if your plugin normally builds against 1.625.x, but you wish to test compatibility with 1.651.x,
-there is no need to edit your POM. Just run:
-
-    mvn -Pjenkins-651 clean test
-
-or
-
-    mvn -Pjenkins-651 hpi:run
-
 ## Setup Wizard
 
 By default, the setup wizard (Jenkins >= 2.0) is skipped when using `hpi:run`. If you want the wizard to be enabled just run: