[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

Mickael Istria (JIRA) issues at jboss.org
Tue Dec 1 02:15:01 EST 2015


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

Mickael Istria edited comment on JBIDE-21145 at 12/1/15 2:14 AM:
-----------------------------------------------------------------

In order to bypass this failing orchestration job, one can still trigger the following jobs manually: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_4.3.mars/ . On completion, that will trigger JBDS build, so there is nothing else to do than triggering this one and waiting for completion.
On https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_4.3.mars/ , I restored to downstream trigger of jbosstools-composite-install that will cascade aggregator and then product without additional effort. I don't know why this downstream trigger was removed.
I trigger a new build for openshift, that should be available in Ci builds automatically upon completion of the chain.

Looking at the big picture, I still believe the the composite-install job, which is supposed to allow minor optimizations (avoiding reaggregating when there was no change) actually save little time/CPU resources compared to always triggering aggregation. Moreover, it has often been identify as a source of issue in the build chain.
Since, the composite-install job performs an install operation which has similar cost to the one of pure-aggregation, I believe it would be more interesting to always aggragate content and to conditionally *publish* the aggregated repository depending on whether there were change (p2diff can check that). Once again, we're back to JBIDE-15388



was (Author: mickael_istria):
In order to bypass this failing orchestration job, one can still trigger the following jobs manually: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_4.3.mars/ . On completion, that will trigger JBDS build, so there is nothing else to do than triggering this one and waiting for completion.
On https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_4.3.mars/ , I restored to downstream trigger of jbosstools-composite-install that will cascade aggregator and then product without additional effort. I don't know why this downstream trigger was removed.
I trigger a new build for openshift, that should be available in Ci builds automatically upon completion of the chain.


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



More information about the jbosstools-issues mailing list