What are seed jobs in Jenkins and how does it work ?
Can we create a new job from seed job without using github ?
Seed is a fully managed CI/CD pipeline for Serverless apps on AWS. Simply add your Git repository and IAM credentials and your entire team can git push to deploy updates to your Serverless app.
There's plugins that allow creating jobs from other jobs, like the excellent Job-DSL plugin. With that, you can create jobs where a groovy script creates a larger number of jobs for you. The Job-DSL plugin refers to those jobs as "seed jobs" (but they're regular freestyle or pipeline jobs).
The main difference between any job and a Pipeline Job is that the Pipeline Scripted job runs on the Jenkins controller, using a lightweight executor expected to use very few resources in order to translate the pipeline to atomic commands that execute or send to the agents.
To create a seed Job, a Job DSL Plugin must be installed on your Jenkins’ server plugin list, which then helps you define the job and incorporate it with the seed job automating the creation of additional jobs. In this article, you will know how to install the Job DSL plugin and create a seed job on the Jenkins pipeline for the DevOps project.
As shown in the above figure, different types of Jenkins Jobs are: (i) Freestyle Project: This is a regular and popular job in Jenkins which allows us to build our project, integrate our builds or source code management with Jenkins, poll the SCM, create triggers, and many more. (ii) Maven Project: Enables us to build our maven projects.
Our seedJob onboards a very simple Freestyle Job (poc-micro) from our microservice-pipelines repository. The benefit of microservice-pipelines is that we are now maintaining all of our pipeline configurations in source control. Using seed jobs allows us to onboard/re-onboard services quickly and easily (history is maintained for re-onboarded jobs).
From what I have gathered, the best way to go about this is to have Chef configure a seed job in Jenkins initial setup and configuration. The seed job should specify, among other things, the git repository from which to find and use a Jenkinsfile for a given job.
That depends on context. Jenkins itself does not provide "seed jobs".
There's plugins that allow creating jobs from other jobs, like the excellent Job-DSL plugin. With that, you can create jobs where a groovy script creates a larger number of jobs for you.
The Job-DSL plugin refers to those jobs as "seed jobs" (but they're regular freestyle jobs). The Job-DSL plugin does not require a github connection.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With