Now this is more interesting. Using the .jenkins.yml file from the repository to inform the job generator what jobs to create is similar to travis.
Of course, the details are in the implementation in the next post. I'm curious. When a repo needs testing, does it always go through the job generator before going through the generated jobs every single time? Does the job generator clean up any jobs that are no longer used when the yaml file changes? Are the jobs generated unique per repository or shared? Can you create nice views, folders, pipeline views as well? -- 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/39f08c0d-e426-43f1-9966-59291abd95a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
