March 2016 - Infra - Ovirt List Archives

[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-422: ------------------------------------------------- Last update on needed steps: Current status: "Stage 1" (first snapshot repo without images) * a. oVirt nightlies are being published as usual * b. A snapshot was created manually using repoman command, as described in [1] * c ** missing ** * d. new release rpm for 4.0 was created manually [2] * e ** missing ** * f. new softlink was created for latest pre-alpha releases [3] "Stage 2" (final repo with images) * a. new jobs [4] building node + appliance created using the rpm from [3] Missing steps: "Stage 1" (first snapshot repo without images) * new jenkins job that will run the whole flow starting from 1b, work has started here [5] (@sandro, please correct if i'm wrong) * new step for checking repoclosure needs to be added as step 'c', code can be taken from [6]. * automate the step of building the release rpm pointing to a specific release dir. * create new release rpm that will always point to latest snapshot link [3] * add sanity for first repo using lago, similar to [7], just using the new release rpm to run on the new snapshot (step 1e) "Stage 2" (repo including images) * run the job(s) to build appliance, node & ovirt-live using the rpm from [2]. (job for ovirt-live might needs fixing to use release rpm) * push the new images to the new repo, using TBD job * run repoclosure to make sure images are install-able, similar to [6] * run lago sanity tests on whatever is possible (node/appliance/he) * update softlink [3] to point to new repo with images * make repo readonly * move bugs to ON_QA [8] * send email on release with links + changelog [1] https://ovirt-jira.atlassian.net/browse/OVIRT-422 [2] http://resources.ovirt.org/pub/ovirt-4.0_prealpha2/rpm/el7/noarch/ovirt-r... [3] http://resources.ovirt.org/pub/ovirt-4.0_prealpha-latest/ [4] [~fabiand(a)redhat.com] - can you share the links to the jobs? [5] https://gerrit.ovirt.org/#/c/54626/ [6] http://jenkins.ovirt.org/job/repos_master_check-closure_merged/ [7] http://jenkins.ovirt.org/job/ovirt_master_system-tests/ [8] as first step we'll use the logic of extracting bugs from the commits msg for a list of projects (do we need approval from each maintainer?) > Create jenkins job to compose ovirt 4.0 snaphost early builds > ------------------------------------------------------------- > > Key: OVIRT-422 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, repoman > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build. > * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on > resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/ > * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1] > * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1 > * We'll run repoclosure on it once the copy is finished > * run sanity (either manually or via Lago manual if possible) > * rhevh team run sanity on the node builds from nightly > * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link. > * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg. > * Send email to users/devel with info on release (list of bugs + link to release rpm). > [2] cat ovirt-4.0-snapshots.repoman (the conf file) > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

two otopi builds in a single jenkins job

by Yedidyah Bar David

Hi all, Yesterday I worked on some change to otopi [1]. Changeset 3 failed jenkins. Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old parent. Then I rebased locally and pushed again, changeset 5 [3]. In changeset 4, the version in master was 1.4.2-something. After the rebase, the version was 1.5.0-something. For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- . Any idea why? Some dirty environment? Also, I now tried to run it again. I do not have a "retrigger" link, so I tried using [4], input the changeset number, marked patchset 5, pressed 'Trigger Selected', and now I see on the side: Triggered Builds 54697,5 No jobs triggered for this event Best, [1] https://gerrit.ovirt.org/54697 [2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/57/ [3] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/58/ [4] http://jenkins.ovirt.org/gerrit_manual_trigger/ -- Didi

8 years, 1 month

3
3
0 / 0

[JIRA] (OVIRT-438) Build oVirt 3.6.4 RC1

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-438?page=com.atlassian.jira... ] sbonazzo updated OVIRT-438: --------------------------- Assignee: Rafael Martins (was: infra) Status: Accepted (was: New) > Build oVirt 3.6.4 RC1 > --------------------- > > Key: OVIRT-438 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-438 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: Rafael Martins > Assignee: Rafael Martins > Priority: High > Fix For: OVIRT-INFRA-FEB-2016 > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-438) Build oVirt 3.6.4 RC1

by Rafael Martins (oVirt JIRA)

Rafael Martins created OVIRT-438: ------------------------------------ Summary: Build oVirt 3.6.4 RC1 Key: OVIRT-438 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-438 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: Rafael Martins Assignee: infra Priority: High Fix For: OVIRT-INFRA-FEB-2016 -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-429) Test email

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-429?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-429: -------------------------------------------- Resolution: Won't Fix Status: Closed (was: New) test > Test email > ---------- > > Key: OVIRT-429 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-429 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: dcaro > Assignee: infra > Attachments: signature.asc > > > Awonder > -- > David Caro > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > IRC: dcaro|dcaroest@{freenode|oftc|redhat} > Web: www.redhat.com > RHT Global #: 82-62605 -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-427) Probem with Ovirt Url (Quick Start Guide)

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-427?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-427: ------------------------------------------------- [~sbendavi(a)redhat.com] is the issue still relevant after the wiki moved to the new location? were the docs fixed? > Probem with Ovirt Url (Quick Start Guide) > ----------------------------------------- > > Key: OVIRT-427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-427 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shlomo Ben David > Assignee: infra > > Hi, > After trying to install oVirt on my home machine, I've noticed that there > is a problem with the url - it's points to 'plain.resources.ovirt.org' > instead of 'resources.ovirt.org'. > '# yum -y install > http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm' > I tried to install this rpm locally and it successfully installed the repo > file, but after trying to install the ovirt-engine I've stacked (there is > no such package). > '# yum -y install ovirt-engine' > FYI > -- > Shlomi Ben-David | Software Engineer | Red Hat ISRAEL > Phone: +972-54-8008858 > IRC: sbendavi > OPEN SOURCE - 1 4 011 && 011 4 1 -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-428) Credentials request

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-428?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-428: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) access given. > Credentials request > ------------------- > > Key: OVIRT-428 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-428 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > Hi, > I need credentials for the Ovirt Jira. Can you please provide? > Thanks > Gil Shinar -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-430) New user request - Gal Ben Haim

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-430?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-430: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) added. > New user request - Gal Ben Haim > ------------------------------- > > Key: OVIRT-430 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-430 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gal Ben Haim > Assignee: infra > > Hello, > I'm a new employee on the RHEV CI team. > I would need a user for the Ovirt Jira bug tracking system. > Can you please create it for me? > Thanks, > Gal -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-427) Probem with Ovirt Url (Quick Start Guide)

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-427?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-427: -------------------------------------------- Description: Hi, After trying to install oVirt on my home machine, I've noticed that there is a problem with the url - it's points to 'plain.resources.ovirt.org' instead of 'resources.ovirt.org'. '# yum -y install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm' I tried to install this rpm locally and it successfully installed the repo file, but after trying to install the ovirt-engine I've stacked (there is no such package). '# yum -y install ovirt-engine' FYI -- Shlomi Ben-David | Software Engineer | Red Hat ISRAEL Phone: +972-54-8008858 IRC: sbendavi OPEN SOURCE - 1 4 011 && 011 4 1 was: Hi, After trying to install oVirt on my home machine, I've noticed that there is a problem with the url - it's points to 'plain.resources.ovirt.org' instead of 'resources.ovirt.org'. '# yum -y install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm' I tried to install this rpm locally and it successfully installed the repo file, but after trying to install the ovirt-engine I've stacked (there is no such package). '# yum -y install ovirt-engine' FYI -- Shlomi Ben-David | Software Engineer | Red Hat ISRAEL Phone: +972-54-8008858 IRC: sbendavi OPEN SOURCE - 1 4 011 && 011 4 1 > Probem with Ovirt Url (Quick Start Guide) > ----------------------------------------- > > Key: OVIRT-427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-427 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shlomo Ben David > Assignee: infra > > Hi, > After trying to install oVirt on my home machine, I've noticed that there > is a problem with the url - it's points to 'plain.resources.ovirt.org' > instead of 'resources.ovirt.org'. > '# yum -y install > http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm' > I tried to install this rpm locally and it successfully installed the repo > file, but after trying to install the ovirt-engine I've stacked (there is > no such package). > '# yum -y install ovirt-engine' > FYI > -- > Shlomi Ben-David | Software Engineer | Red Hat ISRAEL > Phone: +972-54-8008858 > IRC: sbendavi > OPEN SOURCE - 1 4 011 && 011 4 1 -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-422: -------------------------------------------- Status: Accepted (was: New) [~fabiand@redhat.com][~sbonazzola(a)redhat.com] I believe you made some progress for this flow, including adjusting the rhevh and appliance jobs plus adding links + release rpm. Can you add some info & links so we'll be able to plan the remaining items to finish the automation of the flow? > Create jenkins job to compose ovirt 4.0 snaphost early builds > ------------------------------------------------------------- > > Key: OVIRT-422 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, repoman > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build. > * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on > resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/ > * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1] > * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1 > * We'll run repoclosure on it once the copy is finished > * run sanity (either manually or via Lago manual if possible) > * rhevh team run sanity on the node builds from nightly > * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link. > * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg. > * Send email to users/devel with info on release (list of bugs + link to release rpm). > [2] cat ovirt-4.0-snapshots.repoman (the conf file) > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra March 2016