[jira] [Comment Edited] (BIGTOP-1501) come up with a way to use Jenkins plugins/Groovy console to create jobs

["jay vyas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189292#comment-14189292 ] 

jay vyas edited comment on BIGTOP-1501 at 10/29/14 11:39 PM:
-------------------------------------------------------------

the job dsl thing seems cool .  but... my feelings are , with exception of things like release management and reporting --- in general, with *immutable infra* practices encoueraged by things like vagrant and docker,  much of what *build servers* used to be required for ---  is now provided in the local dev infra anyways.

so id suggest we move as much as possible out of the jenkins servers... i could be missing context here though :)



was (Author: jayunit100):
the job dsl thing seems cool .  but... my feelings are , with exception of things like release management and reporting --- in general, with *immutable infra* practices encoueraged by things like vagrant and docker,  much of what *build servers* used to be required for ---  is now provided in the local dev infra anyways.



> 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)