[JBoss JIRA] (JBIDE-19903) Build/test timeout after 5 hours
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19903?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19903:
---------------------------------------------
...and why not have this definition in the root pom.xml ? seems unnecessary to duplicate this across everyone.
> Build/test timeout after 5 hours
> --------------------------------
>
> Key: JBIDE-19903
> URL: https://issues.jboss.org/browse/JBIDE-19903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, cdi-extensions, seam2
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: screenshot.jpg, seam.ui.test.log.txt
>
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> 03:33:03 Failed tests:
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForType:29 Match not found (file - /numberguess/web/giveup.jspx name - numberGuess)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod1:44 Match not found (file - /numberguess/web/giveup.jspx name - remainingGuesses)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod2:59 Match not found (file - /numberguess/web/giveup.jspx name - possibilities)
> 03:33:03
> 03:33:03 Tests run: 86, Failures: 3, Errors: 0, Skipped: 0
> 03:33:03
> 03:33:08 [ERROR] There are test failures.
> {code}
> {code}
> 04:39:42 Running org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite230
> 04:40:10 Jun 02, 2015 4:40:10 AM org.hibernate.eclipse.HibernatePlugin start
> 04:40:10 INFO: HibernatePlugin Started
> 04:40:55 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj-ejb
> 04:40:56 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj
> 04:41:25 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:25 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj-ejb
> 04:41:27 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj
> 04:41:58 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj-ejb
> 04:41:59 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj
> 04:42:03 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:03 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoTemplLibPrj
> 04:42:11 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:11 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:14 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoLibPrj
> 04:42:26 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warTemplLibPrj
> 04:42:53 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warLibPrj
> 04:42:57 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:57 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib{code}
> {code}
> 05:02:54 [INFO] --- tycho-pack200b-plugin:0.22.0:pack (pack200-pack) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO] Pack200 packing jar /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seamfp.ui.test/target/org.jboss.tools.seamfp.ui.test-3.7.0-SNAPSHOT.jar
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (attached-p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:56 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-noauth-4.3.0.GA_CP03.zip
> 05:02:56 Build timed out (after 300 minutes). Marking the build as aborted.
> 05:02:56 Terminating xvnc.
> 05:02:57 $ vncserver -kill :43
> 05:03:07 Killing Xvnc process ID 13038
> 05:03:09 Xvnc seems to be deadlocked. Kill the process manually and then re-run
> 05:03:09 /usr/bin/vncserver -kill :43
> 05:03:09 to clean up the socket files.
> 05:03:09 Build was aborted
> 05:03:09 Archiving artifacts
> 05:03:58 Recording test results
> 05:04:15 Description set:
> 05:04:15 Build was marked for publishing on https://hudson.jboss.org/hudson/
> 05:04:16 Notifying upstream projects of job completion
> 05:04:16 Finished: ABORTED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19903) Build/test timeout after 5 hours
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19903?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19903:
---------------------------------------------
Left comments on https://github.com/jbosstools/jbosstools-javaee/pull/370 but in case that is missed.
Why do we suddenly have the need for adding custom repo's into our test runs ? that just seems so wrong and opening up for subtle build bugs.
> Build/test timeout after 5 hours
> --------------------------------
>
> Key: JBIDE-19903
> URL: https://issues.jboss.org/browse/JBIDE-19903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, cdi-extensions, seam2
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: screenshot.jpg, seam.ui.test.log.txt
>
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> 03:33:03 Failed tests:
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForType:29 Match not found (file - /numberguess/web/giveup.jspx name - numberGuess)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod1:44 Match not found (file - /numberguess/web/giveup.jspx name - remainingGuesses)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod2:59 Match not found (file - /numberguess/web/giveup.jspx name - possibilities)
> 03:33:03
> 03:33:03 Tests run: 86, Failures: 3, Errors: 0, Skipped: 0
> 03:33:03
> 03:33:08 [ERROR] There are test failures.
> {code}
> {code}
> 04:39:42 Running org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite230
> 04:40:10 Jun 02, 2015 4:40:10 AM org.hibernate.eclipse.HibernatePlugin start
> 04:40:10 INFO: HibernatePlugin Started
> 04:40:55 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj-ejb
> 04:40:56 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj
> 04:41:25 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:25 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj-ejb
> 04:41:27 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj
> 04:41:58 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj-ejb
> 04:41:59 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj
> 04:42:03 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:03 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoTemplLibPrj
> 04:42:11 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:11 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:14 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoLibPrj
> 04:42:26 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warTemplLibPrj
> 04:42:53 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warLibPrj
> 04:42:57 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:57 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib{code}
> {code}
> 05:02:54 [INFO] --- tycho-pack200b-plugin:0.22.0:pack (pack200-pack) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO] Pack200 packing jar /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seamfp.ui.test/target/org.jboss.tools.seamfp.ui.test-3.7.0-SNAPSHOT.jar
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (attached-p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:56 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-noauth-4.3.0.GA_CP03.zip
> 05:02:56 Build timed out (after 300 minutes). Marking the build as aborted.
> 05:02:56 Terminating xvnc.
> 05:02:57 $ vncserver -kill :43
> 05:03:07 Killing Xvnc process ID 13038
> 05:03:09 Xvnc seems to be deadlocked. Kill the process manually and then re-run
> 05:03:09 /usr/bin/vncserver -kill :43
> 05:03:09 to clean up the socket files.
> 05:03:09 Build was aborted
> 05:03:09 Archiving artifacts
> 05:03:58 Recording test results
> 05:04:15 Description set:
> 05:04:15 Build was marked for publishing on https://hudson.jboss.org/hudson/
> 05:04:16 Notifying upstream projects of job completion
> 05:04:16 Finished: ABORTED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18438) OpenShift: can complete New App Wizard without selecting gear profile
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18438?page=com.atlassian.jira.plugi... ]
Marián Labuda reassigned JBIDE-18438:
-------------------------------------
Assignee: (was: Marián Labuda)
> OpenShift: can complete New App Wizard without selecting gear profile
> ---------------------------------------------------------------------
>
> Key: JBIDE-18438
> URL: https://issues.jboss.org/browse/JBIDE-18438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
> Priority: Minor
> Fix For: LATER
>
>
> In New OpenShift Application wizard, on page where select 'Gear Profile' - this field is initially blank and user can leave it blank and still successfully complete the wizard. So it works.
> But I don't think it is a good user experience. User should not be able to move to next page until there is a value in this field. Perhaps this field should have a value to start with instead of being blank based on the users account?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-10650) EGitUtils is too large, needs to be split into smaller parts
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10650?page=com.atlassian.jira.plugi... ]
Marián Labuda reassigned JBIDE-10650:
-------------------------------------
Assignee: (was: Marián Labuda)
> EGitUtils is too large, needs to be split into smaller parts
> ------------------------------------------------------------
>
> Key: JBIDE-10650
> URL: https://issues.jboss.org/browse/JBIDE-10650
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Fix For: LATER
>
>
> EGitUtils is a collection of handy utilities to simplify tasks when dealing with EGit/JGit in OpenShift. It holds all its functionality in static methods. The class grew up to > 800 lines in its current incarnation. This is by far too large to be maintained effectively. We need to split it up into smaller parts (into commands? into several util classes?)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20100:
----------------------------------------
A-B) So far, it doesn't tell user when no connector exists. As reading the initial comment from [~jtyrrell], both story of Early-Access visibility and unexisting connector seem not so correlated. The proposal I made earlier (for which I have a first iteration almost ready) only address the 1st part.
B) I don't understand the user story here. We should always recommend people to use the newest JBDS, and if we have a version of Fuse supported against a lower version of JBDS, isn't it expected to work on the newer one too? Not doing that is IMO a big risk of confusing users, or blocking them to old release and making the amount of maintained/tested combinations grow too much for no real benefit.
C) I'll attach a screenshot when I make the PR.
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-20153) Docker server adapter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20153?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20153:
---------------------------------------------
Yes, I don't expect this to be *in* GA; but I do expect we start figuring out how to make this available.
> Docker server adapter
> ---------------------
>
> Key: JBIDE-20153
> URL: https://issues.jboss.org/browse/JBIDE-20153
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.x, 4.4.x
>
>
> I've been wondering for a time what would be the best way to integrate docker with our server adapters.
> I initially first thought it should be an additional profile to the existing local or remote profiles - but I think that option actually ends up being too limiting. To start - the server inside the docker then is assumed to always be a wildfly server; and I think for docker that is too limiting.
> Watching Eclipse Che demo at EclipseCon I realized their approach for "Runners" actually fits perfectly.
> What they do is that they don't actually have any insight into what servers they are running - they simply just have an associated DockerFile for a "runner" which they build and then run before launching.
> Once launched they then know where the server port is, where the possible debug port is, where files are mounted etc.
> So this Docker Server Adapter can be made to run *any* kind of application.
> WildFly, Tomcat, Python, even plain java apps.
> And actually it is not just a DockerFile that is associated with the run but a templated dockerfile. A file where certain variables will be replaced; like:
> {code}
> VOLUME /deployments
> ADD $app$ /deployments
> {code}
> will add the packaged app (i.e. wonka.war) into the /deployments folder and /deployments is mounted.
> And actually the /deployments can then be updated incrementally if wanted to.
> Even greater is that if we could support the same syntax and semantics of the templating we can simply reuse the templates defined by Che at https://github.com/codenvy/dockerfiles/
> You can see more complete info on what codenvy/che does http://docs.codenvy.com/user/builders-and-runners/#custom-machines
> This would cover all the usecases I can currently think of with launching docker from eclipse - but not be tied to any specific server type.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20100:
---------------------------------------------
[~mickael_istria] not a bad idea.
Two things:
A) this assumes there actually *are* Early access available - there won't be for all, so this does not cover the case of when it does not exist yet.
B) How do it tell users they can install devstudio X to get supported version?
C) I don't follow the last bullet point. about "moving setting to installation details page". Can you elaborate ?
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months