Open Source

[TylerBrock]

If we don't then all the MCI hosts / Jenkins hosts will need deploy keys or we will need to modify the base images (all of which are going to waste a fair amount of time for people)

[TylerBrock]

This is becoming more critical as we want to test everything on Travis-CI as well as internally on MCI.

[TylerBrock]

I assume @gjmurakami-10gen is going to have similar problems as the ruby driver tests extensively on Travis-CI for pull requests, etc if they use this in "production" for the driver.

[imlucas]

@TylerBrock short-term idea based on flows we use for mongoscope. ping me if you're interested though.

1. compile to standalone executables with esky
2. upload to github releases
3. use squirrel

(note: this won't work until squirrel is modified to add the project :P)

Then you can just be able to have travis yaml like:

language: python
python:
  - "2.7"
  - "2.6"
  - "3.2"
install: curl -fsSL http://squirrel.mongodb.land/mongo-orchestration/install | bash

And an MCI yaml like:

tasks:
- name: ci
  commands:
    ...
    - command: shell.exec
      params:
        script: |
          # Grab the install bash from squirrel which will figure out what
          # asset we actually need to pull from Github for OS, arch, etc.
          curl -fsSL http://squirrel.mongodb.land/mongo-orchestration/install | bash
          # Start the rest server before we run tests
          ./mongo-orchestration start;
    ...
post:
  ...
  - command: shell.exec
    params:
      script: |
        # Stop the rest server to clean up
        ./mongo-orchestration stop;
  ...

[TylerBrock]

Hey Lucas, we've actually gone ahead an open sourced the project so it's no longer necessary to make the executables, we can just pip install the world.

[behackett]

Yeah, we plan to push this to pypi next week. In fact, I think this ticket can probably be closed.