August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16161: --------------------------------------- Oops. I guess we do need it then. > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4514) Can't install rh-eclipse47, rpmlint and more stuff on rhel7 slaves

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4514?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4514. ------------------------------ > Can't install rh-eclipse47, rpmlint and more stuff on rhel7 slaves > ------------------------------------------------------------------ > > Key: JBDS-4514 > URL: https://issues.jboss.org/browse/JBDS-4514 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, integration-tests, rpm > Affects Versions: 11.1.0.AM1 > Environment: Slaves based on rhel-7.3-server-x86_64-latest image. > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 11.1.0.AM1 > > > Some tests \[1\]\[2\] are broken because yum is not able to download some packages (libdwarf, rpmdevtools,rpmlint,tcl). > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > \[2\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > RPM is trying to download some packages from folder which has been deleted \[3\]. > \[3\] http://download.lab.bos.redhat.com/rel-eng/RHEL-7.3-20161019.0/compose > Download is failing on http 404 and yum surprisingly doesn't try another repositories. > Repository \[3\] comes from /etc/yum.repos.d/compose.repo and is stored in base image "rhel-7.3-server-x86_64-latest". We need to delete, disable or update this repository. > As a temporary workaround I have added "rm -f /etc/yum.repos.d/compose.repo" to \[1\] and \[2\]. -- 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 commented on JBIDE-24882: -------------------------------------- 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.AM1 > > > 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-24884) Log an error if detected cdk registry is wrong

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24884?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24884: --------------------------------------- That seems reasonable. I will verify this in time. > Log an error if detected cdk registry is wrong > ---------------------------------------------- > > Key: JBIDE-24884 > URL: https://issues.jboss.org/browse/JBIDE-24884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > This is a followup of JBIDE-24783. > When minishift openshift registry is unable to return a valid registry, the tooling should log an error. JBIDE-24783 was supposed to add this thing (along with removing the default value), but I was not able to trigger the error. > The workflow is: > Once cdk is started in eclipse, the cdk tooling will create the openshift connection and run minishift openshift registry to figure out which registry to use. But in my testing even if this returns "bla bla", the tooling will happily accept it. > To test this, you can use a simple minishift wrapper such as this: > {code} > #!/bin/bash > case $* in > "openshift registry") > echo bla bla > exit 1 > ;; > *) > /Users/rasp/jbossqa/cdk/cdk-3.1.0/minishift $* > esac > {code} > You can also remove the "exit 1" to check what happens with zero exit code. > In my opinion any of these should trigger an error: > a) minishift openshift registry finishes with a non-zero code > b) the returned string is not a valid url -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-24222 at 8/24/17 2:15 AM: ---------------------------------------------------------------- {quote} Hmm, that did not seem to work, but maybe I have to first close Eclipse before editing the XML and then re-start it. I tried to edit the XML while Eclipse was still running and that did not work. I will try again. {quote} Don't edit the XML, edit the launch config in Eclipse - let me rephrase what I said: The workaround is to go to the launch config and change the PATH to something reasonable: 1. Open cdk server editor by double-clicking the CDK adapter in Servers view 2. In the server editor, click Open launch configuration (almost at the top) 3. In the launch config window, go to the Environment tab 4. Edit the PATH variable to something reasonable. Apply and close. The XML takes the PATH value from the launch config in Eclipse. So once you change the launch config to a reasonable PATH value, you should be fine. And yes, in the launch config the PATH is initially determined by some calls in the code which obviously return rubbish sometimes. So we need to figure out why - that will be dealt with in the other JIRA. In the meantime use the workaround. was (Author: mmalina): {quote} Hmm, that did not seem to work, but maybe I have to first close Eclipse before editing the XML and then re-start it. I tried to edit the XML while Eclipse was still running and that did not work. I will try again. {quote} Don't edit the XML, edit the launch config in Eclipse - let me rephrase what I said: The workaround is to go to the launch config and change the PATH to something reasonable: 1. Open cdk server editor by double-clicking the CDK adapter in Servers view 2. In the server editor, click Open launch configuration (almost at the top) 3. In the launch config window, go to the Environment tab 4. Edit the PATH variable to something reasonable. Apply and close. The XML takes the PATH value from the launch config in Eclipse. So once you change the launch config to a reasonable PATH value, you should be fine. > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Martin Malina > Priority: Critical > Labels: help_wanted > Fix For: 4.5.x > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24222: --------------------------------------- {quote} Hmm, that did not seem to work, but maybe I have to first close Eclipse before editing the XML and then re-start it. I tried to edit the XML while Eclipse was still running and that did not work. I will try again. {quote} Don't edit the XML, edit the launch config in Eclipse - let me rephrase what I said: The workaround is to go to the launch config and change the PATH to something reasonable: 1. Open cdk server editor by double-clicking the CDK adapter in Servers view 2. In the server editor, click Open launch configuration (almost at the top) 3. In the launch config window, go to the Environment tab 4. Edit the PATH variable to something reasonable. Apply and close. The XML takes the PATH value from the launch config in Eclipse. So once you change the launch config to a reasonable PATH value, you should be fine. > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Martin Malina > Priority: Critical > Labels: help_wanted > Fix For: 4.5.x > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff > > -- 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/24/17 1:55 AM: --------------------------------------------------------------- As scripts are executed under root user all the files in /home/hudson/.ssh was owned by root. For the security reason write access to /home/hudson/.ssh/config may have only owner. So I created these PRs: 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... was (Author: lvalach): As scripts are executed under root user all the files in /home/hudson/.ssh was owned by root. For the security reason write access to /home/hudson/.ssh/config may have only owner. So I created this PR: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/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.AM1 > > > 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-24888) wrong project lead for JBIDE and JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24888?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-24888: --------------------------------------------- >No, I didn't have permissions to change that. Thanks Max. stupid permission system - take note :) > wrong project lead for JBIDE and JBDS > ------------------------------------- > > Key: JBIDE-24888 > URL: https://issues.jboss.org/browse/JBIDE-24888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cleanup > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.5.1.AM1 > > Attachments: alexey-is-still-project-lead.png > > > Looks like no one ever changed the project lead from Alexey to Jeff. > !alexey-is-still-project-lead.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24888) wrong project lead for JBIDE and JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24888?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-24888: ---------------------------------------- No, I didn't have permissions to change that. Thanks Max. > wrong project lead for JBIDE and JBDS > ------------------------------------- > > Key: JBIDE-24888 > URL: https://issues.jboss.org/browse/JBIDE-24888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cleanup > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.5.1.AM1 > > Attachments: alexey-is-still-project-lead.png > > > Looks like no one ever changed the project lead from Alexey to Jeff. > !alexey-is-still-project-lead.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24888) wrong project lead for JBIDE and JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24888?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24888. ------------------------------ Muchas gracias, hombre. > wrong project lead for JBIDE and JBDS > ------------------------------------- > > Key: JBIDE-24888 > URL: https://issues.jboss.org/browse/JBIDE-24888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cleanup > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.5.1.AM1 > > Attachments: alexey-is-still-project-lead.png > > > Looks like no one ever changed the project lead from Alexey to Jeff. > !alexey-is-still-project-lead.png! -- 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