Merge pull request #39 from dwnusbaum/migrate-wiki-content

Migrate wiki content to GitHub and add 2.10 release notes

Author: dwnusbaum

CHANGELOG.md

@@ -0,0 +1,95 @@
+## Changelog
+
+### 2.10
+
+Release date: 2020-01-22
+
+-   Fix: When using the `checkout` step with `changelog: true` (the default), if 
+    the SCM leaves the changelog file completely empty, delete it instead of
+    passing the empty changelog file to other APIs. ([JENKINS-59560](https://issues.jenkins-ci.org/browse/JENKINS-59560), [JENKINS-57918](https://issues.jenkins-ci.org/browse/JENKINS-57918))
+
+### 2.9
+
+Release date: 2019-06-07
+
+-   Fix: Use `rw-r--r--` (0644) permissions for changelog files on Posix
+    systems as in version 2.7 and earlier of this plugin rather
+    than `rw------- (0600)` as used in version 2.8 to avoid potential
+    issues related to backups and similar scenarios. ([PR
+    34](https://github.com/jenkinsci/workflow-scm-step-plugin/pull/34))
+
+### 2.8
+
+Release date: 2019-06-05
+
+-   Fix: Prevent SAXParseException from being thrown when using
+    the `checkout` step in parallel blocks.
+    ([JENKINS-34313](https://issues.jenkins-ci.org/browse/JENKINS-34313))
+
+### 2.7
+
+Release date: 2018-10-01
+
+-   Fix: Prevent ConcurrentModificationException when using
+    the `checkout` step in parallel blocks.
+    ([JENKINS-47201](https://issues.jenkins-ci.org/browse/JENKINS-47201))
+-   Improvement: Change the display name of the `checkout` step from
+    "General SCM" to "Check out from version control".
+-   Improvement: Add documentation for specific variables returned by
+    the `checkout` step based on the installed set of plugins.
+    ([JENKINS-26100](https://issues.jenkins-ci.org/browse/JENKINS-26100))
+
+### 2.6
+
+Release date: 2017-06-20
+
+-   [JENKINS-26100](https://issues.jenkins-ci.org/browse/JENKINS-26100) `checkout`
+    step now returns a `Map` of environment variables set by the SCM in
+    legacy Freestyle jobs, such as `GIT_COMMIT` and `SVN_REVISION`.
+
+### 2.5
+
+Release date: 2017-06-16
+
+-   No user-facing changes.
+
+### 2.4
+
+Release date: 2017-02-27
+
+-   No user-facing changes, only test infrastructure.
+
+### 2.3
+
+Release date: 2016-11-10
+
+-   No user-facing changes, only internal metadata.
+
+### 2.2
+
+Release date: 2016-07-05
+
+-   [JENKINS-35247](https://issues.jenkins-ci.org/browse/JENKINS-35247)
+    `git` and `svn` steps now moved to their respective SCM plugins.
+    This plugin now includes only the generic `checkout` step.
+
+### 2.1
+
+Release date: 2016-06-09
+
+-   [JENKINS-35247](https://issues.jenkins-ci.org/browse/JENKINS-35247)
+    Removed direct plugin dependencies on [Git
+    Plugin](https://plugins.jenkins.io/git) and
+    [Subversion
+    Plugin](https://plugins.jenkins.io/subversion),
+    in preparation for moving the `git` and `svn` steps to their natural
+    homes. (forward-ported from 1.14.2 / 1.4.3)
+-   Downgraded “overriding old revision state” warning.
+
+### 2.0
+
+Release date: 2016-04-05
+
+-   First release under per-plugin versioning scheme. See [1.x
+    changelog](https://github.com/jenkinsci/workflow-plugin/blob/82e7defa37c05c5f004f1ba01c93df61ea7868a5/CHANGES.md)
+    for earlier releases.

README.md

@@ -1,9 +1,15 @@
-# Introduction
+# Pipeline: SCM Step Plugin
+
+[![Jenkins Plugin](https://img.shields.io/jenkins/plugin/v/workflow-scm-step)](https://plugins.jenkins.io/workflow-scm-step)
+[![Changelog](https://img.shields.io/github/v/tag/jenkinsci/workflow-scm-step-plugin?label=changelog)](https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/CHANGELOG.md)
+[![Jenkins Plugin Installs](https://img.shields.io/jenkins/plugin/i/workflow-scm-step?color=blue)](https://plugins.jenkins.io/workflow-scm-step)
+
+## Introduction
 
 This plugin allows pipelines to use standard Jenkins SCM plugins to check out source code.
 The goals are the maximum possible compatibility with existing plugins, and great flexibility for script authors.
 
-# Features
+## Features
 
 A freestyle project has a single SCM configured in the UI that governs the one and only workspace for the build.
 A Pipeline can be configured similarly, but the SCM definition becomes a regular step in its script.
@@ -19,7 +25,7 @@ node {
 Jenkins will clone the repository into the workspace and continue with your script.
 (Subsequent builds will update rather than clone, if the same slave and workspace are available again.)
 
-## Multiple SCMs
+### Multiple SCMs
 
 While freestyle projects can use the Multiple SCMs plugin to check out more than one repository,
 or specify multiple locations in SCM plugins that support that (notably the Git plugin),
@@ -38,7 +44,7 @@ parallel repos.collectEntries {repo -> [/* thread label */repo, {
 }]}
 ```
 
-## Changelogs
+### Changelogs
 
 By default each build will show changes from the previous build in its changelog as usual, and you can see an overall changelog on the project index page.
 You may specify `changelog: false` to disable changelog generation if it is not of interest, or too large to compute efficiently.
@@ -47,7 +53,7 @@ Jenkins will automatically remember the SCMs run in the _last build_ of the proj
 This means that you can run multiple SCMs, even from a dynamic list, and get a reasonable changelog.
 (At least for those checkouts that remain constant from build to build, as identified by a key defined by the SCM plugin, typically based on something like the repository location and branch.)
 
-## Polling
+### Polling
 
 If you configure the _Poll SCM_ trigger in the Pipeline’s UI configuration screen, then by default Jenkins will also poll for changes according to the selected _Schedule_, and schedule new builds automatically if changes are detected.
 (Note that this configuration is not part of the Pipeline script, because it affects activities that Jenkins runs outside of the Pipeline.)
@@ -61,15 +67,15 @@ Polling is supported across multiple SCMs (changes in one or more will trigger a
 
 You may specify `poll: false` to disable polling for an SCM checkout.
 
-# Built-in integrations
+## Built-in integrations
 
 Currently there are special integrations in the Git (`git` step) and Subversion (`svn` step) plugins.
 See those plugins for details.
 
-# Generic SCM step
+## Generic SCM step
 
 The `checkout` step may be used to run any other SCM plugin, provided that it has been brought up to date as described below.
-(See the [compatibility list](https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md) for the list of currently SCMs.)
+(See the [compatibility list](https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md) for the list of currently supported SCMs.)
 It could also be used to run an SCM for which there is a special integration that lacks support for an exotic feature.
 The step takes an `scm` parameter which is a map containing at least a `$class` parameter giving the full or simple class name of the desired `SCM` implementation, and the standard `poll` and `changelog` parameters.
 
@@ -101,6 +107,10 @@ This would correspond roughly to a freestyle project whose `config.xml` includes
 
 with no `<hudson.triggers.SCMTrigger>` (polling).
 
-# Supporting Pipeline from an SCM plugin
+## Supporting Pipeline from an SCM plugin
+
+See the [compatibility guide](https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#scms).
+
+## Version History
 
-See the [compatibility guide](https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#scms).
+See [the changelog](CHANGELOG.md).

pom.xml

@@ -12,7 +12,7 @@
     <version>${revision}${changelist}</version>
     <packaging>hpi</packaging>
     <name>Pipeline: SCM Step</name>
-    <url>https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+SCM+Step+Plugin</url>
+    <url>https://github.com/jenkinsci/${project.artifactId}-plugin</url>
     <licenses>
         <license>
             <name>MIT License</name>