Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-21145

Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 4.4.0.Alpha1
    • 4.3.1.Beta1, 4.4.0.Alpha1
    • build
    • None

    Description

      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!

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-21215 IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBIDE-21169 Add openshift.cdk feature into JBT Core update site

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16970 create mechanism to verify that nightly build is different from previous milestone

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              psrna Pavol Srna
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: