You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ See those plugins for details.
75
75
## Generic SCM step
76
76
77
77
The `checkout` step may be used to run any other SCM plugin, provided that it has been brought up to date as described below.
78
-
(See the [compatibility list](https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md) for the list of currently SCMs.)
78
+
(See the [compatibility list](https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md) for the list of currently supported SCMs.)
79
79
It could also be used to run an SCM for which there is a special integration that lacks support for an exotic feature.
80
80
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.
81
81
@@ -109,7 +109,7 @@ with no `<hudson.triggers.SCMTrigger>` (polling).
109
109
110
110
## Supporting Pipeline from an SCM plugin
111
111
112
-
See the [compatibility guide](https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#scms).
112
+
See the [compatibility guide](https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#scms).
0 commit comments