Closed KVGarg closed 4 years ago
@KVGarg Can you rebase this PR, it would good to merge this one first.
Hey @KVGarg, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
@KVGarg The CI should pass now, seems like there's some other issue.
@KVGarg The CI should pass now, seems like there's some other issue.
Yeah! the ruby bundler isn't found
Hey @KVGarg, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @KVGarg, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @KVGarg, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
@abhishalya ready to be merged
Hey @KVGarg, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
@KVGarg Hmm, not sure what is happening with travis since it should use bundler 1.x as in the Gemfile.lock (as it does for the existing master build). Okay, for now we had enough of this. Let's just manually install bundler and fix this. If we find a better solution, a PR would be fine imo.
@KVGarg Check https://github.com/abhishalya/projects/tree/upstream/%23761 the config there works.
Maybe the bundler was not getting installed in stage test that I declared :rofl: I don't know why I declared that new stage :thinking:
Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Finally! A green check from travis
The commit adds a new section in .coafile which will be responsible for linting css files and, check if there are any error or not.