[jbosstools-issues] [JBoss JIRA] (JBIDE-21145) Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21145:
------------------------------------

{quote}why keeping the composite builds?{quote}

In addition to it being a handy way to orchestrate running both the JBT core and core-tests jobs in parallel, it also verifies that the contents of the composite can be co-installed.

Sure, we have additional tests that do install tests downstream of the JBT aggregate build, but this is the *first-line verification* that we don't have some incomplete change (eg., an API change in Base that hasn't been absorbed by Server, or a change to JST which points to the wrong version of AngularJS).

And while it can be annoying sometimes when the job fails, it's better than relying on the install-grinder test, which is often broken for months w/o anyone repairing it. A 3-day problem is way better than a 30-day one, since people SEE it and complain. IMHO, the system is working because we blocked the build when a test failed. 

Isn't that how test-driven dev is supposed to work? :D

> Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-21145
>                 URL: https://issues.jboss.org/browse/JBIDE-21145
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
>            Reporter: Pavol Srna
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> We have often seen old artifacts on nightly sites (mars and neon too). 
> It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds.
> [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/lastBuild/console
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_4.3.mars/lastBuild/console
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/ (latest build shows: "Nov 27, 2015 6:15 AM NOT ​PUBLISHED: ​​UNCHANGED")
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_4.3.mars/ (latest build shows: "Nov 27, 2015 3:43 AM NOT ​PUBLISHED: ​​UNCHANGED")
> Please investigate.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)