Accumulo
  1. Accumulo
  2. ACCUMULO-2959

Enable builds of Accumulo in Travis CI

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.0
    • Component/s: build
    • Labels:
      None

      Description

      Travis CI provides free automated builds to open source projects on GitHub. While it might not be possible to set up automated builds for the apache/accumulo GitHub repo, developers can easily set up Travis CI to build their accumulo fork.

      This task is to create a .travis.yml configuration file that will properly build Accumulo in Travis CI. This file is only used by Travis CI and will not affect users that do not use Travis CI.

        Activity

        Hide
        Mike Walch added a comment -

        Yes, please add me with Peterson Technologies and ET.

        Show
        Mike Walch added a comment - Yes, please add me with Peterson Technologies and ET.
        Hide
        Josh Elser added a comment -

        Also, just noticed that you're not listed on the contributors page, Mike Walch. Would you like to be? (optionally with employer and/or timezone)

        Show
        Josh Elser added a comment - Also, just noticed that you're not listed on the contributors page , Mike Walch . Would you like to be? (optionally with employer and/or timezone)
        Hide
        Josh Elser added a comment -

        Mike Walch, ahh, that makes sense. I went ahead a removed the profile activation. Thanks again for the patch.

        Show
        Josh Elser added a comment - Mike Walch , ahh, that makes sense. I went ahead a removed the profile activation. Thanks again for the patch.
        Hide
        Mike Walch added a comment -

        I was thinking that Travis CI should follow the build instructions in the README. I think the majority of build time is spent downloading the dependencies and running unit tests but feel free to remove the "-P assemble". You are right. It's not required.

        Show
        Mike Walch added a comment - I was thinking that Travis CI should follow the build instructions in the README. I think the majority of build time is spent downloading the dependencies and running unit tests but feel free to remove the "-P assemble". You are right. It's not required.
        Hide
        Josh Elser added a comment -

        Not to harp, but does it make sense to have a test server make the tarball just to throw it away? It seems like activating the assemble profile is unnecessary for what is actually desired.

        Show
        Josh Elser added a comment - Not to harp, but does it make sense to have a test server make the tarball just to throw it away? It seems like activating the assemble profile is unnecessary for what is actually desired.
        Hide
        Mike Drob added a comment -

        Thanks for the patch, Mike Walch!

        Show
        Mike Drob added a comment - Thanks for the patch, Mike Walch !
        Hide
        Mike Walch added a comment -

        The build uses "mvn package -P assemble" which runs units but no integration tests

        Show
        Mike Walch added a comment - The build uses "mvn package -P assemble" which runs units but no integration tests
        Hide
        Mike Walch added a comment -

        Was able to get Accumulo to build in Travis CI -

        https://travis-ci.org/mikewalch/accumulo/builds/28785108

        Show
        Mike Walch added a comment - Was able to get Accumulo to build in Travis CI - https://travis-ci.org/mikewalch/accumulo/builds/28785108
        Hide
        Mike Walch added a comment -

        Yes. The goal was to be able to run builds on commits to a fork. I was planning on enabling the unit tests. Travis CI is able to handle all Accismus unit tests & integration tests (which start up mini-accumulo) so I was hoping they would work in Accumulo.

        Show
        Mike Walch added a comment - Yes. The goal was to be able to run builds on commits to a fork. I was planning on enabling the unit tests. Travis CI is able to handle all Accismus unit tests & integration tests (which start up mini-accumulo) so I was hoping they would work in Accumulo.
        Hide
        Sean Busbey added a comment -

        It does allow for e.g. patch builds that would allow automated builds against arbitrary changes. But that's not quite the same, so if the end goal is builds for github clones sounds like this is the way to go.

        Show
        Sean Busbey added a comment - It does allow for e.g. patch builds that would allow automated builds against arbitrary changes. But that's not quite the same, so if the end goal is builds for github clones sounds like this is the way to go.
        Hide
        William Slacum added a comment -

        I don't think so. I'm interpreting the goal as making it easier for a user with their own fork to set up automated builds. Does the ASF jenkins let anonymous clones take up resources on it?

        Show
        William Slacum added a comment - I don't think so. I'm interpreting the goal as making it easier for a user with their own fork to set up automated builds. Does the ASF jenkins let anonymous clones take up resources on it?
        Hide
        Sean Busbey added a comment -

        Could we achieve these same goals by updating our ASF Jenkins builds?

        Show
        Sean Busbey added a comment - Could we achieve these same goals by updating our ASF Jenkins builds?
        Hide
        Josh Elser added a comment -

        Last time I tried this, TravisCI couldn't handle the ITs. Are you just planning on enabling the unit tests?

        Show
        Josh Elser added a comment - Last time I tried this, TravisCI couldn't handle the ITs. Are you just planning on enabling the unit tests?

          People

          • Assignee:
            Mike Walch
            Reporter:
            Mike Walch
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

                Development