[JIRA] (JENKINS-40550) Remove "script" from Pipeline references in Jenkins UI
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-40550 Remove "script" from Pipeline references in Jenkins UI Change By: Patrick Wolf 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" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40550) Remove "script" from Pipeline references in Jenkins UI
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-40550 Remove "script" from Pipeline references in Jenkins UI Change By: Patrick Wolf 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" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40550) Remove "script" from Pipeline references in Jenkins UI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40550 Re: Remove "script" from Pipeline references in Jenkins UI 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 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40550) Remove "script" from Pipeline references in Jenkins UI
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-40550 Remove "script" from Pipeline references in Jenkins UI Issue Type: Epic Assignee: Unassigned Components: pipeline Created: 2016/Dec/19 5:42 PM Priority: Minor Reporter: Patrick Wolf 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" Add Comment
