August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ If I get things right changing the router timeout seems non-available to the non-admin user. Then it seems as if we could forward the ports from the ports directly (not connecting via the router). I believe that this is what we're doing currently: {code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/behavior/OpenShiftLaunchController.java#L360} Set<PortPair> podPorts = PortForwardingUtils.getForwardablePorts(pod); {code} So far I believe that we're not affected by the timeout in the router. But then, it this scenario there's apparently a timeout in the port-forwaring, too, as discussed here: https://issues.jboss.org/browse/JBIDE-23422?focusedCommentId=13334141&pag.... In arquillian they add a keep-alive ping, something we cannot do since we use oc to forward the ports and thus are not in control of that socket. I believe that we should reach out to openshift for advice how to tackle this since it makes debugging pretty useless. [~rhuss] [~jeffmaury] [~aurelien.pupier] Thoughts? > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24882: --------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m...) > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach edited comment on JBIDE-24882 at 8/29/17 8:38 AM: --------------------------------------------------------------- A test "test_connected_to_github_user" \[1\] was failing with fillowing message: {quote} ASSERT:Failed with (1): Hi devstudio-release! You've successfully authenticated, but GitHub does not provide shell access. {quote} This state should be accepted but test was expecting different user name (JBossJenkins). After PR \[2\] is merged test accept both user names. \[1\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/b... \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m... was (Author: lvalach): A test "test_connected_to_github_user" \[1\] was failing with fillowing message: {quote} ASSERT:Failed with (1): Hi devstudio-release! You've successfully authenticated, but GitHub does not provide shell access. {quote} This state should be accepted but test was expecting different user name (JBossJenkins). After PR \[2\] is merged test accept both user names. \[1\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/b... \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m... > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24656) Split CDK3 server adapter integration tests into separated classes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24656?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24656: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1848, https://github.com/jbosstools/jbosstools-openshift/pull/1554 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1848) > Split CDK3 server adapter integration tests into separated classes > ------------------------------------------------------------------ > > Key: JBIDE-24656 > URL: https://issues.jboss.org/browse/JBIDE-24656 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.5.1.AM2 > > > I decided to divide quite time-consuming CDK server adapter integration tests into smaller test cases due to time that is needed to run all of these test cases in one test class. The one class with all server adapter test cases will be divide into 4 independent classes. > org.jboss.tools.cdk.ui.bot.test.server.adapter.CDK3IntegrationTest will be split into > CDK3IntegrationStartTest > CDK3IntegrationRestartTest > CDK3IntegrationDockerTest > CDK3IntegrationOpenshiftTest > It will be possible to run cdk pr-check job much faster, if it would contain only one complex test case, instead of 4 test cases that each requires to start cdk 3 server adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24903: ---------------------------------------- Assignee: Dmitrii Bocharov [~adietish] ok, taking it. Thank you! > Sonar: report correct test coverage (by using a build that does not use pack2000) > ---------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: build, sonar, test, test-coverage > Fix For: 4.5.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-24903: ------------------------------------ Description: Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% !image-2017-08-29-14-07-45-069.png! According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% !image-2017-08-29-14-11-01-604.png! was: Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% !image-2017-08-29-14-07-45-069.png! According to [~lhein] this is caused by the fact that we build using pack2000. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack2000 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% !image-2017-08-29-14-11-01-604.png! > Sonar: report correct test coverage (by using a build that does not use pack2000) > ---------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Labels: build, sonar, test, test-coverage > Fix For: 4.5.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24903: ------------------------------------- Labels: build sonar test test-coverage (was: ) > Sonar: report correct test coverage (by using a build that does not use pack2000) > ---------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Labels: build, sonar, test, test-coverage > Fix For: 4.5.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack2000. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack2000 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24903: ------------------------------------------ [~dbocharov] is this something you'd be willing to tackle since you're the one with the most knowledge about sonar in our team? > Sonar: report correct test coverage (by using a build that does not use pack2000) > ---------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack2000. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack2000 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24903: ---------------------------------------- Summary: Sonar: report correct test coverage (by using a build that does not use pack2000) Key: JBIDE-24903 URL: https://issues.jboss.org/browse/JBIDE-24903 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.5.1.AM1 Reporter: Andre Dietisheim Fix For: 4.5.x Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% !image-2017-08-29-14-07-45-069.png! According to [~lhein] this is caused by the fact that we build using pack2000. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack2000 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24883) Python on windows slaves

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24883?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-24883: ------------------------------- Story Points: 8 > Python on windows slaves > ------------------------- > > Key: JBIDE-24883 > URL: https://issues.jboss.org/browse/JBIDE-24883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Labels: central-ci > Fix For: 4.5.1.AM2 > > > python installation needs to be scripted in mwqa-cloud-slaves to be installed automatically when provisioning from openstack. > Purpose: facilitate running cross-platform scripts (eg., for JDK detection & discovery). Will allow Nick to start porting .sh script to .py so they can be used on all OSes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017