Local builds for Travis runners

[alaxalves]

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• PR is descriptively titled 📑 and links the original issue above 🔗
• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
• code is in uniquely-named feature branch and has no merge conflicts 📁
• screenshots/GIFs are attached 📎 in case of UI updation
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

[alaxalves]

Ok guys @kaustubh-nair @jywarren, so apparently #605 was not enough to completely split our environments apart. I later realized that the previously created file docker-compose.test.yml was using our default Dockerfile to create its image, and our Dockerfile has been set for production, as well as the production's default docker-compose.yml file. So by making the docker-compose.test.yml file "inherit" of the default Dockerfile was not a good call. Anyway this was causing some misleading on the builds, Codecov and such. Along with @kaustubh-nair we have decided that the best approach was using the default settings provided by Travis itself and include a job testing the builds of the docker image.

[alaxalves]

Some good news is that by setting our runners like this, we got to decrease the build time even more, something like ~2x faster. Check the Before/After:

https://travis-ci.org/publiclab/mapknitter/builds/542443630

https://travis-ci.org/publiclab/mapknitter/builds/542460131

[alaxalves]

Hey guys @kaustubh-nair @cesswairimu the functional tests have been passing in my local environment. Also, @jywarren @icarito @sashadev-sky could yall give me a hint on the Unit tests? Please check the set up I've made in travis.

[jywarren]

I see the error here:

ERROR["test_should_display_export_index", #<Minitest::Reporters::Suite:0x0000000008066550 @name="ExportControllerTest">, 0.5164600869999845]
 test_should_display_export_index#ExportControllerTest (0.52s)
ActionView::Template::Error:         ActionView::Template::Error: File to import not found or unreadable: style.
        Load paths:
          /home/travis/build/publiclab/mapknitter/app/assets/images
          /home/travis/build/publiclab/mapknitter/app/assets/javascripts
          /home/travis/build/publiclab/mapknitter/app/assets/stylesheets
          /home/travis/build/publiclab/mapknitter/vendor/assets/images
          /home/travis/build/publiclab/mapknitter/vendor/assets/javascripts
          /home/travis/build/publiclab/mapknitter/vendor/assets/stylesheets
          /home/travis/build/publiclab/mapknitter/public/lib
          /home/travis/.rvm/gems/ruby-2.4.6/gems/popper_js-1.14.5/assets/javascripts
            app/assets/stylesheets/application.scss:2
            app/views/layouts/application.html.erb:16:in `_app_views_layouts_application_html_erb___2692047925648521322_22375520'
            test/functional/export_controller_test.rb:12:in `block in <class:ExportControllerTest>'

On this test:

mapknitter/test/functional/export_controller_test.rb

Lines 11 to 17 in 3588ccd

	test 'should display export index' do
	get :index
	assert_response :success
	assert assigns[:exports]
	assert assigns[:day]
	assert assigns[:week]
	end

But the error ActionView::Template::Error: File to import not found or unreadable: style. makes me think it's a stylesheet issue? Yes, this line:

mapknitter/app/assets/stylesheets/application.css

Line 18 in 3588ccd

*= require style

it can't seem to find a stylesheet named "style.___" (probably .css). Any reason why that wouldn't be there? Is it looking for an scss or sass file and the asset pipeline is not able to read the filetype we're offering? Some need to be converted to .css so there could be some relation to the asset pipeline job also not completing? Though I didn't look at those logs.