[JIRA] (OVIRT-1021) Trigger a job on a github repo change
eyal edri [Administrator] (oVirt JIRA)
jira at ovirt-jira.atlassian.net
Mon Jan 16 12:04:01 UTC 2017
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25728#comment-25728 ]
eyal edri [Administrator] commented on OVIRT-1021:
--------------------------------------------------
The support for GitHub projects in standard CI is tracked here https://ovirt-jira.atlassian.net/browse/OVIRT-970 and initial work is done now to add ovirt-web-ui as the first oVirt project to have build-artifacts triggered from GitHub.
> 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)
More information about the Infra
mailing list