- Infra - oVirt List Archives

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508837573-23408-175 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1717: -------------------------------- Epic Link: OVIRT-400 > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508837573-23408-175 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1717:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>When a component build passes OST, tag its git hash</h3> <pre> Key: OVIRT-1717 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra</pre> <p>Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508837573-23408-175--

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1717: -------------------------------- Component/s: (was: OST) oVirt CI Epic Link: OVIRT-400 > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by danken (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508837411-18726-656 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit danken created OVIRT-1717: ----------------------------- Summary: When a component build passes OST, tag its git hash Key: OVIRT-1717 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508837411-18726-656 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>danken created OVIRT-1717:</h3> <pre> Summary: When a component build passes OST, tag its git hash Key: OVIRT-1717 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra</pre> <p>Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508837411-18726-656--

1 0

[JIRA] (OVIRT-1683) Add a type key to the list of available upstream sources
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508834573-31675-141 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1683?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1683: -------------------------------- Assignee: infra (was: Gil Shinar) Epic Link: OVIRT-400 > Add a type key to the list of available upstream sources > -------------------------------------------------------- > > Key: OVIRT-1683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > Currently, code supports the following upstream_sources.yaml file: > git: > - url: <git url> > commit: <git commit> > branch: <branch name> > and we need to support: > - type: git > url: <git url> > commit: <git commit> > branch: <branch name> > - type: svn > url: <svn url> > commit: <svn revision> > branch: <branch name> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508834573-31675-141 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1683?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1683:</h3> <pre> Assignee: infra (was: Gil Shinar) Epic Link: OVIRT-400</pre> <blockquote><h3>Add a type key to the list of available upstream sources</h3> <pre> Key: OVIRT-1683 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1683 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra</pre> <p>Currently, code supports the following upstream_sources.yaml file: git:</p> <pre>- url: <git url> commit: <git commit> branch: <branch name></pre> <p>and we need to support:</p> <ul><li><p>type: git url: <git url> commit: <git commit> branch: <branch name></p></li> <li><p>type: svn url: <svn url> commit: <svn revision> branch: <branch name></p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508834573-31675-141--

1 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508833816-21920-181 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1508: -------------------------------- Assignee: infra (was: Gil Shinar) > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508833816-21920-181 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1508:</h3> <pre>Assignee: infra (was: Gil Shinar)</pre> <blockquote><h3>create command line out of upstream_source_collector.py script</h3> <pre> Key: OVIRT-1508 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra</pre> <p>The benefits we will have by moving it into a a separate script are: 1) Not embedding the script inside Jenkins – We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible.</p> <pre>The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it.</pre> <p>2) use the script as command line tool – When developers wants to run it locally on their cloned D/S projects. 3) Use hash as U/S projects folders – When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding.</p> <pre>Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508833816-21920-181--

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508833363-20697-150 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-978: ---------------------------- Resolution: Fixed Status: Done (was: To Do) haven't seen this in a while, not needed for now. > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > Priority: Low > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508833363-20697-150 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ]</pre> <h3>eyal edri updated OVIRT-978:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <p>haven't seen this in a while, not needed for now.</p> <blockquote><h3>Move ovirt-engine & vdsm projects from git:// to <a href="http:///">http://</a> to reduce load from git service</h3> <pre> Key: OVIRT-978 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: danken Assignee: infra Priority: Low</pre> <p>Occasionally, e.g. <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso…</a> I see these failures 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: <a href="https://gerrit.ovirt.org/68804">https://gerrit.ovirt.org/68804</a> 07:29:50 [EnvInject] – Loading node environment variables. 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx local_disk nested) in workspace /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 07:29:50 Fetching changes from the remote Git repository 07:29:50 > git config remote.origin.url git://gerrit.ovirt.org/vdsm.git # timeout=10 07:29:50 Cleaning workspace 07:29:50 > git rev-parse --verify HEAD # timeout=10 07:29:50 Resetting working tree 07:29:50 > git reset --hard # timeout=10 07:29:51 > git clean -fdx # timeout=10 07:29:51 Pruning obsolete local branches 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git 07:29:51 > git --version # timeout=10 07:29:51 > git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune 07:29:51 ERROR: Error fetching remote repo ‘origin’ 07:29:51 hudson.plugins.git.GitException: Failed to fetch from git://gerrit.ovirt.org/vdsm.git</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508833363-20697-150--

1 0

[JIRA] (OVIRT-1676) Refresh oVirt Gerrit Hooks documentation
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508833269-26273-114 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1676?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1676: -------------------------------- Assignee: Shlomo Ben David (was: infra) > 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: Shlomo Ben David > 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#100068) ------------=_1508833269-26273-114 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1676?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1676:</h3> <pre>Assignee: Shlomo Ben David (was: infra)</pre> <blockquote><h3>Refresh oVirt Gerrit Hooks documentation</h3> <pre> 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: Shlomo Ben David Priority: High</pre> <p>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:</p> <ul><li><p>ovirt.org: <a href="https://ovirt.org/develop/infra/gerrit-hooks/">https://ovirt.org/develop/infra/gerrit-hooks/</a></p> <pre>* 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.</pre></li> <li><p>oVirt infra RTD: <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Gerrit_Hooks/index.html">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Gerrit_Hooks/index.html</a></p> <ul><li><p>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 )</p></li></ul></li> <li><p>Gerrit Hooks RTD: <a href="http://ovirt-gerrit-hooks.readthedocs.io/en/latest/">http://ovirt-gerrit-hooks.readthedocs.io/en/latest/</a></p> <pre>* 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.</pre></li></ul> <p>[~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.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508833269-26273-114--

1 0

[JIRA] (OVIRT-1474) automerge poll stage patches
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1474?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1474: -------------------------------- Assignee: infra (was: Gil Shinar) > automerge poll stage patches > ---------------------------- > > Key: OVIRT-1474 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1474 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Gil Shinar > Assignee: infra > Priority: High > Labels: standard-ci > > Add a Boolean parameter to the standard temlate that'll be used only in the pool stage. > This parameter will be evaluated from the project file with true or false and will be used in the poll python script -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-1366) ovirt-engine maven caching configuration in CI prevents using mock_runner locally
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508832878-23308-147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1366?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1366: -------------------------------- Assignee: infra (was: Gil Shinar) > ovirt-engine maven caching configuration in CI prevents using mock_runner locally > --------------------------------------------------------------------------------- > > Key: OVIRT-1366 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1366 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: ovirt-engine, standard-ci > > The engine STD-CI is configured currently to store the maven cache on the slave in '{{/home/jenkins/maven_cache}}'. This works well in CI but effectively renders that STD-CI scripts unusable for people trying to run '{{mock_runner.sh}}' locally with the engine repo. > We need to move the cache somewhere else that would be writeable on any machine. '{{/var/tmp}}' seems like a good candidate. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508832878-23308-147 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1366?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1366:</h3> <pre>Assignee: infra (was: Gil Shinar)</pre> <blockquote><h3>ovirt-engine maven caching configuration in CI prevents using mock_runner locally</h3> <pre> Key: OVIRT-1366 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1366 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: ovirt-engine, standard-ci</pre> <p>The engine STD-CI is configured currently to store the maven cache on the slave in ‘{{/home/jenkins/maven_cache}}’. This works well in CI but effectively renders that STD-CI scripts unusable for people trying to run ‘{{mock_runner.sh}}’ locally with the engine repo. We need to move the cache somewhere else that would be writeable on any machine. ‘{{/var/tmp}}’ seems like a good candidate.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508832878-23308-147--

1 0

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508832851-27473-126 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1394: -------------------------------- Assignee: infra (was: Gil Shinar) No clear decision on this yet and doesn't seem to an urgent task. We might need to look into it again when we decide how we move forward with mock runner or the way we run jobs in CI. > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508832851-27473-126 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1394:</h3> <pre>Assignee: infra (was: Gil Shinar)</pre> <p>No clear decision on this yet and doesn't seem to an urgent task. We might need to look into it again when we decide how we move forward with mock runner or the way we run jobs in CI.</p> <blockquote><h3>Remove STD-CI cleanup function cleanup_var</h3> <pre> Key: OVIRT-1394 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra</pre> <p>We do not remember why /var/tmp is being cleaned on each STD-CI job. /var/tmp is good place for caching stuff (maven for example). I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508832851-27473-126--

1 0