Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-3208

reorg/refactor directories for consistency across JBT/JBDS

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.Beta1
    • 9.0.0.Alpha1
    • build
    • None
    • Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015
    • NEW

    Description

      Be it resolved - we should reorg directories for consistency across JBT/JBDS:

      Latest suggestion:

      • /{mars,9.0}/
        • /{snapshots,staging,development,stable}/
          • /updates/
            • /{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
              • /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.*, 4.50.*...>/
          • /builds/
            • /<job-name>/
              • / {<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}

                /

      —

      Older idea:

      <download.jboss.org,devstudio.redhat.com>
      <earlyaccess,updates,discovery>/<mars,9.0>
       /snapshots [replace nightly]
       /staging [rename content for QE, moves to development when approved]
       /development
       /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
      drop /integration (not used)
    builds/<jobname>/<buildid>
    builds/<jobname>/composite*.xml for last N builds
    targetplatforms/<type>/<version>

      Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112

      This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.

      [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.luna/
      [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-composite-install_4.2.luna/

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-18921 release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-18833 luna nightly are not being updated preventing QE to do easy testing of committed code

          • 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-3163 change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

          • 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

          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-18742 Only rely on rsync to publish new aggregate (remove other comparators and checks)

          • 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-18846 create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-14610 Design http://download.jboss.org/jbosstools structure

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-18914 Spring cleaning for /targetplatforms/ folder

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19018 JBT Central Discovery staging site contains early access child site in its composite*.xml

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3421 Update site lists its files in upper left corner

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3422 Links for offline install zips on update site are dead

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19758 when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-20141 Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3423 JBDS update site has blue JBT branding instead of red JBDS branding

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBIDE-19608 For JBIDE 4.3.0.Alpha2: Code Freeze + Branch

          • 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-18772 Include publish steps in pom files

          • Critical - To be worked on immediately following BLOCKER issues.
          • 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) JBDS-3191 Improve the way we switch between development and GA

          • 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
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: