Jenkins provides two ways to create pipelines: Scripted Pipeline and Declarative Pipeline.

Scripted Pipeline is a more flexible and powerful way to define pipelines using Groovy scripting. It allows you to write custom code to define your pipeline's stages, steps, and logic. You have complete control over your pipeline, which can make it easier to implement complex workflows. However, it can also be more difficult to read and maintain than Declarative Pipeline.

Declarative Pipeline is a simpler way to define pipelines using a structured syntax. It uses a predefined set of keywords to define the pipeline's stages and steps, which makes it easier to read and maintain. It also provides built-in syntax validation and can generate visualizations of your pipeline. However, it may not be as flexible as Scripted Pipeline in some cases.

Both types of pipelines have their pros and cons, and the choice depends on your specific requirements and preferences. If you need more control and flexibility, then Scripted Pipeline may be the way to go. If you prefer a simpler and more structured approach, then Declarative Pipeline may be a better fit.