Skip to content

Instantly share code, notes, and snippets.

@ethanrublee

ethanrublee/standalone.rst Secret

Created Sep 21, 2011
Embed
What would you like to do?
standalone ros stuff.

Standalone library pipeline

Some description of the standalone library...

standalone.yml:

- name: rosdep2
  job-profile: python-nose
  rosinstall:
    local-name : ...
    uri : ...

- name: image_pipeline
  job-profile: cmake-simple
  dependencies:
    pip: [...]
    apt: [...]
  debian:
    profile: make-installable #could be git-buildpackage, svn-buildpackage, etc..

make-install profile would be debian package recipe that would basically just set the INSTALL_PREFIX to /opt/ros/DISTRO/

setup.sh will export variable for an FHS that is at /opt/ros/DISTRO, e.g. PYTHONPATH, CMAKE_PREFIX_PATH, etc...

Thoughts

  • Could we potentially just keep this yaml file in each standalone project?
  • post commit hook trigger build/test
  • post commit hook for triggering a debian
  • documentation needs to be built and pushed on each build
  • ROS packages that depend on standalone libraries must be rebuilt and tested
@kwc

This comment has been minimized.

Copy link

@kwc kwc commented Sep 21, 2011

Experiment with doing rosdoc on just a single package:

http://build.willowgarage.com/job/rosdoc-param/?

Experiment with a generic template for Python standalone ROS packages, assumes test output in nosetests.xml:

http://build.willowgarage.com/job/python-rosdep2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment