[
https://issues.jboss.org/browse/JBIDE-11495?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11495:
---------------------------------------------
I think this is part of rethinking how we build the various stacks (big and small). The
suggested notes above is following the model of "lets just use the latest and hope
for best" approach; its great because all the latest greatest build together but the
downside is that you never spot if you actually broke anyone and you are most likely
rebuilding unnecessarily.
JBTIS doesn't even do any of this - they choose a fixed version of JBT core to use and
use that for release.
I would say issue is about making it easy to setup hudson builds for your component builds
and document which jobs to use.
Improve ability to configure dependent hudson jobs and provide
accessable documentation
---------------------------------------------------------------------------------------
Key: JBIDE-11495
URL:
https://issues.jboss.org/browse/JBIDE-11495
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Barry LaFond
Assignee: Douglas Palmer
Fix For: 4.0.x
SOA decoupling has elevated the need to have more configurable control over upstream and
downstream dependencies.
Notes from Nick:
* a number of jobs are now set to build only when triggered by upstream, but SOA stuff is
not as well handled
* ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should
use Parameterized Trigger to cause downstream to fire
* you can also ensure that you're building against a stable aggregate using an
override like the one I've set up for SOA Tooling aggregate...
* in your maven invocation, under Properties, you can do this: # use latest upstream
nightly Core update site instead of "wild components" in the composite staging
site
jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
* that way you pull from the aggregate (updates weekly) instead of the composite (updates
every time a component respins)
* means if you depended on something like
tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry
about getting incompatible pieces
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira