Recommendations for Maintaining a Jenkins Pipeline SCM Snippet
Complex Pipelines can be difficult to write and maintain within the Jenkins classic UI’s Script text area on the Jenkins Pipeline configuration page.
To make this easier, your Pipeline’s Jenkinsfile can be written in a text editor or integrated development environment (IDE) and committed to source control. Jenkins can then check out your Jenkinsfile from source control as part of your Pipeline project’s build process and then proceed to execute your Pipeline.
For more information about Jenkins SCM Snippets please see https://jenkins.io/doc/book/pipeline/getting-started/#defining-a-pipeline-in-scm
To use the VectorCAST Jenkins Pipeline SCM Snippet the user can click on the link at the bottom of the SCM Checkout Snippet highlighted in the picture below (Snippet Generator).
A new tab will open allowing you to select your sample step for Git or Checkout. Provide the necessary information and click "Generate Pipeline Script". From there, copy the generated snippet, close the tab and paste the copied snippet into the SCM Checkout Snippet section of the VectorCAST Pipeline Job create window.