Open jwilm opened 10 years ago
I suspect this has something to do with dciy.toml
, and might be another symptom of it just not being that great a way of approaching the specification of buildsteps :confused:
That's strange. @jwilm, are you still seeing this? I can't seem to reproduce it now:
Or even by building master
off of your fork, which (properly) fails due to pending migrations:
The build should actually blow up descriptively if the CI commands are empty for whatever reason. The only way it wouldn't is if rspec
or bundler
silently failed, with no output and a 0 exit code...
There is a problem building DCIY master branch when running DCIY on master. Output from rspec is not shown, and the build completes as if
bundle exec rake spec
returned successfully without doing anything. Here is the output from DCIY:This does not seem to happen when cloning and building a fresh copy of DCIY from terminal, although that gets a lot of rspec errors due to the security token not being set.
Sorry I don't have time to look into this further this morning. My next steps would be testing against another code base to see if that builds properly, and then doing a bisect to see where this was introduced if it's not just a problem with our own build configuration.