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

migrate Fuse Tools builds to JBT infrastructure/process

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • 4.30.x
    • 4.5.0.AM1
    • build, fusetools, updatesite
    • None
    • devex #132 May 2017, devex #139 October 2017
    • 21

    Attachments

      Issue Links

        is blocked by

        Sub-task - The sub-task of the issue JBIDE-24765 implement workaround for blocked branches when we need to update parent poms automatically

        • 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

        Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FUSETOOLS-2264 Switch master branch to Oxygen TP

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

        Bug - A problem that impairs or prevents the functions of the product. FUSETOOLS-2353 Installation of JBoss Fuse Tools results in conflicting dependency while installing from Central

        • 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. FUSETOOLS-2421 RemoteDebugWhenEditingRoutesFromJMXNavigatorIT.testRemoteDebugScenario test is failing on master with job on DevTools CCI

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

        Task - Represents a small unit of work that is not end-user facing. FUSETOOLS-2265 Create a branch for 9.2 based on Oxygen

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

        Task - Represents a small unit of work that is not end-user facing. FUSETOOLS-2266 Switch master branch target platform to Oxygen

        • 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

        Task - Represents a small unit of work that is not end-user facing. FUSETOOLS-2420 SonarCloud.io code coverage is no more reported correctly

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBIDE-23317 Create and use Oxygen.0.M7 target platform

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

        Task - Represents a small unit of work that is not end-user facing. JBIDE-24746 Move Integration Stack-based Target Platform to JBoss Tools-based Target Platform for SAP Tooling

        • 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

        Task - Represents a small unit of work that is not end-user facing. FUSETOOLS-2468 Include Fuse Tooling in listing of available projects in jbosstools-devdoc

        • 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

        Task - Represents a small unit of work that is not end-user facing. JBIDE-24703 Remove Integration Stack related target platform from Fuse Tooling codebase

        • 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. FUSETOOLS-1263 Move Fuse Tooling sources into JBoss organization at 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBIDE-24525 Create and use Oxygen.0.RC4 target platform

        • 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
        1.
        		 add fuse tools features to JBT core, coretests, integration-tests update sites (as appropriate) Sub-task Closed Major Nick Boldt
        2.
        		 Add fuse tooling into devstudio feature(s) Sub-task Closed Major Nick Boldt
        3.
        		 Add Fuse Tooling dependencies to JBT/devstudio Oxygen-based TPs Sub-task Closed Major Lars Heinemann
        4.
        		 Remove Fuse Tooling dependencies from Integration Stack target platforms Sub-task Closed Major Paul Leacu (Inactive)
        5.
        		 Document process for async Fuse Tools releases Sub-task Closed Major Nick Boldt
        6.
        		 Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore) Sub-task Closed Major Lars Heinemann
        7.
        		 Ensure SAP tooling is available from within JBT/devstudio Sub-task Closed Major Nick Boldt
        8.
        		 Publish Fuse Tools tests (with sources?) to JBT Core Tests site Sub-task Closed Major Lars Heinemann
        9.
        		 migrate Fuse Tools jobs under Devstudio view in Central CI? Sub-task Closed Major Lars Heinemann
        10.
        		 migrate Fuse central connector from IS to JBT/devstudio Central Sub-task Closed Major Nick Boldt
        11.
        		 update readme & root pom for Fuse Extras / SAP tooling to fix license, copyright Sub-task Closed Major Nick Boldt
        12.
        		 add component = fusetools and fuse-extras into the scripts that nag re: N&N, branching, tagging, root poms, etc. Sub-task Closed Major Nick Boldt
        13.
        		 migrate fusetools job from fusesource jenkins to dev-platform jenkins Sub-task Closed Major Nick Boldt
        14.
        		 verify correct copyright dates, terms and licenses Sub-task Closed Major Nick Boldt
        15.
        		 ensure Fuse Tools team knows where the devdocs are and has read them Sub-task Open Major Unassigned
        16.
        		 Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools Sub-task Closed Major Unassigned
        17.
        		 Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace Sub-task Open Major Jeff MAURY
        18.
        		 remove discovery site references to old/redundant sites Sub-task Closed Major Lars Heinemann
        19.
        		 migrate PR build jobs on fusesource jenkins to dev-platform Sub-task Closed Major Jeff MAURY
        20.
        		 Include Fuse CI job update for job configuration update Sub-task Open Major Jeff MAURY

        Activity

          People

            Unassigned Unassigned
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: