Barak Korren created OVIRT-1548:
-----------------------------------
Summary: Better STD-CI for GitHub
Key: OVIRT-1548
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Priority: High
We currently have some support for crating STD-CI jobs for projects running on
GitHub. There are however, several issues with it:
* The job templates you use for GitHub are different then the ones you use for
Gerrit:
** Job names need to contain '\-github-'
** In Gerrit you need a separate 'project' entry for the 'build-artifacts'
jobs, in GitHub you need a separate one for 'check-patch'.
** SCM checkout details are specified in the 'project' entry as opposed to a
separate SCM file (We might want to adopt this for Gerrit).
* The 'check-patch' jobs do not have full STC-CI. They don't run the post-build
steps.
* The triggering scheme is strange:
** All jobs trigger when certain messages are posted in the PR comments.
** Nothing is triggered automatically (As opposed to Gerrit where CI runs as
soon as a patchset is submitted)
** Nothing triggers when a PR is merged (As opposed to with Gerrit where
'check-merged' and 'build-artifacts' are triggered on merge).
* The white-listing scheme is different:
** The 'jenkins-whiltelist' file does not effect theses jobs at all.
** GitHub project/organisation membership determines white-listing
** white-listing is determined by who added the comment to run CI, not who
authored the patch.
Some of these issues and differences had already been tracked in other tickets.
This ticket is for concentrating all related work. Other related tickets will
be linked to it as blockers.
--
This message was sent by Atlassian JIRA
(v1000.1131.0#100055)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
