Running cruise add --help starts builders for existing projects #98

javanthropus opened this Issue Apr 14, 2012 · 0 comments


None yet

1 participant


When running cruise add --help from the current master branch, an attempt is made to start all builders for all existing projects in the background. If the builders are not already running, they will be started; otherwise, errors are reported about file lock ownerships:

Builder for project 'example_project' started
Logging to: /opt/cruisecontrol.rb/log/example_project_builder.log


[fatal] Another process holds a lock on project 'example_project'.
Look for a process with a lock on file /home/build/.cruise/projects/example_project/builder.lock
Builder for project 'example_project' exited

This happens because the cruise script forces the Rails environment to be set to production prior to loading the environment files. The production environment is set to always start builders by default.

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