Remove references to the fact that commit status support was introduced (2.5 years ago) in GitLab 8.1

README.md

@@ -2,7 +2,6 @@
 - [Introduction](#introduction)
 - [User support](#user-support)
 - [Known bugs/issues](#known-bugsissues)
-- [Supported GitLab versions](#supported-gitlab-versions)
 - [Configuring the plugin](#configuring-the-plugin)
     - [Global configuration and authentication](#global-configuration)
     - [Jenkins Job Configuration](#jenkins-job-configuration)
@@ -20,9 +19,9 @@ This plugin allows GitLab to trigger builds in Jenkins after code is pushed and/
 # User support
 
 If you have a problem or question about using the plugin, please make sure you are using the latest version. Then create an issue in the GitHub project if necessary. New issues should include the following:
-* GitLab plugin version (e.g. 1.2.0)
-* GitLab version (e.g. 8.1.1)
-* Jenkins version (e.g. 1.651.1)
+* GitLab plugin version (e.g. 1.5.2)
+* GitLab version (e.g. 10.5.1)
+* Jenkins version (e.g. 2.111)
 * Relevant log output from the plugin (see below for instructions on capturing this)
 
 Version 1.2.0 of the plugin introduced improved logging for debugging purposes. To enable it:
@@ -44,11 +43,6 @@ This is not an exhaustive list of issues, but rather a place for us to note sign
 * [#473](https://github.com/jenkinsci/gitlab-plugin/issues/473) - When upgrading from plugin versions older than 1.2.0, you must upgrade to that version first, and then to the latest version. Otherwise, you will get a NullPointerException in com.cloudbees.plugins.credentials.matchers.IdMatcher after you upgrade. See the linked issue for specific instructions.
 * [#608](https://github.com/jenkinsci/gitlab-plugin/issues/608) - GitLab 9.5.0 - 9.5.4 has a bug that causes the "Test Webhook" function to fail when it sends a test to Jenkins. This was fixed in 9.5.5.
 
-# Supported GitLab versions
-
-* GitLab versions 8.1.x and newer (both CE and EE editions) are supported via the GitLab [commit status API](https://docs.gitlab.com/ce/api/commits.html#commit-status) which supports with external CI services like Jenkins
-* Versions older than 8.1.x may work but are no longer officially supported
-
 # Configuring the plugin
 ## Global configuration
 ### GitLab-to-Jenkins authentication (required by default)
@@ -259,7 +253,7 @@ To use GitLab with Flexible Publish, configure the *Post-build Actions* as follo
 
 ## Gitlab Configuration
 
-GitLab 8.1 has implemented a commit status API, you need an extra post-build step to support commit status.
+You need an extra post-build step to support commit status.
 
 * In GitLab go to your repository's project *Settings*
     * Click on *Web Hooks*
@@ -273,7 +267,7 @@ GitLab 8.1 has implemented a commit status API, you need an extra post-build ste
         * GitLab should display "Hook successfully executed"
         * Jenkins project ``JENKINS_PROJECT_NAME`` should start
 
-* Add a post-build step *Publish build status to GitLab commit (GitLab 8.1+ required)* to the job.
+* Add a post-build step *Publish build status to GitLab* to the job.
 * For pipeline jobs surround your build step with the `gitlabCommitStatus` step like this:
 
     ```

src/main/java/com/dabsquared/gitlabjenkins/publisher/GitLabCommitStatusPublisher.java

@@ -99,7 +99,7 @@ public class GitLabCommitStatusPublisher extends Notifier implements MatrixAggre
 
         @Override
         public String getHelpFile() {
-            return "/plugin/gitlab-plugin/help/help-gitlab8.1CI.html";
+            return "/plugin/gitlab-plugin/help/help-send-result-to-gitlab.html";
         }
 
         public FormValidation doCheckName(@QueryParameter String value) {

src/main/resources/com/dabsquared/gitlabjenkins/publisher/Messages.properties

@@ -1,4 +1,4 @@
-GitLabCommitStatusPublisher.DisplayName=Publish build status to GitLab commit (GitLab 8.1+ required)
+GitLabCommitStatusPublisher.DisplayName=Publish build status to GitLab
 name.required=Build name required.
 GitLabMessagePublisher.DisplayName=Add note with build status on GitLab merge requests
 GitLabVotePublisher.DisplayName=Add vote for build status on GitLab merge requests

src/main/webapp/help/help-gitlab8.1CI.html

@@ -1,3 +0,0 @@
-<div>
-  Enable GitLab 8.1 Continuous Integration feature. <b>DO NOT ENABLE IF YOU'RE USING A VERSION BEFORE GITLAB 8.1</b>.
-</div>

src/main/webapp/help/help-send-result-to-gitlab.html

@@ -0,0 +1,3 @@
+<div>
+  Send build result to GitLab. It will be visible in the commit and/or merge request UI as appropriate. You must have at least one GitLab connection/server configured in the Jenkins global configuration. If you have more than one, select the appropriate one from the 'GitLab connection' dropdown menu in the job configuration.
+</div>