You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Giridharan Kesavan (JIRA)" <ji...@apache.org> on 2014/10/29 23:28:35 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14189145#comment-14189145 ]
Giridharan Kesavan commented on BIGTOP-1501:
--------------------------------------------
[~rvs] jenkins has this yaml plugin , which could be used for configuring jobs.
https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin
> 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)