{"id":167,"date":"2017-04-12T22:29:28","date_gmt":"2017-04-12T14:29:28","guid":{"rendered":"http:\/\/www.jsjs.org\/?p=167"},"modified":"2017-04-12T22:29:28","modified_gmt":"2017-04-12T14:29:28","slug":"pipeline-as-code-with-jenkins","status":"publish","type":"post","link":"https:\/\/blog.jsjs.org\/?p=167","title":{"rendered":"Pipeline as Code with Jenkins"},"content":{"rendered":"
\n

The default interaction model with Jenkins, historically, has been very web UI driven, requiring users to manually create jobs, then manually fill in the details through a web browser. This requires additional effort to create and manage jobs to test and build multiple projects, it also keeps the configuration of a job to build\/test\/deploy separate from the actual code being built\/tested\/deployed. This prevents users from applying their existing CI\/CD best practices to the job configurations themselves.<\/p>\n<\/div>\n

\n

Pipeline<\/h2>\n
\n
\n

With the introduction of the Pipeline plugin<\/a>, users now can implement a project\u2019s entire build\/test\/deploy pipeline in a Jenkinsfile<\/code> and store that alongside their code, treating their pipeline as another piece of code checked into source control.<\/p>\n<\/div>\n

\n

The Pipeline plugin was inspired by the Build Flow plugin<\/a> but aims to improve upon some concepts explored by Build Flow with features like:<\/p>\n<\/div>\n

\n