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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-21145:
---------------------------------------------

"helping to orchestrate when to build them" == being part of the context that generates the aggregate updatesite.

and I just don't grok why you think the composite install will not need to do the same as the aggregate build, i.e. *download* the proper artifacts to perform its task. The aggregate will even download *less* to make the build than a full composite install will have to.

Not sure why you say that michael and I's explicit suggestion on how to do the aggregate builds are not proposals for a better solution for having a more reliable and simpler aggregation. none of this have been about scheduling times. The scheduling times are fine. its the reliability and fragility of the setup we were trying to fix.

> Composite 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
>
>         Attachments: jbide21145-conflict-between-tp-and-central.png
>
>
> 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)