[ https://ovirt-jira.atlassian.net/browse/OVIRT-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39835#comment-39835 ] Eyal Edri commented on OVIRT-1678: ---------------------------------- [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] can it be done by [~accountid:5c977456c430371a3c67dbf6] as part of learning STD-CI?

Move gerrit-admin project to be standard CI -------------------------------------------

Key: OVIRT-1678 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git, Gerrit Hooks Reporter: Eyal Edri Assignee: infra

Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks. This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way. I would start with adding a 'check-patch.sh' script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks. It's also a great way to learn more about how to create a stanard CI project. More info on it can be found on the infra docs page: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards...

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)