[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=25610#comment-25610 ] 

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

[~fdeutsch] The problem with freeform jobs is that they get unmaintained fast. But we do accept patches to the 'jenkins' repo, so you can make any job you like as long as you write it in JJB YAML.

I don't think Standard-CI and Travis are fully interchangable, for example, Travis lets you ask for a Docker image to run your tests on, in Standard-CI you specify environment in terms of OS, repos and packages you want. Travis also gives you pre-baked steps for interacting with various systems, in standard CI we just let you run a script which can be limiting or liberating depending on how you look at it (We do support interacting with certain systems on your behalf, depending on the artifacts you leave behind).

Given the simplicity of Standard-CI, I think it would be possible to write a .travis.yaml file that implements it, but probably not the other way around. Then again, if you already have your CI defined in "Standard-CI" terms, you might as well let the oVirt Jenkins run it...

But before we go any further I would like to hear a more detailed description of what you are looking to do, to better understand if it fits into the standard CI framework, or if its more of an OST type of thing.

> 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.692.0#100025)