If your tests are passing and branch merge to master your changes will be deploy automatically to AWS.
http://flowupapp-env.eu-west-1.elasticbeanstalk.com/
Travis is configured to automatically deploy the project to our AWS instances of any commits merge to master that are passing tests.
Travis compiles and generates a zip using sbt dist.
When the zip is ready, travis upload it to a versioned bucket named flowupserver-builds
AWS Codepipeline is watching the bucket and will deploy to elastic beanstalk flowup-app > flowupApp-env
flowupApp-env will build the Dockerfile and will run binary generated by sbt dist.
Available at http://flowupapp-env.eu-west-1.elasticbeanstalk.com/
docker-compose up
sbt gatling:test
sbt "test-only *AnyPatterRelatedToTheClassName"
An example based on this project could be:
sbt "test-only *ElasticsearchClientTest"
Full documentation here.
Full documentation here.
To run the FlowUp server using a configuration similar to the production one where the assets are going to be versioned and the javascript minified you can run the server using this command sbt testProd. This will build the server artifact and will start the service using a production like build you can run locally.