Talk docs—includes CI (Continuous Integration) benefits, description, and setup tips 💡💪
Switch branches/tags
Clone or download
greenkeeper[bot] and yowainwright Update commitizen to the latest version 🚀 (#58)
* chore(package): update commitizen to version 3.0.5

* chore(package): update lockfile yarn.lock
Latest commit fc8b7c7 Dec 3, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
.github
art
docs
.editorconfig
.gitignore
.markdownlintrc
.nvmrc
.spelling
CHANGELOG.md
CODEOWNERS
CODE_OF_CONDUCT.md
LICENSE
README.md
package.json
yarn.lock

README.md

Developer CI Benefits

Talk: Developer CI Benefits

Greenkeeper badge CircleCI

The Developer CI Benefits talk repository provides documents, links, lists, images, and notes to support the talk. The CI Benefits Talk covers: setup, road to benefits, and benefits of CI. This talk's examples are provided in shell commands and JavaScript but can be applied to other development patterns and languages. If unfamiliar, CI stands for continuous integration.


Initiatives 📈

The sections below provide context into to flow of the Developer CI Benefits talk. This talk uses JavaScript to describe CI but CI patterns in other languages may be similar.


  • 🔥 View a demo of techniques described in this repository or discussed during the talk here (also, on NPM).
  • View a demo's dependent and how dependent project is influenced and can be update base on it's parent changes (also, no NPM).

Context

This talk is aimed at developers interested in CI benefits. It describes how CI works with examples for getting started with CI. It touches on different tooling and options available for CI. It connects implementation of CI and ways to save time for developers and money for companies.

Goals

This talk's goals are to describe CI, CI benefits, CI patterns, and provide developers with information to get started with CI.

Conclusions

Concluding this talk, listeners/developers will have tools to use to start their own CI processes. They will have a brief exploration into different CI patterns. They will be aware of benefits that developers receive after implementing CI.


Bulleted Documents 🔫

Listed below are docs for the talk. The Docs README can be viewed for more docs information.



Reference 📝

Listed below are references used in the construction of this repository.

  • CircleCI: the tool used and described in this repository to run CI
  • Travis: a CI runner alternative to CircleCI used to run CI
  • Greenkeeper: a tool that monitors and assists in updating JavaScript packages
  • NPM: a package manager for node/JavaScript projects
  • Jest: a unit testing tool for testing JavaScript projects
  • Puppeteer: a Chrome browser tool that provides an API to control Chrome

Contributing

The steps below define how to contribute to this repository.

Contributing to this repository can be done by:

  1. forking this repository
  2. pushing a commit without bypassing pre-commit messages
  3. follow the messaging within the Pull Request Template

Besides code updates, this repository follows Contributing Guidelines as defined by Contributing Covenant for communication within issues and pull request conversations.

For updating and/or adding documents, use the Illustration templates here.


Shoutouts 🙏

Listed below are people I would like to thank for helping me learn enough to give this talk. Because these people will be referenced in the talk, I'd like to thank them.

  • Arjan Singh: Thanks for forcing me to do TDD (Test Driven Development).
  • Brian Gates: Thanks for improving caching practices in CircleCi. You've saved me so much time.
  • Brian Gonzalez: Thanks for building a lot of cool s**t always—projects referenced in this talk; starting Harmless Changes.
  • David Inoa: Thanks for helping make this project better, reaching out about it, and your CodePen.
  • Jon Ong: You're brilliant and I got to watch you build awesome project—including projects for CI—like gh-automerge.
  • Matt Young: Thanks doing a bunch of cool CI projects—like auto-update—make it public!
  • Peter Cadwell: Thanks for helping this repository much better!
  • Rouzbeh Sarrafieh: Thanks for helping me with this talk and always making software seem so fun.