[
https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin....
]
Lukáš Valach edited comment on JBDS-4263 at 2/27/17 9:23 AM:
-------------------------------------------------------------
I reran test against recommended update sites.
[#37|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/37/]
Devstudio: 10.4-0.20170227.0853.el7
Update site:
https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e...
Failed tests:
*
[
PMD|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]
** There is different problem than in #31 and #32, nothing about log4j.
** [^rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt]
{code}
Caused by: java.lang.ClassNotFoundException: net.sourceforge.pmd.RuleSetNotFoundException
cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057
{code}
[#38|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/38/]
Devstudio: 10.4-0.20170227.0853.el7
Update site:
https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1...
Failed tests:
* JBoss_Business_Process_and_Rules_Development (Installation failed. The installable unit
org.jboss.tools.bpel.feature.feature.group has not been found.)
* JBoss_Data_Virtualization_Development (Installation failed)
* JBoss_Developer_Studio_Integration_Stack_Early_Access_Components (Installation failed)
* JBoss_Fuse_Development (Installation failed)
* JBoss_Integration_and_SOA_Development (Installation failed)
* PMD (similar error like in #37)
I have to look why the installation failed.
----
I created second job that runs against the Integration Stack
[
rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.en...].
Which update site should I use for testing against IS?
[
Snapshots|https://devstudio.redhat.com/10.0/snapshots/updates/integration...]
or
[
stable|https://devstudio.redhat.com/10.0/staging/updates/integration-stac...
{quote}
3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging \[2\] and
stable \[3\] sites?
{quote}
Sure, I can do that, but just to be clear... Why do you want me to test Devstudio RPM
10.4 against stable/staged 10.3 version which is older than last snapshot? Do you want me
to use staging URL as default or only use it one times?
was (Author: lvalach):
I reran test against recommended update sites.
[#37|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/37/]
Devstudio: 10.4-0.20170227.0853.el7
Update site:
https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e...
Failed tests:
*
[
PMD|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]
** There is different problem than in #31 and #32, nothing about log4j.
** [^rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt]
{code}
Caused by: java.lang.ClassNotFoundException: net.sourceforge.pmd.RuleSetNotFoundException
cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057
{code}
[#38|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/38/]
Devstudio: 10.4-0.20170227.0853.el7
Update site:
https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1...
Failed tests:
* JBoss_Business_Process_and_Rules_Development (Installation failed. The installable unit
org.jboss.tools.bpel.feature.feature.group has not been found.)
* JBoss_Data_Virtualization_Development (Installation failed)
* JBoss_Developer_Studio_Integration_Stack_Early_Access_Components (Installation failed)
* JBoss_Fuse_Development (Installation failed)
* JBoss_Integration_and_SOA_Development (Installation failed)
* PMD (similar error like in #37)
I have to look why the installation failed.
----
I created second job that runs against the Integration Stack
[
rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.en...].
Which update site should I use for testing against IS?
[
Snapshots|https://devstudio.redhat.com/10.0/snapshots/updates/integration...]
or
[
stable|https://devstudio.redhat.com/10.0/staging/updates/integration-stac...
{quote}
3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging \[2\] and
stable \[3\] sites?
{quote}
Sure, I can do that, but just to be clear... Why do you want me to test Devstudio RPM
10.4 against stable/staged 10.3 version which is older than last snapshot? Do you want me
to use staging URL as default or only use it one times?
Why there isn't 10.3.0.GA folder?
https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/
Problems after install from Red Hat Central into
rh-eclipse46-devstudio
-----------------------------------------------------------------------
Key: JBDS-4263
URL:
https://issues.jboss.org/browse/JBDS-4263
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 10.3.0.AM2
Reporter: Nick Boldt
Assignee: Lukáš Valach
Fix For: 10.4.0.AM1
Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip,
build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt,
rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt,
rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
The installation of software from Red Hat Central causes errors in the log. Some
functionality may be broken. We have to test installation of all the stuff from the
central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)