|Please ask about problems and questions regarding this tutorial on answers.ros.org. Don't forget to include in your question the link to this page, the versions of your OS & ROS, and also add appropriate tags.|
Enabling ROS Epic Fail for a Hudson BuildDescription: Enable ROS Epic Fail for a Hudson build, so that tests can use ROS Epic Fail
Tutorial Level: ADVANCED
In this tutorial, we will add ROS Epic Fail to a build so that users can access the epic fail bag files.
Choosing the Bag File Location
First, one must chose a location for bag files that is capable of handling large files. This is because the bag files will often take up 30-40 gigs for each test. Second, bag files will be written at great speed, and so there must be enough bandwidth. Third, users will have to be able to get the bag files out and so they can analyze them. Often, the chosen location will be on the hard drive of the build machine. By default, ROS Epic Fail writes the bag files to the ROS test_results directory. This is often not a good idea in Hudson, because Hudson often deletes that directory.
Setting the Bag File Location
ROS Epic Fail reads from the environment variable ROS_EPIC_FAIL_BAGS_DIR. Thus, you must add a command to export that environment variable to each Hudson "Execute shell" block. The directory must exist, and the Hudson build must have permission to write to the directory.