-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
Remove "script" from Pipeline references in Jenkins UI
-
To clarify the differences we are going to call the new syntax "Declarative Pipeline" and the existing full-imperative syntax "Scripted Pipeline".
Both are part of Pipeline and run on the same execution engine. The syntax is the only difference. Both can be used in a Jenkinsfile, both can be loaded from SCM.
It has been suggested that terms like "Generate Pipeline script" or "Load Pipeline script from SCM' were confusing because they imply that only "Scripted Pipeline" can be used. We need to remove "script" from these references:
"Generate Pipeline Script" -> "Generate Pipeline"
"Load Pipeline script from SCM" -> "Load Pipeline from SCM"
[JENKINS-40550] Remove "script" from Pipeline references in Jenkins UI
| Epic Child | New: WEBSITE-272 [ 177232 ] |
| Epic Child | New: WEBSITE-274 [ 177234 ] |
| Epic Child | New: WEBSITE-273 [ 177233 ] |
| Epic Child |
New:
|
| Epic Child | New: JENKINS-40557 [ 177244 ] |
| Epic Child |
New:
|
| Epic Child | New: JENKINS-40559 [ 177246 ] |
| Description |
Original:
We are getting close to releasing Declarative Pipeline syntax to extend Pipeline. This syntax has a predefined structure to simplify creating Pipelines. To clarify the differences we are going to call the new syntax "Declarative Pipeline" and the existing full-imperative syntax "Scripted Pipeline". Both are part of Pipeline and run on the same execution engine. The syntax is the only difference. Both can be used in a Jenkinsfile, both can be loaded from SCM. It has been suggested that terms like "Generate Pipeline script" or "Load Pipeline script from SCM' were confusing because they imply that only "Scripted Pipeline" can be used. We need to remove "script" from these references: "Generate Pipeline Script" -> "Generate Scripted Pipeline" "Load Pipeline script from SCM" -> "Load Pipeline from SCM" |
New:
We are getting close to releasing Declarative Pipeline syntax to extend Pipeline. This syntax has a predefined structure to simplify creating Pipelines. To clarify the differences we are going to call the new syntax "Declarative Pipeline" and the existing full-imperative syntax "Scripted Pipeline". Both are part of Pipeline and run on the same execution engine. The syntax is the only difference. Both can be used in a Jenkinsfile, both can be loaded from SCM. It has been suggested that terms like "Generate Pipeline script" or "Load Pipeline script from SCM' were confusing because they imply that only "Scripted Pipeline" can be used. We need to remove "script" from these references: "Generate Pipeline Script" -> "Generate Pipeline" "Load Pipeline script from SCM" -> "Load Pipeline from SCM" |
Code changed in jenkins
User: R. Tyler Croy
Path:
content/doc/book/pipeline/getting-started.adoc
content/doc/book/pipeline/jenkinsfile.adoc
content/doc/book/pipeline/shared-libraries.adoc
http://jenkins-ci.org/commit/jenkins.io/8adf7b8e0d6d208580b776fa27e4b8976ab882af
Log:
Correct or remove references to Pipeline Script where possible
There is still some outstanding work which needs to be done in JENKINS-40550 to
update web UI elements to reflect the appropriate "Scripted Pipeline" phrasing.
References WEBSITE-273