The pipeline as code page teaches users how to automate the creation, execution, and deletion of pipeline jobs based on the creation and deletion of jobs.
You're welcome to define a pipeline job that include the pipeline definition in the job or you can define a pipeline job that reads the job definition from SCM. Those two techniques won't automatically create and destroy jobs based on branches, but they are allowed and supported by Jenkins. On Mon, Oct 28, 2019 at 10:21 PM Tim Black <timbla...@gmail.com> wrote: > Just double checking this, at the below link it says the only way to use > pipeline as code is to use the multi Branch pipeline configuration. Is this > really true? > > https://jenkins.io/doc/book/pipeline-as-code/ > > I thought perhaps there was a way to configure a job that doesn't monitor > for branches and create corresponding jobs, but simply pulls a Jenkins file > from SCM. > > Perhaps this behavior I describe is just a subset of what multi-branch > pipeline can do? So to achieve my simple behavior I just use multi-branch > Pipeline and configure it to not monitor for new branches? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/c45794e2-bb73-4b06-b450-a6cfef76b15f%40googlegroups.com > . > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHyEziNtryZMVBj8YuhSZt-dgFO_VLU3CaO-jW3PWtdtQ%40mail.gmail.com.
