Continuous Deploy

Uploaded on

Presentation for Göteborgs Scalaentusiaster Meetup group. …

Presentation for Göteborgs Scalaentusiaster Meetup group.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Continuous DeployUsing the cloud with Play! 2, Bitbucket, Cloudbees and Heroku for FREE*
  • 2. IntroductionMagnus AnderssonCo-founder Solvies ABBlog: magnusart.comTwitter: @magnusart
  • 3. Overview● What is Continuous Deploy?● This is what we are doing today● Meet the tools ○ Play! 2 Framework ○ Atlassian Bitbucket ○ CloudBees ○ Heroku● DEMO!● Is all this really for FREE*?● Appendix A - Continuous Deploy recipe● Appendix B - Links and resources
  • 4. What is Continuous Deploy?To continuously deploy software into targetenvironment upon push/check in to blessedVCSContinious Integration, Continuous Deliveryand DevOps are are subset or supersets of thesame idéas, tools and methodologies
  • 5. This is what we are doing today
  • 6. Meet the toolsRuby on Rails inspired web framework. Buildswith Scala Build Tool.Both Scala and Java, foundation rewritten inPlay2.
  • 7. Meet the toolsGit hosting that allows for free privaterepositories. Free private git and mercurialrepos.The competitor, Github, can be used as well butonly public repos are free
  • 8. Meet the toolsOnline Jenkins Continuous Integration serverhosting.Travis CI is an interesting alternative, butwould not work well for this scenario as there isno private way to store private SSL keys.
  • 9. Meet the toolsPolyglot cloud PAAS hosting. Supports Ruby,Java, Scala, Cloujure and Python in the CeladonCedar stackSolves package archiving (Git), deployautomation, rollback and provides a third partyadd-on community (DB, Logging, Messaging)Heroku runs in the Amazon cloud. Slug size foryour app is 100mb, inc. resources/artifacts
  • 10. DEMO!
  • 11. Is all this really for FREE*?Yes it is, but only for a give value for FREE...You may want to pay for the following1. Play! 2 Framework support a. Typesafe supscription. Price: info@typesafe.com2. Atlassian Bitbucket a. 5 collaborators free b. Paid plans ranging from $10 - $80/month3. CloudBees a. 300 minutes of build time, 10 developers free/month b. Plans ranging from $15 - $100/month c. Paid plans are fixed base price + pay as you go
  • 12. 4. Heroku Dynos a. 750 dyno hours/month free b. Dynos cost $0.05/hour (~35$/month per dyno) c. Dynos are charged per second d. If you spin up a Dyno Heroku will charge for it until you manually spin it down again. e. If you have less than two web Dynos, Heroku will spin down your Dyno after a period of inactivity. Starts up upon first subsequent request (5-10 sec). f. HireFireApp is a 3rd party Ruby application that can scale your Dynos based on response time and job queue. It will poll your app with HTTP requests, so Dyno spin down should not be an issue. Costs amounts to HireFireApp $10/month + Heroku $0.05/h. Only supports Ruby stack natively, but uses a simple JSON api your app can implement.
  • 13. 4. Heroku Third Party addons a. Convenient way to install third party addons b. Heroku PgSQL database 5MB is included i. $200/month for 1TB and 1.7GB Cache c. MongoLab 250MB free DB i. $10/month for 0.5GB and upwards d. IronMQ 250 000 request/month free i. $9.99/month for 10 000 000 requests/month ii. Both RabbitMQ and CloudAMQP are in private betas e. For file storage Heroku recommends Amazon S3 f. In general the add-ons can be pricy, but there is no lockin, you can get started in Heroku and move to those things that turns out to be too expensiveMore addons:
  • 14. Appendix A Continuous Deploy recipe1. Create Heroku App a. Configure custom buildpack to keep Slug size down b. Is it deployed?2. Create Git repos a. Create remote repo b. Clone repo c. Add Heroku remote d. Create Play Application in subfolder e. Move files to parent dir f. Add Procfile config for Play! g. Add gitignore h. git push heroku master
  • 15. 4. Create CloudBees job a. Create job b. Configure CloudBees access to Git repos (Heroku and Atlassian/Github) c. Install Jenkins SBT plugin to CloudBees d. Add Git Plugin e. Configure job Git remotes f. Add tagging g. Fire up build!5. Commit, push to trigger a build followed by deploy into Heroku
  • 16. Appendix B Links and resourcesHireFireApp support ticket describing API: Scala Build Pack, Heroku competitorhttps://openshift.redhat.comOpenShift DIY Cartridge Play2 Quickstart presentation is available on SlideShare
  • 17. Contact informationMagnus AnderssonCo-founder Solvies ABmagnus.andersson@solvies.seTwitter: