[jbosstools-issues] [JBoss JIRA] (JBIDE-11495) Improve ability to configure dependent hudson jobs and provide accessable documentation

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790214#comment-12790214 ] 

Mickael Istria commented on JBIDE-11495:
----------------------------------------

The 2 first points of the request already apply to JBT CI jobs (check SCM and cascade downstream)

Point #3 makes no sense for JBT core because we do want to test all the latest build together since it makes feedback much faster. Using aggregate to build JBT core would reduce the amount of errors spotted, which is the contrary of CI principles (find as many errors as possible, as soon as possible).

Point #4 is already covered by using the following profile: "-P jbosstools-staging-aggregate" https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L455


So overall, I think this request doesn't apply to JBT core. IMO, this request should be either rejected, or moved to JBTIS.
                
> 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/updates/nightly/core/trunk/
> * 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