any update?

Hi Paulo, anything else needed from us?
Did you got a chance to post patches to gerrit.ovirt.org for adding Kiimchi project to standard CI?

Hi ,
Regarding the first part of your 1'st question, your patch needs to be sent to the 'jenkins' project on gerrit.ovirt.org (on the master branch): git://gerrit.ovirt.org/jenkins.git. , does he need special permissions for that? Also I'm not sure about the second part of the question.
Regarding your 2'nd question, all you need is to add a key named 'trigger-times' in the project yaml, and put the desired value.
For example:

• project:
  name: kimchi_project
  project: kimchi
  stage: build-artifacts
  trigger-times: 'H H/6 * * *'
  ...

Regarding question 3, afaik we only support CentOS and Fedora, can you confirm that?

can you help Paulo on the basics on how to submit a patch to gerrit.ovirt.org to the jenkins repo?

Hi . Nice documentation, but I still have some questions:

1- I created the project yaml and the scm yaml files in my local repository. How can I submit them to review? I planning to configure only one of our 4 projects to test in a first moment and, in addition, using a specific branch in my fork in github that will include the necessary files to CI Standard. If this first test works well, is it possible to submit updates (point to projects github repository) and improvements in project's files?
2- One of the fields for the project yaml file is the trigger, that can be on-change or timed. In case of timed (that is what I want to use) how can I set the periodicity to run the job?
3 - Reading the documentation, I could see only references to build artifacts to CentOS (EL) and Fedora. We provide artifacts to Ubuntu (Debian) and OpenSUSE, also. Is it possible to build for these distros?

hey, just one update regarding standard CI , we are in progress of adding documentation on how to add yaml code in here:
https://gerrit.ovirt.org/#/c/61376/5

so you can use it for adding your project

Hi

I read the standard CI and have an idea of what is necessary to add in our code to do this. I'm only finishing some other tasks and then will focus in the implementation of all CI stuff from our side.

Hey,
Did you got a chance to read on the standard CI ? do you need help in adding the 1st job?

I think we can support also GitHub repos, same way as Lago is running CI on
jenkins.ovirt.org.
for e.g:
http://jenkins.ovirt.org/job/lago_master_build-artifacts-el7-x86_64/,

But if you're considering moving to Gerrit it will be much easier and
you'll be able to enjoy more advantages of our CI system, such as gerrit
hooks.

e.

On Tue, Jun 28, 2016 at 7:23 PM, Barak Korren (oVirt JIRA) <

–
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)

I guess that if you want to remain on GitHub, we could make Gerrit repositories that will only contain the scripts for building the images, or even just simple wrapper scripts that will clone code from GitHub and use it...

You can build anything with standard CI.
One thing to note is that just building something with STD CI already makes it available over HTTP from Jenkins.

The uploading to resource.ovirt.org and repo building is not strictly part if the STD CI per-se its is a deployment stage that typically follows it.
We currently build RPMs in oVirt and have a tool called 'repoman' that knows how to collect them into yum repos. This means that supporting 'yum/dnf' repos is very easy for us. I guess we could also support other kinds of repos but that will take some work because we will need to come up with some tooling for that.

Thanks guys by your support. I'm going to read the STD CI and provide the necessary changes in our repository to automate our artifacts building process.

Our GitHub repositories are [1], [2] and [3] and, until now, the decision to use Gerrit in our process is out of scope (personally I like the idea and will rise the question to our Maintainers and community to see what they think about).

One curiosity. If we follow the STD CI, is it possible to build and make available package repositories (we support yum/dnf, apt and zypper) to be used by our users in addition to the images repositories?

[1] https://github.com/kimchi-project/wok.git
[2] https://github.com/kimchi-project/gingerbase.git
[3] https://github.com/kimchi-project/kimchi.git