[
https://issues.apache.org/jira/browse/BIGTOP-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195775#comment-14195775
]
Roman Shaposhnik commented on BIGTOP-1501:
------------------------------------------
[~gkesavan] and [~kaiyzen] thank you guys for feedback! I'm seriously looking
into Job DSL Plugin now!
[~jayunit100] the idea with Job DSL plugin is to do exactly what you're
suggesting: have close to 0 amount of state in Jenkins configuration itself.
Basically all state of Jenkins will be kept in Bigtop source code and would be
expected to be able to completely boostrap from a single seed Job reading the
DSL. At least that's the hope.
> come up with a way to use Jenkins plugins/Groovy console to create jobs
> -----------------------------------------------------------------------
>
> Key: BIGTOP-1501
> URL: https://issues.apache.org/jira/browse/BIGTOP-1501
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.8.0
> Reporter: Roman Shaposhnik
> Fix For: 0.9.0
>
>
> The idea here is simple: we're now migrating to the new style of build
> infrastructure that is 100% Docker centric. This will make our Jenkins jobs
> highly regular and subject to automatic creation based on a template.
> At this point, I don't know of an easy way to automate this and would
> appreciate if somebody can research it.
> The pipeline I imagine would be this: there will be a meta-job on Jenkins
> running and creating other jobs based on the state of a template in our
> source code repo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
