Bigtop
  1. Bigtop
  2. BIGTOP-1201

Enhance (gradleize) the build to ease development, deployment; abstract implementation

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7.0
    • Fix Version/s: 0.8.0
    • Component/s: build
    • Labels:
      None

      Description

      As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:

      • build Bigtop framework
      • build and install target artifacts (packages, jars)
      • prepared to develop or test targeted stack
      • enforce all per-requisites consistently
      • coordinate version updates
      • produce documentation
      • <add more here>

      There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can

      • short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
      • long term: consolidate all bits of the framework in one comprehensive build management system

      An apparent requirements of the solution:

      • it needs to play well with JVM stack
      • it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
      • don't limit our ability to replace (if needed) various bits of current framework with something more uniform.

      Behold, I propose Gradle.

      1. BIGTOP-1201.patch
        29 kB
        Konstantin Boudnik
      2. BIGTOP-1201.patch
        28 kB
        Konstantin Boudnik
      3. BIGTOP-1201.patch
        28 kB
        Konstantin Boudnik
      4. BIGTOP-1201.patch
        27 kB
        Konstantin Boudnik
      5. BIGTOP-1201.patch
        26 kB
        Konstantin Boudnik
      6. BIGTOP-1201.patch
        23 kB
        Konstantin Boudnik
      7. BIGTOP-1201.patch
        26 kB
        Konstantin Boudnik
      8. BIGTOP-1201.patch
        20 kB
        Konstantin Boudnik
      9. BIGTOP-1201.patch
        18 kB
        Konstantin Boudnik
      10. BIGTOP-1201.patch
        18 kB
        Konstantin Boudnik
      11. BIGTOP-1201.patch
        17 kB
        Konstantin Boudnik
      12. BIGTOP-1201.patch
        17 kB
        Konstantin Boudnik
      13. BIGTOP-1201.patch
        16 kB
        Konstantin Boudnik
      14. BIGTOP-1201.patch
        14 kB
        Konstantin Boudnik
      15. BIGTOP-1201.patch
        12 kB
        Konstantin Boudnik
      16. BIGTOP-1201.patch
        5 kB
        Konstantin Boudnik

        Issue Links

        There are no Sub-Tasks for this issue.

          Activity

          Konstantin Boudnik made changes -
          Link This issue is required by BIGTOP-1309 [ BIGTOP-1309 ]
          Konstantin Boudnik made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12645070 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12645069 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12645069 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12643613 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12643303 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12643259 ]
          jay vyas made changes -
          Summary Enchance the build to ease development, deployment; abstract implementation Enhance (gradleize) the build to ease development, deployment; abstract implementation
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12642308 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12642301 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12642262 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12641168 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12639518 ]
          Konstantin Boudnik made changes -
          Summary Enchanced the build to ease development, deployment; abstract implementation Enchance the build to ease development, deployment; abstract implementation
          Konstantin Boudnik made changes -
          Summary Enchanced the build to ease development, deployment, abstract implementation details Enchanced the build to ease development, deployment; abstract implementation
          Konstantin Boudnik made changes -
          Summary Enchanced the build to facilitate deployment, abstract implementation details Enchanced the build to ease development, deployment, abstract implementation details
          Konstantin Boudnik made changes -
          Summary Enchanced the build to facilitate deployment, development, and abstract implementation details Enchanced the build to facilitate deployment, abstract implementation details
          Konstantin Boudnik made changes -
          Summary Enchanced the build to facilitrate deployment, development, and abstract implementation details Enchanced the build to facilitate deployment, development, and abstract implementation details
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12636166 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12635960 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12635943 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12635716 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12635450 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12634108 ]
          Konstantin Boudnik made changes -
          Attachment BIGTOP-1201.patch [ 12630227 ]
          Konstantin Boudnik made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Konstantin Boudnik made changes -
          Description As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:
            - build Bigtop framework
            - build and install target artifacts (packages, jars)
            - prepared for develop or test targeted stack
            - enforce all per-requisited consistently
            - coordinate version updates
            - produce documentation
            - <add more here>

          There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can
           - short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
            - long term: consolidate all bits of the framework in one comprehensive build management system

          An apparent requirements of the solution:
            - it needs to play well with JVM stack
            - it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
            - don't limit our ability to replace (if needed) various bits of current framework with something more uniform.

          Behold, I propose Gradle.

          As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:
            - build Bigtop framework
            - build and install target artifacts (packages, jars)
            - prepared to develop or test targeted stack
            - enforce all per-requisites consistently
            - coordinate version updates
            - produce documentation
            - <add more here>

          There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can
           - short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
            - long term: consolidate all bits of the framework in one comprehensive build management system

          An apparent requirements of the solution:
            - it needs to play well with JVM stack
            - it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
            - don't limit our ability to replace (if needed) various bits of current framework with something more uniform.

          Behold, I propose Gradle.

          Konstantin Boudnik made changes -
          Field Original Value New Value
          Description As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:
            - build Bigtop framework
            - build. install, and target artifacts (packages, jars)
            - prepared for develop or test targeted stack
            - enforce all per-requisited consistently
            - coordinate version updates
            - produce documentation
            - <add more here>

          There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can
           - short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
            - long term: consolidate all bits of the framework in one comprehensive build management system

          An apparent requirements of the solution:
            - it needs to play well with JVM stack
            - it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
            - don't limit our ability to replace (if needed) various bits of current framework with something more uniform.

          Behold, I propose Gradle.

          As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:
            - build Bigtop framework
            - build and install target artifacts (packages, jars)
            - prepared for develop or test targeted stack
            - enforce all per-requisited consistently
            - coordinate version updates
            - produce documentation
            - <add more here>

          There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can
           - short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
            - long term: consolidate all bits of the framework in one comprehensive build management system

          An apparent requirements of the solution:
            - it needs to play well with JVM stack
            - it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
            - don't limit our ability to replace (if needed) various bits of current framework with something more uniform.

          Behold, I propose Gradle.

          Konstantin Boudnik created issue -

            People

            • Assignee:
              Konstantin Boudnik
              Reporter:
              Konstantin Boudnik
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development