[JBoss JIRA] (JBDS-4302) Component should declare dependencies in requirements-.json
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4302:
-----------------------------------
Summary: Component should declare dependencies in requirements-.json
Key: JBDS-4302
URL: https://issues.jboss.org/browse/JBDS-4302
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.4.0.AM2
Reporter: Denis Golovin
Current implementation for dependencies validation is hardcoded and was originally implemented for static set of components. It should part of components configuration in requirements.json file.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-23882:
------------------------------------
[~nickboldt][~lvalach] - yes - the siteUrl should be pulled from jboss.discovery.earlyaccess.site.integration-stack.url or jboss.discovery.site.integration-stack.url in ide-config.properties. Note that the EA discovery composite has child size = 0 (no more EA).
> Automate test of installation of software from Red Hat Central into devstudio RPM
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23882
> URL: https://issues.jboss.org/browse/JBIDE-23882
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Environment: RHEL7, devstudio RPM
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.4.4.AM2
>
>
> We need to catch problems like in JBDS-4263.
> [~lvalach] said: {quote}
> I think I should automate test of installation from Central, because this procedure is quite time consuming.
> {quote}
> [~nickboldt] said: {quote}
> before you do that might want to look at the existing automated tests we have:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g....
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p....
> of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root
> maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally
> so ... partial automation
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-23882:
--------------------------------------
Sure, thanks for feedback. It shouldn't be problem to read siteUrl from ide-config.properties. I will probably have to put Devstudio version as new parameter (to be able to find tripe variable|devstudio|version).
Just to be clean (if you think that there is a mistake in plugin.xml), URLs of discovery sites are not hardcoded, there are variables like these:
{code}
grep 'siteUrl=' ./all_plugin.xml | sort | uniq #all_plugin.xml = Concatenation of all plugin.xml which has been found in devstudio-directory.xml
siteUrl="https://dl-ssl.google.com/android/eclipse/">
siteUrl="http://update.zeroturnaround.com/update-site-jboss/">
siteUrl="${jboss.discovery.earlyaccess.site.url}">
siteUrl="${jboss.discovery.site.integration-stack.url}"
siteUrl="${jboss.discovery.site.url}">
{code}
> Automate test of installation of software from Red Hat Central into devstudio RPM
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23882
> URL: https://issues.jboss.org/browse/JBIDE-23882
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Environment: RHEL7, devstudio RPM
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.4.4.AM1
>
>
> We need to catch problems like in JBDS-4263.
> [~lvalach] said: {quote}
> I think I should automate test of installation from Central, because this procedure is quite time consuming.
> {quote}
> [~nickboldt] said: {quote}
> before you do that might want to look at the existing automated tests we have:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g....
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p....
> of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root
> maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally
> so ... partial automation
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years