- Infra - oVirt List Archives

[CQ]: 88547,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 07 Mar '18

07 Mar '18

Change 88547,3 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/88547/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6095/

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by eyal edri (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520412194-21289-127 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1919: ---------------------------------- Until we have that RFE implemented, we need to document this process, even if its not final. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520412194-21289-127 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1919:</h3> <p>Until we have that RFE implemented, we need to document this process, even if its not final.</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520412194-21289-127--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520411242-30870-123 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1919: ------------------------------------- Please open an RFE ticket for supporting {{ci re-merge please}} in GitHub. It would be veryi simple to implement actually, all it take is a few little code changes in {{pipelines/standard-stage.groovy}} if you care to try... > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520411242-30870-123 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1919:</h3> <p>Please open an RFE ticket for supporting {{ci re-merge please}} in GitHub. It would be veryi simple to implement actually, all it take is a few little code changes in {{pipelines/standard-stage.groovy}} if you care to try…</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520411242-30870-123--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520411126-14008-137 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1919 at 3/7/18 8:25 AM: ------------------------------------------------------------- There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage for any project can be run manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. was (Author: bkorren(a)redhat.com) There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520411126-14008-137 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1919 at 3/7/18 8:25 AM:</h3> <p>There is no ‘ci re-merge please’ command for github, however for pieplien-based jobs (v2) any stage for any project can be run manually using the [standard-manual-runner|<a href="http://jenkins.ovirt.org/job/standard-manual-runner/">http://jenkins.ovirt.org/job/standard-manual-runner/</a>] job.</p> <p>What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be ‘check-merged’.</p> <p>was (Author: bkorren(a)redhat.com) There is no ‘ci re-merge please’ command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|<a href="http://jenkins.ovirt.org/job/standard-manual-runner/">http://jenkins.ovirt.org/job/standard-manual-runner/</a>] job.</p> <p>What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be ‘check-merged’.</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520411126-14008-137--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1919: ------------------------------------- There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520407593-14384-146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1920: ---------------------------------- Issue Type: Task (was: Bug) > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520407593-14384-146 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1920:</h3> <pre>Issue Type: Task (was: Bug)</pre> <blockquote><h3>Modify ci_env_client.py to be case and signs insensitive</h3> <pre> Key: OVIRT-1920 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 Project: oVirt - virtualization made easy Issue Type: Task Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra</pre> <p>In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes).</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520407593-14384-146--

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

Daniel Belenky created OVIRT-1920: ------------------------------------- Summary: Modify ci_env_client.py to be case and signs insensitive Key: OVIRT-1920 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1920: ---------------------------------- Epic Link: OVIRT-400 > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 211 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Mar '18

07 Mar '18

------=_Part_171_710260247.1520307928418 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-mas= ter/=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-maste= r/211/ Build Number: 211 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #211 [Yaniv Kaul] Set custom emulated machine (rhel-7.4) for VM2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: The response content type 'text/html; charset=3Diso-8859-1' isn't the expec= ted XML -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_u= p_4 at 0x45ff230> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 254, in _host_is_up_4 host_obj =3D host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 363= 46, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211,= in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130,= in _check_fault body =3D self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316,= in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849= , in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889= , in _check_content_type raise Error(msg) Error: The response content type 'text/html; charset=3Diso-8859-1' isn't th= e expected XML --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=3D15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, i= n assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 254, in _host_is_up_4 host_obj =3D host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 363= 46, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211,= in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130,= in _check_fault body =3D self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316,= in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849= , in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889= , in _check_content_type raise Error(msg) 'The response content type \'text/html; charset=3Diso-8859-1\' isn\'t the e= xpected XML\n-------------------- >> begin captured logging << ------------= --------\novirtlago.testlib: ERROR: * Unhandled exception in <function = _host_is_up_4 at 0x45ff230>\nTraceback (most recent call last):\n File "/u= sr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_e= quals_within\n res =3D func()\n File "/home/jenkins/workspace/ovirt-sys= tem-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/te= st-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = =3D host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk= 4/services.py", line 36346, in get\n return self._internal_get(headers, = query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.= py", line 211, in _internal_get\n return future.wait() if wait else futu= re\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line = 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/= site-packages/ovirtsdk4/service.py", line 208, in callback\n self._check= _fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/serv= ice.py", line 130, in _check_fault\n body =3D self._internal_read_body(r= esponse)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py",= line 316, in _internal_read_body\n self._connection.check_xml_content_t= ype(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init_= _.py", line 849, in check_xml_content_type\n response.headers\n File "/= usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _che= ck_content_type\n raise Error(msg)\nError: The response content type \'t= ext/html; charset=3Diso-8859-1\' isn\'t the expected XML\n-----------------= ---- >> end captured logging << ---------------------' ------=_Part_171_710260247.1520307928418--

1 1

planned Jenkins restart
by Evgheni Dereveanchin 07 Mar '18

07 Mar '18

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1