- Infra - oVirt List Archives

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1549: ------------------------------------- Without going into too much detail yet, the instruction you posted seem to refer to Gerrit projects, while the project you linked to is on GitHub? Is that project actually maintained in Gerrit? If so, where? Some more questions: * Does the project build RPMs? * Are those RPMs officially released somewhere? * Do we really want to track the project at the source level? If so, will the maintainers be willing to add an 'automation' directory and the related scripts? > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 298 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_245_434408739.1500696006298 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 298 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #298 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_245_434408739.1500696006298--

1 2

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

danken created OVIRT-1549: ----------------------------- Summary: run OST as a third-party tester for OpenStack's ovsdbapp Key: OVIRT-1549 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1548: ----------------------------------- Assignee: Barak Korren (was: infra) > 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: Barak Korren > Priority: High > Labels: github, standard-ci > > 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)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

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)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1548: -------------------------------- Epic Link: OVIRT-400 > 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 > Labels: github, standard-ci > > 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)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 22 Jul '17

22 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1547: ------------------------------------- There is no bot here. This seems to be the logic on the GitHub pull-request trigger plugin when if is configured to filter by project/organisation membership. I suspect the amount of alerts matches the amount of jobs we have triggering on pull request events exactly. We probably need a staging environment for further testing and coming up with solutions, so adding OVIRT-1533 as a blocker > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 22 Jul '17

22 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1547: -------------------------------- Issue Type: Bug (was: Task) > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 22 Jul '17

22 Jul '17

eyal edri created OVIRT-1547: -------------------------------- Summary: limit the amount of warnings the whitelist bots sends to GitHub Key: OVIRT-1547 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 22 Jul '17

22 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1547: ----------------------------- Epic Link: OVIRT-400 > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0