Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-2535

frontend-maven-plugin fails on ppc64le

    Details

      Description

      An alternate method to install nodejs during maven build is to use frontend-maven-plugins. However, the current version of the plugins ( version =< 1.0.0) has hard coded path to x86 node binary.
      This issue has been resolved by pull request https://github.com/eirslett/frontend-maven-plugin/pull/427, targeted for 1.2.0 release.
      Meanwhile to unblock zeppelin, Tez, and Ambari 2.2.0 builds we need to include the plugin and PhantomJS as part of the docker slave image for PPC.

        Activity

        Hide
        kwmonroe Kevin W Monroe added a comment -

        My license comment above may be answered here:

        http://www.apache.org/legal/resolved.html#category-a

        phantomjs is BSD 3-clause, and so it appears this is acceptable for inclusion in Apache products. Anyone more versed in this stuff care to weigh in?

        Show
        kwmonroe Kevin W Monroe added a comment - My license comment above may be answered here: http://www.apache.org/legal/resolved.html#category-a phantomjs is BSD 3-clause, and so it appears this is acceptable for inclusion in Apache products. Anyone more versed in this stuff care to weigh in?
        Hide
        kwmonroe Kevin W Monroe added a comment -

        reopening to address above points

        Show
        kwmonroe Kevin W Monroe added a comment - reopening to address above points
        Hide
        kwmonroe Kevin W Monroe added a comment -

        This isn't resolved yet (no one committed the patch to bigtop's git repo). I had a look today and have a couple questions about the current (Sept 15) patch:

        • I see you using wget instead of git clone. Why? Is git not available in the image? It's fine if that's the case, but if you do have git available, you could save a couple wget / unzip steps.
        • Every time you "RUN", you start at the root of an isolated filesystem, so this extra step isn't needed:
          +RUN cd ..
        • The license for the phantomjs blob that you're retrieving is BSD (license from github). I'm no expert in licensing, so I'm not sure if there are any ramifications of including this for a bigtop docker slave's runtime environment. Can anyone speak to potential conflicts or attribution requirement here?
        Show
        kwmonroe Kevin W Monroe added a comment - This isn't resolved yet (no one committed the patch to bigtop's git repo). I had a look today and have a couple questions about the current (Sept 15) patch: I see you using wget instead of git clone. Why? Is git not available in the image? It's fine if that's the case, but if you do have git available, you could save a couple wget / unzip steps. Every time you "RUN", you start at the root of an isolated filesystem, so this extra step isn't needed: +RUN cd .. The license for the phantomjs blob that you're retrieving is BSD ( license from github ). I'm no expert in licensing, so I'm not sure if there are any ramifications of including this for a bigtop docker slave's runtime environment. Can anyone speak to potential conflicts or attribution requirement here?
        Hide
        asanjar Amir Sanjar added a comment -

        requires build

        Show
        asanjar Amir Sanjar added a comment - requires build

          People

          • Assignee:
            asanjar Amir Sanjar
            Reporter:
            asanjar Amir Sanjar
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:

              Development