Jenkins is a great CI/CD tool. But, sometimes it is hard to use, but the Jenkins Plugin for Pipeline helps you a lot.
Are you using Jenkins CI to automate your build and release process? Are you using a workflow (continuous integration) tool like Maven, Gradle, or Ant? Are you celebrating every time someone checks in code because this means less work for you? Jenkins Pipeline could be the next best step for your deployment pipeline.
The Pipeline plugin is essential for teams or organizations that are planning to automate and deploy new versions of applications. Pipeline provides a way to organize complex workflows into stages, and then tie these steps together to build out complex deployment workflows.
Jenkins Plugin For Pipeline
This plugin and its dependencies form a suite of plugins that lets you orchestrate automation, simple or complex. See the Jenkins Pipeline documentation for more details.
Documentation on the Jenkins site:
How do I start with Pipeline?
Pipeline Syntax Reference
Pipeline Steps Reference
Extending Pipeline with SharedLibraries
Other information about Pipeline is available in GitHub. Quick links:
Developing plugins for Pipeline
Pipeline CPS Engine
Formerly known as the Workflow plugin. Originally inspired by the discontinued Build Flow Plugin.
Plugins that implement Pipeline steps or integrate with Pipeline-related APIs should not depend on workflow-aggregator because it includes many unncessary dependencies. Instead, they should depend only on the plugins that provide the APIs necessary for the integration. For the common case of implementing a Pipeline step, plugins typically only need to depend on workflow-step-api. In order to test Pipeline-related functionality, plugins need test-scope dependencies on workflow-job and workflow-cps. Additional test-scope dependencies on plugins like workflow-durable-task-step or workflow-basic-steps may be needed for more complex tests.
See GitHub Releases. For older versions, see historical changelog.