[ https://ovirt-jira.atlassian.net/browse/OVIRT-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25729#comment-25729 ] eyal edri [Administrator] commented on OVIRT-1021: -------------------------------------------------- Also, As stated, we don't support projects in oVirt CI that are not part of the standard CI ( i.e use the automation folder, etc.. ). The reason for that is that all the infrastructure is based on that and running a job outside it will mean the jenkins slave will need to be maintained and updated just for that job, for e.g, you'll need to: - have the relevant pkg installed on the slave and make sure to clean it when you're done ( something mock does for you in std ci) - have the right OS Installed ( mock is agnostic and can run on any fedora/centos version we support no matter that the VM os is ) We worked hard to get to this point where we have standardization on all the projects, so I don't see any option right now to support any project that doesn't use the existing framework. If there are limitations or missing features in the current implementation then we should discuss them and work on closing that gap.

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)