[JBoss JIRA] (JBIDE-26962) Create job DSL template for launching Jenkinsfile
by Jan Richter (Jira)
Jan Richter created JBIDE-26962:
-----------------------------------
Summary: Create job DSL template for launching Jenkinsfile
Key: JBIDE-26962
URL: https://issues.jboss.org/browse/JBIDE-26962
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Reporter: Jan Richter
Assignee: Jan Richter
Nearly all adapters projects use jenkinsfiles to define their builds. Create a template in job DSL that would allow easy definition of such jobs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26887) Installing containers tools on RHEL 8.1
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26887?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26887:
-----------------------------------------
Issue will be fixed in Ansible.
> Installing containers tools on RHEL 8.1
> ---------------------------------------
>
> Key: JBIDE-26887
> URL: https://issues.jboss.org/browse/JBIDE-26887
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> *Info:*
> When provisioning scripts are running with labels "jbds docker" to provision RHEL 8+, the script automatically install podman instead docker (see the *label/rhel/docker.sh*). BUT THE SCRIPT IS STILL FAILING - IT NEEDS TO BE INVESTIGATED AND FIXED.
> *See the log with assert from Jenkins:*
> {code:java}
> [branch_rhel8-1-x64-jbds] Writing manifest to image destination
> [branch_rhel8-1-x64-jbds] Storing signatures
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] test_talk_to_the_outer_world
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] ASSERT:Unable to ping remote hosts from container: PING 10.38.5.26 (10.38.5.26) 56(84) bytes of data.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] --- 10.38.5.26 ping statistics ---
> [branch_rhel8-1-x64-jbds] 1 packets transmitted, 0 received, 100% packet loss, time 0ms
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] c2c03a296d2329a4f3ab72a7bf38b78a8a80108204d326b0139d6af700e152d1
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] Ran 4 tests.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] FAILED (failures=1)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26903) Several central.itests tests are failing (ArchetypesTest, BasicTests, DnDTest)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26903?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26903:
------------------------------------
Description:
h2. Reason - central has changed a little bit over time:
- link "Get involved" (CAT button) has been removed (https://issues.jboss.org/browse/JBIDE-26817)
- present archetypes has changed (same has been removed)
- DnD link is not working
- several others
- examples needs to run on Java 8 (add JRE 8 when running on Java 11)
was:
h2. Reason - central has changed a little bit over time:
- link "Get involved" (CAT button) has been removed (https://issues.jboss.org/browse/JBIDE-26817)
- present archetypes has changed (same has been removed)
- DnD link is not working
- several others
> Several central.itests tests are failing (ArchetypesTest, BasicTests, DnDTest)
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26903
> URL: https://issues.jboss.org/browse/JBIDE-26903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.13.0.AM1
> Environment: All OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Attachments: failing tests.png, new_central.png, old_central.png
>
>
> h2. Reason - central has changed a little bit over time:
> - link "Get involved" (CAT button) has been removed (https://issues.jboss.org/browse/JBIDE-26817)
> - present archetypes has changed (same has been removed)
> - DnD link is not working
> - several others
> - examples needs to run on Java 8 (add JRE 8 when running on Java 11)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26913:
----------------------------------
Fix Version/s: 4.14.0.AM1
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.14.0.AM1
>
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
> - fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
> - fix the failing 'testModeAnnotated' and 'testWithoutBeansXml' BeansXMLDiscoveryModesTestCDI11 tests (CDI 1.1)
> - fix the failing 'testValidationOfBeanDiscoveryInExplicitArchives' BeanDiscoveryInExplicitArchivesTestCDI11 test (CDI 1.1)
> - fix the failing 'testValidationOfBeanDiscoveryInImplicitArchives' BeanDiscoveryInImplicitArchivesTestCDI11 test (CDI 1.1)
> - fix the failing 'testBuildInContextsWarnings' WeldBuiltInContextsTestCDI11 test (CDI 1.1)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26787?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26787:
----------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019, devex #173 Oct 2019, devex #176 Nov/Dec 2019)
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.jboss.org/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months