Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12475 Split JBoss Tools into several functional groups of components for migration to Github
  3. JBIDE-12828

migrate JBT & JBDS jobs to use new github repos

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • 4.0.0.CR1
    • 4.0.0.Beta1
    • build, updatesite
    • None

    Description

      For first the trunk jobs, then AFTER Beta1 is released the stable_branch jobs, the following must be done.

      Work to start Oct 22

      • [Max] For every repo moved - svn delete in trunk, put Readme with pointer.
      • [Nick] Open branch 4.0.0.Beta1 for writes, keep trunk locked down. [DONE]
      • [Nick] create root poms for chunk repos; for N:1 "chunk" repos (base, server, javaee, central): merge jbosstools-base/[as,archives,jmx]/site/* into jbosstools-base/site/* - one site w/ all features on it [DONE]
      • [Nick] merge stuff from the above temp-* repos into the new actual repos [DONE]
      • [Nick/Mickael] switch trunk jobs to source from github instead of svn [DONE]
      • [Nick] make sure all jobs (including rsync for download.jboss.org) are updated to fetch from git instead of svn [DONE]
      • [Nick/Mickael] make sure all refs to promote.sh, jbosstools-cleanup.sh, promote.sh are pointed at github instead of svn
      • for 1:1 individual repos: no change needed for ./site/ folder [DONE]

      (see also http://ether-man.rhcloud.com/p/build.next )

      Attachments

        Issue Links

          is blocked by

          Sub-task - The sub-task of the issue JBIDE-12944 migrate installer tests to use new directory structure (git) and new published sites; ensure jobs are doing what they say they are

          • 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.
          • Resolved

          Sub-task - The sub-task of the issue JBIDE-12945 Migrate jbosstools-docs-nightly job to use git sources instead of svn

          • 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

          Sub-task - The sub-task of the issue JBIDE-12946 add code coverage support to jbosstools-4.0_trunk.tests; make job yellow when tests fail, not red

          • 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

          Sub-task - The sub-task of the issue JBIDE-12947 test failure in org.jboss.tools.drools.ui.bot.test causes soa tooling tests site to fail to build

          • 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-12993 Cleanup/create plain checkout.sh script for jbosstools repos from github

          • 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-12986 due to refactoring of tests module & migration to git, installer tests broken

          • 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-13032 update contributor guide for github use

          • 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-12925 missing empty folders after migration of hibernatetools (svn) to jbosstools-hibernate (git)

          • 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. JBIDE-12926 missing empty folders after migration of esb (svn) to jbosstools-esb (git)

          • 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-12914 Use Tycho 0.16

          • 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:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: