You can, of course, configure a pipeline and use any groovy file that you check out from SCM, Jenkinsfile is the general name of that file, and in some cases default, but see here n.5: https://www.jenkins.io/doc/book/pipeline/getting-started/#defining-a-pipeline-in-scm
Anatoly. On Monday, June 1, 2020 at 6:37:46 PM UTC+3, Al Silver wrote: > > I've used Jenkins a little but not in the traditional method of CI/CD. I'm > using Jenkins as a Web UI to run individual python scripts for networking > devices... Users would log into Jenkins and then select any one of numerous > Freestyle projects (with parameters) to run (there could be 100 or > more...). The job executes a shell which runs a pytest script that logs > into (via ssh) multiple networking devices and performs some actions... > pretty straightforward and it works ok but has some limitations. With that > said, I think I'll have more flexibility and power building and maintaining > these jobs as pipelines and treating them as code. My question is I guess > I would need to convert my pipelines into Jenkinsfiles? However, most of > the docs I read show a single Jenkinsfile (named "Jenkinsfile") I would > need one for each job (a 100 or so). I must be missing something here or > not understanding. Can someone point in the right direction for what I'm > trying to accomplish? > > Thx > Al > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/efa19331-a38f-4660-bafa-528abf24b158%40googlegroups.com.
