[JIRA] (OVIRT-1021) Trigger a job on a github repo change

[Barak Korren (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25711#comment-25711 ] 

Barak Korren commented on OVIRT-1021:
-------------------------------------

{quote}
I'd like to run a job on a github repo, without the need to add he complete automation folder.

But maybe it is enough if I can come up with a freeform job when writing it in JJB YAML.
{quote}

This would just mean you will be maintaining the code for your job in the '{{jenkins}}' repo instead of in your own repo where it belongs (Try asking the Travis devs to store your '{{.travis}}' file in one of their repos...).

This would also mean that you are not going to enjoy any of the effors made over the years to improve the oVirt CI infra, in essence you are going to have to re-learn all the lessons already learned.

And come on, its not like its a massive task to create an '{{automation}}' directory, its just a directory with simple scripts in it, and requirement files if needed. I think the learning curve to making it is far shallower then learning the whole Jenkins Job Builder syntax and how all the different system components interlock together. Being simple scripts, you get the benefit of being able to also run them locally to test without needing the whole CI infrastructure to do it.

> Trigger a job on a github repo change
> -------------------------------------
>
>                 Key: OVIRT-1021
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1021
>             Project: oVirt - virtualization made easy
>          Issue Type: Bug
>            Reporter: Fabian Deutsch
>            Assignee: infra
>
> Hey,
> we are pushing some changes to this github repository:
> https://github.com/kubevirt/demo
> The test autpmation requires nesting, thus it would be nice if this repo could be run on jenkins.
> Could our jenkins instance get a plugin to be able to hook it up to github i.e.
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+plugin
> The other thing would be how to store the job specification in the repo.
> Here it would be nice if we could dump a travis-ci-like file into the repo and let the job inerprete this.



--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)