This topic describes the prerequisites needed for creating a Pipeline.
To create a Pipeline:
-
Ensure that you have CloudBees CI installed. For instructions on installing CloudBees CI, see Onboarding for CloudBees CI on modern cloud platforms
-
Install the Pipeline plugin to automate your continuous delivery pipeline and perform other complex tasks in Jenkins. For more information, refer to the Pipeline plugin.
-
Install the CloudBees Pipeline: Groovy Checkpoint plugin.
For more information on installing plugins, please refer to Best practices: Install plugins on production instances.
Recommended plugins
CloudBees recommends these plugins to be able to access more functionality for Pipeline creation.
Recommended plugins for Continuous Delivery
-
The CloudBees Pipeline Explorer plugin provides an improved log-viewing experience to troubleshoot Pipelines. It includes improved performance vs the classic log view, embedded search capabilities, and customizable preferences to personalize your log-viewing experience.
Recommended plugins for Source Code Management
-
Use the Git plugin to retrieve source code and build results, so developers can quickly access test results and check their code.
-
The GitHub Branch Source plugin creates a new project based on the repository structure from one or more GitHub users or organizations. For more information, refer to Creating projects based on GitHub repository structure.
-
The CloudBees SCM Reporting plugin allows you to access enhanced build information from GitHub and Bitbucket.
-
The Bitbucket Branch Source plugin allows you to use Bitbucket Cloud and Bitbucket Server as sources for multibranch projects.
Recommended plugins for Reporting
-
Email Extension plugin sends build status messages to relevant stakeholders.
-
CloudBees Slack Integration plugin sends Slack notification containing build status messages to relevant stakeholders.
Recommended plugins for consistency
-
CloudBees Pipeline: Templates Plugin ensures that Pipeline builds conform to organizational standards by giving the Jenkins administrator the opportunity to provide users a simplified and directed experience for configuring jobs, in "domain specific" terms that make sense to their organization.