[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
As discussed via chat, sounds like the best option here is to depend on the composite
staging site from the previous milestone.
Thus, to override this value in trunk's parent pom:
{code}
<
jbosstools-nightly-staging-composite>http://download.jboss.org/jbossto...
{code}
We need to set this in the jobs:
{code}
-Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
{code}
And we need to couple your _trunk jobs to the upstream _stable_branch jobs instead of the
_trunk ones.
Eg.,
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.ag...
should depend on upstream
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggreg...
instead of
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/
similarly for esb:
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indig...
should depend on
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compon...
(and so on for common, jst, tests, usage components)
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL:
https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira