[JIRA] (OVIRT-1679) Move Lago to use the STDCI pipelines
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1679?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1679:
--------------------------------
Epic Link: OVIRT-400
> Move Lago to use the STDCI pipelines
> ------------------------------------
>
> Key: OVIRT-1679
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1679
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Lago, oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: change-queue, github, jenkins, lago, standard-ci
>
> Because of work on OVIRT-1522, OVIRT-1599, we now have new pipeline jobs for GitHub projects. OVIRT-1486 and OVIRT-1534 gave us the ability to create change queues for GitHub projects. This is time to seriosly consider moving Lago from its old lago-specific STDCI clone to the general STDCI/CQ scheme.
> Once we do that, we can also remove all the templates that are only used by Lago ATM.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
6 years, 6 months
[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jir... ]
eyal edri updated OVIRT-1170:
-----------------------------
Resolution: Done
Status: Done (was: Blocked)
No reply on this ticket, if it will be needed in the future, please reopen it with relevant info.
> add option to disable networking (or have it off by default)
> ------------------------------------------------------------
>
> Key: OVIRT-1170
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Greg Sheremeta
> Assignee: infra
>
> Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahoste... )
> In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
6 years, 6 months
[JIRA] (OVIRT-1678) Move gerrit-admin project to be standard CI
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506583670-23349-172
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1678?page=com.atlassian.jir... ]
eyal edri updated OVIRT-1678:
-----------------------------
Epic Link: OVIRT-411
> Move gerrit-admin project to be standard CI
> -------------------------------------------
>
> Key: OVIRT-1678
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Gerrit/git
> Reporter: eyal edri
> Assignee: infra
>
> Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks.
> This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way.
> I would start with adding a 'check-patch.sh' script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks.
> It's also a great way to learn more about how to create a stanard CI project.
> More info on it can be found on the infra docs page:
> http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
------------=_1506583670-23349-172
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1678?page=com.atlassian.jir... ]</pre>
<h3>eyal edri updated OVIRT-1678:</h3>
<pre>Epic Link: OVIRT-411</pre>
<blockquote><h3>Move gerrit-admin project to be standard CI</h3>
<pre> Key: OVIRT-1678
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Gerrit/git
Reporter: eyal edri
Assignee: infra</pre>
<p>Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks. This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way. I would start with adding a ‘check-patch.sh’ script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks. It's also a great way to learn more about how to create a stanard CI project. More info on it can be found on the infra docs page: <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...</a></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100063)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1506583670-23349-172--
6 years, 6 months
[JIRA] (OVIRT-1678) Move gerrit-admin project to be standard CI
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506583670-25926-202
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
eyal edri created OVIRT-1678:
--------------------------------
Summary: Move gerrit-admin project to be standard CI
Key: OVIRT-1678
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Gerrit/git
Reporter: eyal edri
Assignee: infra
Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks.
This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way.
I would start with adding a 'check-patch.sh' script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks.
It's also a great way to learn more about how to create a stanard CI project.
More info on it can be found on the infra docs page:
http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
------------=_1506583670-25926-202
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>eyal edri created OVIRT-1678:</h3>
<pre> Summary: Move gerrit-admin project to be standard CI
Key: OVIRT-1678
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Gerrit/git
Reporter: eyal edri
Assignee: infra</pre>
<p>Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks.</p>
<p>This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way. I would start with adding a ‘check-patch.sh’ script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks.</p>
<p>It's also a great way to learn more about how to create a stanard CI project. More info on it can be found on the infra docs page: <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa...</a></p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100063)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1506583670-25926-202--
6 years, 6 months
[JIRA] (OVIRT-1677) The infra-docs check-patch jobs are not voting
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506583021-14540-181
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1677:
-----------------------------------
Summary: The infra-docs check-patch jobs are not voting
Key: OVIRT-1677
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1677
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Priority: High
The CI jos for infra-doc are not voting.
See example here: https://gerrit.ovirt.org/c/80836/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
------------=_1506583021-14540-181
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1677:</h3>
<pre> Summary: The infra-docs check-patch jobs are not voting
Key: OVIRT-1677
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1677
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Priority: High</pre>
<p>The CI jos for infra-doc are not voting. See example here: <a href="https://gerrit.ovirt.org/c/80836/">https://gerrit.ovirt.org/c/80836/</a></p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100063)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1506583021-14540-181--
6 years, 6 months
[JIRA] (OVIRT-1676) Refresh oVirt Gerrit Hooks documentation
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1676?page=com.atlassian.jir... ]
eyal edri updated OVIRT-1676:
-----------------------------
Epic Link: OVIRT-411
> Refresh oVirt Gerrit Hooks documentation
> -----------------------------------------
>
> Key: OVIRT-1676
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1676
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Gerrit/git
> Reporter: eyal edri
> Assignee: infra
> Priority: High
>
> There has been a lot of work done and improvements around the oVirt Gerrit Hooks in the past year, including refactoring of the whole projects, moving to Python, adding new hooks and consolidating libraries.
> However, the official documentation for it has remained outdated and doesn't reflect the latest updates.
> We need to go over all current docs and refresh it with new updated content ( i.e remove obsolete info and add info on the new stuff ).
> The current locations (at least that I'm aware of) that needs updating:
> * ovirt.org: https://ovirt.org/develop/infra/gerrit-hooks/
> * I recommend to remove this page and add a link to gerrit-hooks readthedocs page instead
> * However, I would recommend adding a section on it here https://ovirt.org/develop/dev-process/working-with-gerrit/ and mentioning that each project has various hooks that adds automation and verfication.
> * oVirt infra RTD: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Gerrit_Hooks/index.html
> * This needs a refresh and should focus on how to deploy hooks on a project, enable different suites, type of suites, etc.. ( so basically a simple "user guide" or usage guide )
> * Gerrit Hooks RTD: http://ovirt-gerrit-hooks.readthedocs.io/en/latest/
> * This should be completely refactored, as the design and code changed significantly
> * The first section should be aimed at infra team, explaining the design of the project, deployment on the Gerrit server, steps to deploy new code, and anything admin would need to know about the project
> * The second section should be auto-generated from the code itself and show the documentation on all the classes and functions.
> [~sbendavi(a)redhat.com][~amarchuk] I think we can take advantage of the quiet time during the shutdown to start focusing on this important task and get some progress.
> Let me know if I missed anything.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
6 years, 6 months
[JIRA] (OVIRT-1676) Refresh oVirt Gerrit Hooks documentation
by eyal edri (oVirt JIRA)
eyal edri created OVIRT-1676:
--------------------------------
Summary: Refresh oVirt Gerrit Hooks documentation
Key: OVIRT-1676
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1676
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Gerrit/git
Reporter: eyal edri
Assignee: infra
Priority: High
There has been a lot of work done and improvements around the oVirt Gerrit Hooks in the past year, including refactoring of the whole projects, moving to Python, adding new hooks and consolidating libraries.
However, the official documentation for it has remained outdated and doesn't reflect the latest updates.
We need to go over all current docs and refresh it with new updated content ( i.e remove obsolete info and add info on the new stuff ).
The current locations (at least that I'm aware of) that needs updating:
* ovirt.org: https://ovirt.org/develop/infra/gerrit-hooks/
* I recommend to remove this page and add a link to gerrit-hooks readthedocs page instead
* However, I would recommend adding a section on it here https://ovirt.org/develop/dev-process/working-with-gerrit/ and mentioning that each project has various hooks that adds automation and verfication.
* oVirt infra RTD: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Gerrit_Hooks/index.html
* This needs a refresh and should focus on how to deploy hooks on a project, enable different suites, type of suites, etc.. ( so basically a simple "user guide" or usage guide )
* Gerrit Hooks RTD: http://ovirt-gerrit-hooks.readthedocs.io/en/latest/
* This should be completely refactored, as the design and code changed significantly
* The first section should be aimed at infra team, explaining the design of the project, deployment on the Gerrit server, steps to deploy new code, and anything admin would need to know about the project
* The second section should be auto-generated from the code itself and show the documentation on all the classes and functions.
[~sbendavi(a)redhat.com][~amarchuk] I think we can take advantage of the quiet time during the shutdown to start focusing on this important task and get some progress.
Let me know if I missed anything.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
6 years, 6 months
Build failed in Jenkins: system-sync_mirrors-glusterfs-3.8-el7-x86_64 #754
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-3.8-el7-x86_64...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-3.8-el7-x86_64...>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune
> git rev-parse origin/patch^{commit} # timeout=10
> git rev-parse patch^{commit} # timeout=10
Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch)
Commit message: "Exclude big packages from mirrors"
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f
> git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10
[system-sync_mirrors-glusterfs-3.8-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6441380287128143197.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-3.8-el7 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1478, in _commonLoadRepoXML
self._revertOldRepoXML()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in _revertOldRepoXML
os.rename(old_data['old_local'], old_data['local'])
OSError: [Errno 2] No such file or directory
Build step 'Execute shell' marked build as failure
6 years, 6 months