[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-23732.
---------------------------------
> Implement new batch integration ui tests for content assist features in job.xml file.
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-23732
> URL: https://issues.jboss.org/browse/JBIDE-23732
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.4.2.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: batch, integration_tests
> Fix For: 4.9.0.AM3
>
>
> These tests covers both view tabs where content assist feature is used (design and source view). Test:
> 1. Offered batch artifacts in content assist menu for ref attribute
> 2. Offered element's id for id attribute with correct level of context
> 3. Fully qualified names of exceptions used in class attribute of include/exclude tag
> 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation
> 5. Proper list of element's id referred from next, to attributes and/or restart attributes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-22138.
---------------------------------
Closing. works as expected, verified in:
Red Hat Developer Studio
Version: 12.9.0.AM3
Build id: AM3-v20180906-1322-B3331
Build date: 20180906-1322
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
> Expected result:
> If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26333) CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26333.
---------------------------------
Closing, I was not able to reproduce this.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM3
Build id: AM3-v20180906-1322-B3331
Build date: 20180906-1322
> CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26333
> URL: https://issues.jboss.org/browse/JBIDE-26333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: CDKStartupOSconnError.gif, screenshot-1.png
>
>
> I am watching error being thrown just after cdk server adapter is created and OS untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail).
> {code}
> null
> org.jboss.tools.openshift.cdk.server
> Error
> Sun Sep 02 20:16:37 CEST 2018
> Error contacting OpenShift
> org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://192.168.42.235:8443. The VM may not have been registered successfully. Please check your console output for more information
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26334:
-------------------------------------
Sprint: devex #155 September 2018
> Launcher wizard: improve user experience
> ----------------------------------------
>
> Key: JBIDE-26334
> URL: https://issues.jboss.org/browse/JBIDE-26334
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: launcher_wizard
> Fix For: 4.9.0.Final
>
> Attachments: error-markers-for-missing-info.png, maven-artifact-elements.png, mission-infos.png
>
>
> The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user.
> Suggested improvements:
> * A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide.
> !mission-infos.png!
> * A novice user has no idea what the maven artifact elements are for.
> !maven-artifact-elements.png!
> * Generally speaking it is preferable to decorate missing input fields with a "*" than to mark them as errors (as one can see in most web forms). OpenShift tooling does this as a rule of thumb.
> !error-markers-for-missing-info.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26175.
---------------------------------
Closing, now it works as expected, debug is also ok.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM3
Build id: AM3-v20180906-1322-B3331
Build date: 20180906-1322
> Cannot create server adapter for eap71-basic-s2i template from CDK
> ------------------------------------------------------------------
>
> Key: JBIDE-26175
> URL: https://issues.jboss.org/browse/JBIDE-26175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.6.0.Final
> Environment: CDK: CDK v3.5.0-1
> Red Hat Developer Studio
> Version: 12.0.0.GA
> Build id: GA-v20180706-1014-B2970
> OS: Linux, v.4.17.3-200.fc28.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.3
> Java version: 1.8.0_172
> Reporter: Josef Kopriva
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: application_wizard, regression, server_adapter, upstream
> Fix For: 4.9.0.AM3
>
>
> I was not able to create server adapter for eap71-basic-s2i template application.
> Pod error log:
> {code:java}
> --> Scaling eap-app-1 down to zero
> --> Scaling eap-app-2 to 1 before performing acceptance check
> error: update acceptor rejected eap-app-2: pods for rc 'myproject/eap-app-2' took longer than 600 seconds to become available
> {code}
> Error log from OpenShift console:
> {code:java}
> Readiness probe failed: {
> "probe.eap.dmr.EapProbe": {
> "probe.eap.dmr.ServerStatusTest": "running",
> "probe.eap.dmr.DeploymentTest": "Exception executing test: unorderable types: Status() < Status()",
> "probe.eap.dmr.BootErrorsTest": [
> {
> "failed-operation": {
> "operation": "deploy",
> "address": [
> {
> "deployment": "kitchensink.war"
> }
> ]
> },
> "failure-description": "{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"kitchensink.war\\\".FIRST_MODULE_USE\" => \"WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \\\"kitchensink.war\\\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\\\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\\\".statistics is already registered\"}}",
> "failed-services": {
> "jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE": "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"
> }
> }
> ]
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months