You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2014/12/15 07:04:13 UTC

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

     [ https://issues.apache.org/jira/browse/BIGTOP-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-1501:
-------------------------------------
    Attachment: 0001-BIGTOP-1501.-come-up-with-a-way-to-use-Jenkins-plugi.patch

Attaching a very rough first cut at what I have in mind. Please, please comment.

> 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
>
>         Attachments: 0001-BIGTOP-1501.-come-up-with-a-way-to-use-Jenkins-plugi.patch
>
>
> 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)