- Infra - oVirt List Archives

Enhancing std-ci for deployment (std-cd)
by Barak Korren 07 Jun '16

07 Jun '16

Hi all, I'm contemplating the best way to enable including deployment logic in standard-CI scripts. Case to the point - embedding the deployment logic of our infra-puppet repo. One thing to note about this, is that deployment in this scenario can happen either post-merge (Like it does today) or pre-merge (Create a per-patch puppet env to enable easy testing) I can think of a few ways to go about this: 1. Copy the full generated puppet configuration into 'exported-artifacts' and add logic to the YAML to copy it to the foreman server. The main shortcoming of this is that we will have to maintain quite a bit of custom logic in the YAML. This beats the purpose of embedding the logic in the source repo in the 1st place. 2. Mount the '/etc/puppet' directory into the chrrot This will require having the foreman be a Jenkins slave and some custom YAML to ensure the jobs run on it (not a big deal IMO) The shortcoming is that running tests locally with mock_runner would be cumbersome (It will touch your local /etc/puppet directory and probably fail). Another issue is that we will have to find a way to figure out Gerrit patch information from inside mock. Possibly we could use the commit message or git hash for that. 3. Invent some kind of a new deploy_*.sh script This makes it possible to run the checking code locally without the deployment code. The YAML changes for this could be quite generic and shared with other projects. We could possibly also invent a 'deploy_*.target' to specify where to run the deploy script (E.g. a Jenkins label). We could even consider not running the script inside mock, though I think mock's benefits outweigh the limits it imposes on accessing the outside system (which can be mostly bypassed anyway with bind mounts). So, WDYT? -- Barak Korren bkorren(a)redhat.com RHEV-CI Team

2 3

[Vdsm] infra support for the new stable branch ovirt-4.0
by Francesco Romani 07 Jun '16

07 Jun '16

Hi Infra, (Dan, please ACK/NACK the following) I'm not sure this is already been worked on, or if it was already configured automatically, sending just in case to be sure. Me and Yaniv (CC'd) agreed to continue our maintainer duties and take care of the ovirt-4.0 Vdsm stable branch which was recently created. I'd like to ask if we have the gerrit permissions and CI jobs ready for the new branch. DISCLAIMER: I haven't yet tried to submit (yet alone merge) a patch to the ovirt-4.0 branch, we are still preparing the first backports :) Thanks, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

5 6

One patch - two failures
by Yevgeny Zaspitsky 07 Jun '16

07 Jun '16

Below are the details of one my patches that failed in CI. How surprising the fact that it failed with two different reasons and both aren't patch related! ---------- Forwarded message ---------- From: "Jenkins CI" <gerrit2(a)gerrit.ovirt.org> Date: Jun 5, 2016 11:37 PM Subject: Change in ovirt-engine[master]: core: update vdsm-jsonrpc-java to verion 1.2.3 To: "Moti Asayag" <masayag(a)redhat.com>, "Yevgeny Zaspitsky" < yzaspits(a)redhat.com> Cc: Jenkins CI has posted comments on this change. Change subject: core: update vdsm-jsonrpc-java to verion 1.2.3 ...................................................................... Patch Set 2: Build Failed http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/53… : FAILURE http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… : FAILURE http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64/5… : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… : SUCCESS -- To view, visit https://gerrit.ovirt.org/58584 To unsubscribe, visit https://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Iae15520c831c0b8de36169f0287057684033d376 Gerrit-PatchSet: 2 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Yevgeny Zaspitsky <yzaspits(a)redhat.com> Gerrit-Reviewer: Alona Kaplan <alkaplan(a)redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Moti Asayag <masayag(a)redhat.com> Gerrit-Reviewer: Piotr Kliczewski <piotr.kliczewski(a)gmail.com> Gerrit-Reviewer: Yevgeny Zaspitsky <yzaspits(a)redhat.com> Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> Gerrit-HasComments: No

5 6

Old Jenkins findbugs error ignored
by Tal Nisan 07 Jun '16

07 Jun '16

Check out this patch: https://gerrit.ovirt.org/#/c/58652/ Old Jenkins failed on Findbugs (seems like an env problem, not a findbugs analysis failure for that matter). Patch was marked as failed CI yet as soon as the new Jenkins finished its run it overwritten the failed CI of the old Jenkins and marked as CI passed

3 4

Jenkins build is back to stable : ovirt_master_publish-rpms_nightly #74
by jenkins＠jenkins.phx.ovirt.org 06 Jun '16

06 Jun '16

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/74/>

1 0

Jenkins build is back to stable : ovirt_4.0_publish-rpms_nightly #20
by jenkins＠jenkins.phx.ovirt.org 06 Jun '16

06 Jun '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_publish-rpms_nightly/20/>

1 0

Adding a new flag to a specific gerrit project?
by Juan Hernández 06 Jun '16

06 Jun '16

Hello, As part of the effort to improve the documentation of the REST API the documentation team will help us review the patches for the specification. I was wondering if it is possible to add a new flag, like the CR, CI, and V that we currently have. Would be nice to have a "Documentation" flag (or similar) so that the documentation team can +1 that flag. Is this possible? Can this flag be added to the ovirt-engine-api-model project? Can we define a group of users that have permissions to set this flag? Thanks in advance, Juan Hernández -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

4 10

[JIRA] (OVIRT-545) Re: Please remove ovirt-node-ng-image* from several repositories
by eyal edri [Administrator] (oVirt JIRA) 06 Jun '16

06 Jun '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-545?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-545: -------------------------------------------- Resolution: Fixed Status: Done (was: Blocked) > Re: Please remove ovirt-node-ng-image* from several repositories > ---------------------------------------------------------------- > > Key: OVIRT-545 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-545 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > > Creating a ticket for it. > I think all node members have access to the resources server also if > needed. (rbarry has). > On Fri, May 13, 2016 at 1:44 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote: > > Hey, > > > > could someone please remove all builds of these two packages: > > > > ovirt-node-ng-image > > ovirt-node-ng-image-update > > > > from the > > ovirt-3.6* > > ovirt-4.0* > > master* > > > > repositories? > > > > This is needed, because the versioning was changed. > > > > Thanks > > fabian > > > > -- > > Fabian Deutsch <fdeutsch(a)redhat.com> > > RHEV Hypervisor > > Red Hat > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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) -- This message was sent by Atlassian JIRA (v1000.25.1#100000)

1 0

[JIRA] (OVIRT-545) Re: Please remove ovirt-node-ng-image* from several repositories
by Fabian Deutsch (oVirt JIRA) 06 Jun '16

06 Jun '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-545?page=com.atlassian.jira.p… ] Fabian Deutsch commented on OVIRT-545: -------------------------------------- I learned that the repos are automatically cleaned based on the age of the rpms, not based on the version. That means that by now the old rpms are already removed and this ticket can be closed. > Re: Please remove ovirt-node-ng-image* from several repositories > ---------------------------------------------------------------- > > Key: OVIRT-545 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-545 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > > Creating a ticket for it. > I think all node members have access to the resources server also if > needed. (rbarry has). > On Fri, May 13, 2016 at 1:44 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote: > > Hey, > > > > could someone please remove all builds of these two packages: > > > > ovirt-node-ng-image > > ovirt-node-ng-image-update > > > > from the > > ovirt-3.6* > > ovirt-4.0* > > master* > > > > repositories? > > > > This is needed, because the versioning was changed. > > > > Thanks > > fabian > > > > -- > > Fabian Deutsch <fdeutsch(a)redhat.com> > > RHEV Hypervisor > > Red Hat > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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) -- This message was sent by Atlassian JIRA (v1000.25.1#100000)

1 0

[JIRA] (OVIRT-553) Update all jenkins jobs currently building master to build from 4.0 branch too if available
by eyal edri [Administrator] (oVirt JIRA) 06 Jun '16

06 Jun '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-553?page=com.atlassian.jira.p… ] eyal edri [Administrator] closed OVIRT-553. ------------------------------------------- Resolution: Fixed all jobs were added/cloned to 4.0 AFAIK. please update if we missed anything. > Update all jenkins jobs currently building master to build from 4.0 branch too if available > ------------------------------------------------------------------------------------------- > > Key: OVIRT-553 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-553 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > > On May 25th we'll branch 4.0 from master. > We'll need all jenkins jobs running on master to work on 4.0 as well. -- This message was sent by Atlassian JIRA (v1000.25.1#100000)

1 0