[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26310:
----------------------------------
Fix Version/s: 4.9.0.AM2
(was: 4.9.0.AM3)
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM2
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26310:
----------------------------------
Attachment: Screenshot_20180821_103625.png
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM3
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26310:
----------------------------------
Attachment: Screenshot_20180821_103305.png
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM3
>
> Attachments: Screenshot_20180821_103305.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26251) Server adapter: cannot start in Debug using oc 3.11
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26251.
---------------------------------
Closing, I was able to start server adapter in debug with oc 3.11 build from master.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM2
Build id: AM2-v20180815-0130-B3168
Build date: 20180815-0130
> Server adapter: cannot start in Debug using oc 3.11
> ---------------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-26161.
-----------------------------------
Resolution: Done
> Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26161
> URL: https://issues.jboss.org/browse/JBIDE-26161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.9.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Martin Malina
> Fix For: 4.9.0.AM2
>
> Attachments: bigmek-ok.png, bigmek_graphics_issue.png
>
>
> Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others:
> * domek
> * bigmek
> * dev-platform-mac1
> * dev-platform-mac2
> Make dev-platform-macX machines capable to run cdk
> * add them to mac_xhyve label
> Should not be dev-platform-macX upgraded to High Sierra?
> cc: [~nickboldt] [~mmalina]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-26161:
---------------------------------------
[~odockal] can you try now on display :0 (port 5900)?
I tried a tip from here:
https://www.markandersononline.com/blog/apple-remote-desktop-fix-authenti...
Which was to run this command:
{code}
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -allowAccessFor -allUsers -privs -all -clientopts -setmenuextra -menuextra yes
{code}
It changed the Sharing settings on the machine from Screen Sharing to Remote Management. And then I changed the password there once more and it started to work for me.
> Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26161
> URL: https://issues.jboss.org/browse/JBIDE-26161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.9.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Martin Malina
> Fix For: 4.9.0.AM2
>
> Attachments: bigmek-ok.png, bigmek_graphics_issue.png
>
>
> Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others:
> * domek
> * bigmek
> * dev-platform-mac1
> * dev-platform-mac2
> Make dev-platform-macX machines capable to run cdk
> * add them to mac_xhyve label
> Should not be dev-platform-macX upgraded to High Sierra?
> cc: [~nickboldt] [~mmalina]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26284) Servers created from relative path can't start
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26284?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-26284:
-------------------------------------
The steps I used (rough representation of a code):
{noformat}
beans = findServerBeans({ discoveryPath: '../../Downloads/Wildfly12' }) - relative path
createServer({ id: 'wildfly', serverType: beans[0].serverAdapterTypeId, attributes: { 'server.home.dir': beans[0].location } })
startServerAsync({ mode: 'run', params: { id: 'wildfly', serverType: beans[0].serverAdapterTypeId, attributes: { 'server.home.dir': beans[0].location } } })
{noformat}
The start part used to fail, but now something seems to have changed. Now I'm stuck at the first step with an internal error:
{noformat}
SEVERE: Internal error: java.lang.reflect.InvocationTargetException
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:63)
at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.request(GenericEndpoint.java:116)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleRequest(RemoteEndpoint.java:252)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:181)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:183)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:92)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:61)
... 11 more
Caused by: java.lang.NullPointerException
at org.jboss.tools.ssp.server.minishift.discovery.MinishiftDiscovery.folderWhiteListBin(MinishiftDiscovery.java:40)
at org.jboss.tools.ssp.server.minishift.discovery.MinishiftDiscovery.getMinishiftBinaryFromFolder(MinishiftDiscovery.java:26)
at org.jboss.tools.ssp.server.minishift.discovery.MinishiftDiscovery.folderContainsMinishiftBinary(MinishiftDiscovery.java:30)
at org.jboss.tools.ssp.server.minishift.discovery.MinishiftBeanTypeProvider$MinishiftBeanType.isServerRoot(MinishiftBeanTypeProvider.java:35)
at org.jboss.tools.ssp.server.discovery.serverbeans.ServerBeanLoader.loadTypeInternal(ServerBeanLoader.java:54)
at org.jboss.tools.ssp.server.discovery.serverbeans.ServerBeanLoader.loadBeanInternal(ServerBeanLoader.java:47)
at org.jboss.tools.ssp.server.discovery.serverbeans.ServerBeanLoader.getServerBean(ServerBeanLoader.java:35)
at org.jboss.tools.ssp.server.ServerManagementServerImpl.findServerBeans(ServerManagementServerImpl.java:169)
... 16 more
{noformat}
> Servers created from relative path can't start
> ----------------------------------------------
>
> Key: JBIDE-26284
> URL: https://issues.jboss.org/browse/JBIDE-26284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-server-protocol
> Reporter: Jan Richter
> Assignee: Rob Stryker
>
> Servers created with their ''server.home.dir'' attribute set to a relative path will error on starting.
> Example log from wildfly (and yes, that is the complete log):
> {noformat}Error: Could not find or load main class org.jboss.modules.Main{noformat}
> Relative paths either need to be resolved, or rejected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26161:
---------------------------------------
Oh I see it as well, thanks! I consider this to be resolved once more.
> Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26161
> URL: https://issues.jboss.org/browse/JBIDE-26161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.9.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Martin Malina
> Fix For: 4.9.0.AM2
>
> Attachments: bigmek-ok.png, bigmek_graphics_issue.png
>
>
> Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others:
> * domek
> * bigmek
> * dev-platform-mac1
> * dev-platform-mac2
> Make dev-platform-macX machines capable to run cdk
> * add them to mac_xhyve label
> Should not be dev-platform-macX upgraded to High Sierra?
> cc: [~nickboldt] [~mmalina]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months