[JBoss JIRA] (JBIDE-23668) Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23668?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-23668:
------------------------------------------
[~nickboldt] we are fine with adding <build> part as a profile
[~jeffmaury] if you want to be able to run IT tests in jenkins against devstudio than this config is needed. Anybody can run them against "current installation" but that does not give QE any value. We need to be able to run tests in jenkins against devstudio and on all supported platforms.
> Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23668
> URL: https://issues.jboss.org/browse/JBIDE-23668
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, integration-tests
> Reporter: Pavol Srna
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
>
> This configuration needs to be moved from [1] to build/parent/pom.xml
> {code}
> <properties>
> <surefire.timeout>7200</surefire.timeout>
> <integrationTestsSystemProperties>-Dusage_reporting_enabled=false</integrationTestsSystemProperties>
> <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> <testProduct>com.jboss.devstudio.core.product</testProduct>
> </properties>
> {code}
> {code}
> <profile>
> <id>mac-installPath</id>
> <activation>
> <os>
> <family>mac</family>
> </os>
> </activation>
> <properties>
> <test.installPath.OSX>/devstudio.app/Contents/Eclipse/</test.installPath.OSX>
> </properties>
> </profile>
> <profile>
> <id>install-base</id>
> <activation>
> <property>
> <name>test.installBase</name>
> </property>
> </activation>
> <properties>
> <test.installPath>${test.installBase}${test.installPath.OSX}</test.installPath>
> </properties>
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <work>${test.installPath}</work>
> <product>${testProduct}</product>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> <profile>
> <!-- Workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=388084 -->
> <id>osx</id>
> <activation>
> <os>
> <family>mac</family>
> </os>
> </activation>
> <properties>
> <platformSystemProperties> -XstartOnFirstThread </platformSystemProperties>
> </properties>
> </profile>
> <profile>
> <id>download-devstudio</id>
> <activation>
> <property>
> <name>!test.installBase</name>
> </property>
> </activation>
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <product>${testProduct}</product>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>target-platform-configuration</artifactId>
> <configuration>
> <dependency-resolution>
> <extraRequirements>
> <requirement>
> <type>p2-installable-unit</type>
> <id>com.jboss.devstudio.core.feature.feature.group</id>
> <versionRange>0.0.0</versionRange>
> </requirement>
> </extraRequirements>
> </dependency-resolution>
> </configuration>
> </plugin>
> </plugins>
> </build>
> <repositories>
> <repository>
> <id>devstudio-repo</id>
> <name>devstudio-repo</name>
> <layout>p2</layout>
> <url>${devstudio.repository}</url>
> </repository>
> </repositories>
> </profile>
> {code}
> {code}
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <useUIThread>false</useUIThread>
> <appArgLine>-pluginCustomization ${basedir}/../pluginCustomization.ini</appArgLine>
> <systemProperties>
> <org.eclipse.update.reconcile>false</org.eclipse.update.reconcile>
> <!-- JBDS-4077 this should be passed in from Jenkins or commandline -->
> <tpc.version>${TARGET_PLATFORM_VERSION_MAX}</tpc.version>
> </systemProperties>
> <explodedBundles>
> <bundle>org.mozilla.xulrunner.cocoa.macosx</bundle>
> <bundle>org.mozilla.xulrunner.gtk.linux.x86</bundle>
> <bundle>org.mozilla.xulrunner.gtk.linux.x86_64</bundle>
> <bundle>org.mozilla.xulrunner.win32.win32.x86</bundle>
> </explodedBundles>
> </configuration>
> </plugin>
> </plugins>
> </build>
> {code}
> We need to find out how to deal with pluginCustomization.ini [2]. Download from somewhere?
> [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
> [2] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23665) Create Windup tooling connector for JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23665 at 1/5/17 9:23 AM:
------------------------------------------------------------
You've set a fixversion of 4.4.3.AM1 (which I changed to AM2 as code freeze for AM1 is today and this change is too big to get done today w/o proper reviews and approvals).
Also, what's the current state of the Windup tooling? Does the windup server run in a separate thread or is it coupled to the Eclipse thread (thus causing crashes and OOM problems) ? Please advise. cc: [~jeffmaury] [~rob.stryker] [~koen.aers]
was (Author: nickboldt):
You've set a fixversion of 4.4.3.AM1 (which I changed to AM2 as code freeze for AM1 is today and this change is too big to get done today w/o proper reviews and approvals).
But you requested this change be done for JBT 4.3. So, I'm confused. Do you want this for our Mars-based release from last year, or the current development stream for this year? Which version of Eclipse are you using to develop Windup tooling? Does it run on Mars and Neon too? Or just Neon?
Also, what's the current state of the Windup tooling? Does the windup server run in a separate thread or is it coupled to the Eclipse thread (thus causing crashes and OOM problems) ? Please advise. cc: [~jeffmaury] [~rob.stryker] [~koen.aers]
> Create Windup tooling connector for JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-23665
> URL: https://issues.jboss.org/browse/JBIDE-23665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central-update
> Affects Versions: 4.4.3.AM1
> Reporter: John Steele
> Assignee: John Steele
> Fix For: 4.4.3.AM2
>
>
> For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23665) Create Windup tooling connector for JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23665:
-------------------------------
Description: For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector. (was: For JBT and JBDS (I'm not sure which versions, maybe JBT 4.3 and JBDS 9), Windup will be available from JBoss Central. The Central discovery catalog needs to list it as a new connector.)
> Create Windup tooling connector for JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-23665
> URL: https://issues.jboss.org/browse/JBIDE-23665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.4.3.AM1
> Reporter: John Steele
> Assignee: John Steele
> Fix For: 4.4.3.AM2
>
>
> For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4204 at 1/5/17 9:18 AM:
----------------------------------------------------------
[~supriya.bharadwaj] got your ping on Hipchat but you provided no information about the status of this being documented in the release notes / known issues. Had a look at https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... and see no comment about Wayland, Fedora 25, or JBDS-4204.
Then I discovered RHDEVDOCS-353 so I see the plan is to doc this for 10.3, not to add it to 10.2 docs.
was (Author: nickboldt):
[~supriya.bharadwaj] got your ping on Hipchat but you provided no information about the status of this being documented in the release notes / known issues. Had a look at https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... and see no comment about Wayland, Fedora 25, or JBDS-4204.
So... I guess this still needs documenting?
> Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland
> -------------------------------------------------------------------------------------------
>
> Key: JBDS-4204
> URL: https://issues.jboss.org/browse/JBDS-4204
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 10.1.0.GA
> Environment: FC25, wayland
> Reporter: cube 00
> Assignee: Snjezana Peco
> Labels: upstream
> Fix For: 10.3.0.AM1
>
> Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip
>
>
> The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either.
> Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23668) Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23668?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23668:
------------------------------------
The general pattern about moving those tests into component repo is that:
* they should run against the current installation
* they should follow existing test configurations
* if they run for a longer period, they should be moved to a specific common profile
*
Based on that, I think the only relevant property to be moved is integrationTestsSystemProperties and may be merged with common test properties.
The surefire timeout must be part of this specific common profile
Idem for the profiles because they seem to be linked to tests running with DevStudio which is not our case anymore
> Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23668
> URL: https://issues.jboss.org/browse/JBIDE-23668
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, integration-tests
> Reporter: Pavol Srna
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
>
> This configuration needs to be moved from [1] to build/parent/pom.xml
> {code}
> <properties>
> <surefire.timeout>7200</surefire.timeout>
> <integrationTestsSystemProperties>-Dusage_reporting_enabled=false</integrationTestsSystemProperties>
> <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> <testProduct>com.jboss.devstudio.core.product</testProduct>
> </properties>
> {code}
> {code}
> <profile>
> <id>mac-installPath</id>
> <activation>
> <os>
> <family>mac</family>
> </os>
> </activation>
> <properties>
> <test.installPath.OSX>/devstudio.app/Contents/Eclipse/</test.installPath.OSX>
> </properties>
> </profile>
> <profile>
> <id>install-base</id>
> <activation>
> <property>
> <name>test.installBase</name>
> </property>
> </activation>
> <properties>
> <test.installPath>${test.installBase}${test.installPath.OSX}</test.installPath>
> </properties>
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <work>${test.installPath}</work>
> <product>${testProduct}</product>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> <profile>
> <!-- Workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=388084 -->
> <id>osx</id>
> <activation>
> <os>
> <family>mac</family>
> </os>
> </activation>
> <properties>
> <platformSystemProperties> -XstartOnFirstThread </platformSystemProperties>
> </properties>
> </profile>
> <profile>
> <id>download-devstudio</id>
> <activation>
> <property>
> <name>!test.installBase</name>
> </property>
> </activation>
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <product>${testProduct}</product>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>target-platform-configuration</artifactId>
> <configuration>
> <dependency-resolution>
> <extraRequirements>
> <requirement>
> <type>p2-installable-unit</type>
> <id>com.jboss.devstudio.core.feature.feature.group</id>
> <versionRange>0.0.0</versionRange>
> </requirement>
> </extraRequirements>
> </dependency-resolution>
> </configuration>
> </plugin>
> </plugins>
> </build>
> <repositories>
> <repository>
> <id>devstudio-repo</id>
> <name>devstudio-repo</name>
> <layout>p2</layout>
> <url>${devstudio.repository}</url>
> </repository>
> </repositories>
> </profile>
> {code}
> {code}
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> <useUIThread>false</useUIThread>
> <appArgLine>-pluginCustomization ${basedir}/../pluginCustomization.ini</appArgLine>
> <systemProperties>
> <org.eclipse.update.reconcile>false</org.eclipse.update.reconcile>
> <!-- JBDS-4077 this should be passed in from Jenkins or commandline -->
> <tpc.version>${TARGET_PLATFORM_VERSION_MAX}</tpc.version>
> </systemProperties>
> <explodedBundles>
> <bundle>org.mozilla.xulrunner.cocoa.macosx</bundle>
> <bundle>org.mozilla.xulrunner.gtk.linux.x86</bundle>
> <bundle>org.mozilla.xulrunner.gtk.linux.x86_64</bundle>
> <bundle>org.mozilla.xulrunner.win32.win32.x86</bundle>
> </explodedBundles>
> </configuration>
> </plugin>
> </plugins>
> </build>
> {code}
> We need to find out how to deal with pluginCustomization.ini [2]. Download from somewhere?
> [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
> [2] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months