Closed localshred closed 13 years ago
After altering that view (- unless @build.artefacts.nil? || @build.artefacts.empty?
) I can get in and see the project page, but clicking force build
ends up doing nothing. I'm not seeing any errors in the rails log.
Currently, there are two modes of running goldberg.
bin/goldberg start_poller
(using the production environment of course). Our understanding was that someone running it in production will probably start it using apache+passenger or some such set up, where we wouldn't be able to start the poller. I just realised this second mode hasn't been documented in the README, and I'll make sure to add that in.There seems to be a separate issue where if you go to a project's page before any builds have been created it barfs. I'm fixing that presently.
Excellent, thank you for the quick response! I'll run the poller and see how things go.
Fixed the empty?
problem in cc2234.
I ran into an error trying to force a build on a new project I created. I was able to add the project using
bin/goldberg add
. After adding the project I launched the app withbin/goldberg start 3001
. When I click force build on the project, nothing appears to happen (not sure if that is normal behavior), then when I click the project to see its builds, I get the standard Rails "We're sorry but something went wrong" error. Checking production.log yields the following error:What is the best way to get around this?