Automate Builds via CircleCI about stoic_penknife HOT 2 CLOSED

D - Get CircleCI RUNNING. Get it set up and running.
O - I have an excellent, classy, working, clear .circleCI/config.yml file set up, that I understand how it works and what each line is doing
B - Somehow I need to better understand how the circleCI config file works... somehow I find it very confusing. Do I need to understand, do I need to use Docker? I fucking hate Docker.
O - Do you need to use Docker with CircleCI?
I -

• What, exactly, does CircleCI do for me?
  Basically, in the context of Stoic Penknife it's going to a) auto-build my app, b) auto-run my tests and rubocop, and then (IF both of these steps succeed) c) auto-deploy the application to Heroku on production. So basically it will save me having to do these steps each time myself, of running tests, rubocop and clicking a button on the Heroku website to deploy. (Actually I think GitHub can already be auto-integrated, so it's not even really saving that step).
• What is Continuous Integration and concretely what will it look like in Stoic Penknife world? What is Continuous Build?
  Before CI is "CB", Continuous Build, i.e. simply automating that every time a new git commit is entered into the repo, that the app gets auto-built someplace. On top of that comes running your tests to check whether your changes still work with the master branch. Together this points you toward the pre-requisites of CI. CI also includes a "philosophical" element of aiming to have developers work in a version control system like git, and be able to work on smaller tasks that can be integrated into the master branch continuously rather than periodically.
• What is Continuous Deployment (How is it different from CI?) and concretely what will it look like in Stoic Penknife world?
  CD is basically the addition to CI that, If the app builds and your tests pass, that the changes get pushed to production. (Or first to staging, then production, if this wasn't just a hobby project!)

To sum up both here is AWS' succinct definition:
"Continuous integration is focused on automatically building and testing code, as compared to continuous delivery, which automates the entire software release process up to production."
http://docs.aws.amazon.com/codepipeline/latest/userguide/concepts.html

• The three rough elements of a Continuous Integration setup are Dependencies, Testing and Deployment.

• Dependencies / Set the Project Up - What Dependencies will I need for Stoic Penknife?

• Ruby 2.6.2

• Postgres

• Bundler

• Install gems in Gemfile

• Testing - What commands will I need to add in order to run my test suite on Stoic Penknife?

• How will I have Rubocop run automatically as part of the tests? Maybe take inspiration from https://gist.github.com/djburdick/5104d15f612c15dde65f ?

• Deployment - What commands will I need in order to deploy Stoic Penknife on Heroku, if the build and the tests are successful?

•  Do I need to understand, do I need to use Docker? I fucking hate Docker.
  Yes and no. CircleCI is already using Docker behind the scenes as I understand it, for their specific machines.

from stoic_penknife.

• do this

from stoic_penknife.