[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520780298-10370-189
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
eyal edri reassigned OVIRT-1915:
--------------------------------
Assignee: Dusan Dodor (was: infra)
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: Dusan Dodor
> Labels: jenkins, ost
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1520780298-10370-189
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]</pre>
<h3>eyal edri reassigned OVIRT-1915:</h3>
<pre>Assignee: Dusan Dodor (was: infra)</pre>
<blockquote><h3>Add option to filter packages in OST manual</h3>
<pre> Key: OVIRT-1915
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: Dusan Dodor
Labels: jenkins, ost</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1520780298-10370-189--
6 years, 8 months
[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
eyal edri edited comment on OVIRT-1915 at 3/11/18 2:56 PM:
-----------------------------------------------------------
Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.
{code:java}
ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos
{code}
was (Author: eedri):
Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.
{quote}ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote}
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
> Labels: jenkins, ost
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
6 years, 8 months
[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520780153-28237-134
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
eyal edri edited comment on OVIRT-1915 at 3/11/18 2:55 PM:
-----------------------------------------------------------
Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.
{quote}ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote}
was (Author: eedri):
Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.
ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
> Labels: jenkins, ost
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1520780153-28237-134
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]</pre>
<h3>eyal edri edited comment on OVIRT-1915 at 3/11/18 2:55 PM:</h3>
<p>Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.</p>
<pre>{quote}ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote}</pre>
<p>was (Author: eedri): Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.</p>
<pre>ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos</pre>
<blockquote><h3>Add option to filter packages in OST manual</h3>
<pre> Key: OVIRT-1915
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: infra
Labels: jenkins, ost</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1520780153-28237-134--
6 years, 8 months
[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1915:
----------------------------------
Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.
ARCHS=("x86_64 noarch")
echo -n "" > ${EXT_RESOURCES}
for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done
sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
> Labels: jenkins, ost
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
6 years, 8 months
[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]
Greg Sheremeta updated OST-99:
------------------------------
Description:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
...
Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting...]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.
---
https://gerrit.ovirt.org/#/c/67166
was:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
...
Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting...]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.
> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
> Key: OST-99
> URL: https://ovirt-jira.atlassian.net/browse/OST-99
> Project: oVirt system tests
> Issue Type: Improvement
> Reporter: Greg Sheremeta
> Assignee: infra
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
6 years, 8 months
[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520772085-26371-157
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]
Greg Sheremeta commented on OST-99:
-----------------------------------
I have this working and a patch posted -- closing.
Thanks for the help everyone!
> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
> Key: OST-99
> URL: https://ovirt-jira.atlassian.net/browse/OST-99
> Project: oVirt system tests
> Issue Type: Improvement
> Reporter: Greg Sheremeta
> Assignee: infra
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1520772085-26371-157
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]</pre>
<h3>Greg Sheremeta commented on OST-99:</h3>
<p>I have this working and a patch posted — closing.</p>
<p>Thanks for the help everyone!</p>
<blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3>
<pre> Key: OST-99
URL: https://ovirt-jira.atlassian.net/browse/OST-99
Project: oVirt system tests
Issue Type: Improvement
Reporter: Greg Sheremeta
Assignee: infra</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1520772085-26371-157--
6 years, 8 months
[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520771999-12112-110
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]
Greg Sheremeta updated OST-99:
------------------------------
Description:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
...
Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting...]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.
was:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
> Key: OST-99
> URL: https://ovirt-jira.atlassian.net/browse/OST-99
> Project: oVirt system tests
> Issue Type: Improvement
> Reporter: Greg Sheremeta
> Assignee: infra
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1520771999-12112-110
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]</pre>
<h3>Greg Sheremeta updated OST-99:</h3>
<pre>Description:</pre>
<p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.</p>
<p>The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.</p>
<p>Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<p>…</p>
<p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...</a>]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.</p>
<pre>was:</pre>
<p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.</p>
<p>The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.</p>
<p>Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3>
<pre> Key: OST-99
URL: https://ovirt-jira.atlassian.net/browse/OST-99
Project: oVirt system tests
Issue Type: Improvement
Reporter: Greg Sheremeta
Assignee: infra</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1520771999-12112-110--
6 years, 8 months
