- Infra - oVirt List Archives

[JIRA] (OVIRT-1455) Deep dive about STD-CI
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1455?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1455: -------------------------------- Epic Link: OVIRT-400 > Deep dive about STD-CI > ---------------------- > > Key: OVIRT-1455 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1455 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Not enough people understand standard-CI and mock-runner. > Lets make a deep-dive to teach people. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1455) Deep dive about STD-CI
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1455: ----------------------------------- Summary: Deep dive about STD-CI Key: OVIRT-1455 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1455 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Not enough people understand standard-CI and mock-runner. Lets make a deep-dive to teach people. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1454) Document and educate team about change-queue
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1454?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1454: -------------------------------- Epic Link: OVIRT-400 > Document and educate team about change-queue > -------------------------------------------- > > Key: OVIRT-1454 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1454 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > As we progress towards making the change-queue fully operational, we need to write some documentation and traing the team about using and debugging it. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1454) Document and educate team about change-queue
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1454: ----------------------------------- Summary: Document and educate team about change-queue Key: OVIRT-1454 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1454 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra As we progress towards making the change-queue fully operational, we need to write some documentation and traing the team about using and debugging it. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1453) Make timed build-artifacts jobs deploy directly to 'tested'
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1453?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1453: ----------------------------------- Assignee: Barak Korren (was: infra) > Make timed build-artifacts jobs deploy directly to 'tested' > ----------------------------------------------------------- > > Key: OVIRT-1453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1453 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue, deploy-to-experimental, ovirt-engine-appliance, ovirt-node-ng > > The time build-artifacts jobs currently invoke the old 'deploy-to-experimental' job to deploy their packages into the experimental flow. > The new 'deploy-to-experimental' job cannot deploy the packages for the timed build-artifacts jobs because it can only handle merged patches. This is the reason why we kept the old build-artifacts jobs around. > Since the artifacts from the timed jobs get deployed to experimental they are also moved to 'tested' after OST succeeds and to the nightly repos. > As we prepare to replace the experimental flow with the chage-queue, we need an alternative solution for getting the artifacts from the timed jobs into 'tested'. > The experimental test jobs do not currently test the artifacts built by the timed build jobs, namely node and appliance. > The proposed solution is therefore to just make the timed build jobs deploy the built artifacs directly to the 'tested' repo and bypass the change-queue flow. > Long term, the CI for projects that are current;y handled via timed builds will be done the new 'test-system-artifacts' and 'build-system-artifacts' STD-CI stages (OVIRT-1396) -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1453) Make timed build-artifacts jobs deploy directly to 'tested'
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1453: ----------------------------------- Summary: Make timed build-artifacts jobs deploy directly to 'tested' Key: OVIRT-1453 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1453 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The time build-artifacts jobs currently invoke the old 'deploy-to-experimental' job to deploy their packages into the experimental flow. The new 'deploy-to-experimental' job cannot deploy the packages for the timed build-artifacts jobs because it can only handle merged patches. This is the reason why we kept the old build-artifacts jobs around. Since the artifacts from the timed jobs get deployed to experimental they are also moved to 'tested' after OST succeeds and to the nightly repos. As we prepare to replace the experimental flow with the chage-queue, we need an alternative solution for getting the artifacts from the timed jobs into 'tested'. The experimental test jobs do not currently test the artifacts built by the timed build jobs, namely node and appliance. The proposed solution is therefore to just make the timed build jobs deploy the built artifacs directly to the 'tested' repo and bypass the change-queue flow. Long term, the CI for projects that are current;y handled via timed builds will be done the new 'test-system-artifacts' and 'build-system-artifacts' STD-CI stages (OVIRT-1396) -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1453) Make timed build-artifacts jobs deploy directly to 'tested'
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1453?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1453: -------------------------------- Epic Link: OVIRT-400 > Make timed build-artifacts jobs deploy directly to 'tested' > ----------------------------------------------------------- > > Key: OVIRT-1453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1453 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, deploy-to-experimental, ovirt-engine-appliance, ovirt-node-ng > > The time build-artifacts jobs currently invoke the old 'deploy-to-experimental' job to deploy their packages into the experimental flow. > The new 'deploy-to-experimental' job cannot deploy the packages for the timed build-artifacts jobs because it can only handle merged patches. This is the reason why we kept the old build-artifacts jobs around. > Since the artifacts from the timed jobs get deployed to experimental they are also moved to 'tested' after OST succeeds and to the nightly repos. > As we prepare to replace the experimental flow with the chage-queue, we need an alternative solution for getting the artifacts from the timed jobs into 'tested'. > The experimental test jobs do not currently test the artifacts built by the timed build jobs, namely node and appliance. > The proposed solution is therefore to just make the timed build jobs deploy the built artifacs directly to the 'tested' repo and bypass the change-queue flow. > Long term, the CI for projects that are current;y handled via timed builds will be done the new 'test-system-artifacts' and 'build-system-artifacts' STD-CI stages (OVIRT-1396) -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1451) Add a CI mirror for Gluster 3.10
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1451?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1451: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add a CI mirror for Gluster 3.10 > -------------------------------- > > Key: OVIRT-1451 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1451 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > We currently have mirrors only for Gluster 3.6 and 3.8, since Gluster 3.10 was released, we need to add a mirror for it. > For more information about mirrors: > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Transactional_mirrors/i… > The process to add mirrors is roughly: > # Create a patch to the 'jenkins' repo with: > ## Adding upstream repo configuration to the '{{data/mirrors-reposync.conf}}' file > ## Adding a mirror sync job to '{{jobs/confs/projects/system/sync_mirrors.yaml}}'. > # Verify patch by: > ## Running JJB to create the new sync job > ## Invoke the new sync job to see that it manages to sync the mirror for the 1st time > ## Wait a while to let the job get schedules and run on its own (sync jobs are scheduled every 8 hours by default) > As part of this work please document the process for adding a new mirror in infra-docs. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

About www.ovirt.org TLS cert
by Marc Dequènes (Duck) 18 Jun '17

18 Jun '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lIBBQOd5xJlfx4grVHn7GK3iqTHQD3nfF Content-Type: multipart/mixed; boundary="jIWnohbHnrLDBm9w209XrI73urH0UDQwx"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <cc4752b6-816a-be6b-7ecf-4bfebd35c301(a)redhat.com> Subject: About www.ovirt.org TLS cert --jIWnohbHnrLDBm9w209XrI73urH0UDQwx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, So the Digicert system does not warn you about all certs but only if you were configured to be in some access list at creation or renewal time. I was not in RH when www.ovirt.org cert was issued, so=E2=80=A6 Fortunately I was kindly warned by another guy having access to the system. I requested a renewal yesterday but today it is not yet done. So let's hope it is done when I wake up or during the day. Just to keep you informed. \_o< --jIWnohbHnrLDBm9w209XrI73urH0UDQwx-- --lIBBQOd5xJlfx4grVHn7GK3iqTHQD3nfF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlk27HoACgkQVen596wc RD+SpA//QiFxb61/wvRNhhP8xya1JMVDTORSPe3JiPIXvv1VT0jCHwsc6+bbExnW Tq8cjDFvKYXch00KKFEt6IrsfPyIUvwhzzr7OHu/EPutzUg7JmOGNBFXMZIDD5rD 3sW9v/jsPqKhjIjamwu7PcEEz0C+Lc3q7TLyszPfDHVxIZ8ufZgjEK52QSUOVbT3 XCbltnlVieHzHyI772bUDwaCUFpLNTy/XiRM76GX8xiYPYD78KD8FZNkiDx3RYpx hSpKAcGfeegas/LXg+40Ml38Pd6a/GGEfwQL2+wNAKnId3Q8AcftCtcgz4Kb1aZt toXLHQg0IFGLd7SBgterZ9oWjqH46anntzrnc9SYg21dgDwosALcG9RQxuSkwd0d G8qvydsmEYZ3TyseFjVjE0JsR1ZIyYlLvqRB2ZebpD2JZjiOhMtHfKH9UvFDw4P+ ktZ2iDIOPl/oEBCP7/45p0NjKZrLZdYRpHm3dhJ4UqRtGadvQmYn83bH95FDBtqc K/Wlvh5+OovJbpBwq+2ezJzZ1TYCkktqYq9WYpirkxBI/4+OdccDk/b25/mjIQyU vjFB6PO60Nc3H2T8ST4EFv7i4j46h3Uot3l8sa/i3CVxHaK3gQJQ+4WReoJVBj3R NjB1AkkYhn7PRmtjQ2Wp9A6cwILhWGZYVm2ueyZlXss9pD6L9No= =q4vV -----END PGP SIGNATURE----- --lIBBQOd5xJlfx4grVHn7GK3iqTHQD3nfF--

2 2

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7162 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '17

18 Jun '17

------=_Part_287_1745465884.1497340503363 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7162/, Build Number: 7162, Build Status: FAILURE ------=_Part_287_1745465884.1497340503363--

1 81