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

Only rely on rsync to publish new aggregate (remove other comparators and checks)

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Major
    • 4.3.0.Beta1
    • None
    • build
    • None
    • Sprint #2 April 2015

    Description

      Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not.

      It's more or less just a matter of scripting

      p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot
if [[ -s p2diff_snapshot ]]; then
   ./publish.sh
fi

      Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain)

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-18662 use getProjectSHAs.sh to control when to run aggregate builds, instead of doing composite site installs

          • 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

          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-13835 Improve publish script (split? Move to maven?)

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. JBIDE-19072 Improve plugin version auditing & how we build

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3208 reorg/refactor directories for consistency across JBT/JBDS

          • 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

          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

              mistria@redhat.com Mickael Istria
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: