[
https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-552:
----------------------------------
So, to set this up, I need the list of URLs to use as the installation input:
{code}
# jbosstools_site_stream = master, 4.3.mars, 4.4.neon
# SET = central, earlyaccess
if [[ ${PROJECT} == "jbosstools" ]]; then
INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/bu...
elif [[ ${PROJECT} == "devstudio" ]]; then
INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbo...
fi
{code}
Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites?
We could either use the URLs you have in ide-config.properties, or to mirror what I'm
doing above, you would use sites that include ONLY the IS content (not the IS content
mixed in with JBT/JBDS via a composite site).
We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so
if you want both types of install test, we'll need TWO sets of URLs and TWO jobs.
create install tests for JBTIS/JBDSIS
-------------------------------------
Key: JBTIS-552
URL:
https://issues.jboss.org/browse/JBTIS-552
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution, target-platform
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.0.Beta1
Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP
and no conflicting install deps (eg., different IS projects w/ conflicting singleton
dependencies)
Should be based on JBT/JBDS p2director install job [1].
[1]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
Later we could also create a job that maps to the JBT/JBDS install-grinder job [2].
[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)