[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

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-21145:
---------------------------------------

I current state even if we just stop doing checks if upload required (which I think is fine, lets do this) and start aggregating latest the greatest *aggregation build result* is not going to be reliable. Or better say it is not going to be reliable all the time without attention from involved parties. Composite install job would not be reliable by transition, because with all the JBT components built without synchronization aggregation build picks up random combination of JBossTools components from nightly p2 repositories.

I would stop discussing build improvements in this issue and fix actual problem stated in summary by disabling check "if upload required" and started aggregating when it is triggered by downstream trigger.

p2diff IMO can be used until we have .qualifier generated every build based on time stamp. 

Then we can see what we can do to make actual aggreagted build results reliable.








> 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)