Build Automation - Continuous Integration - Delivery

[joshwiens]

Working Tasks for implementation of CI & CD

Tools

CI & CD Platform ( In order of viability imho )

• Travis CI

Build Automation

• Gulp Build Automation

Unit Test / Coverage

• Chai Execution in Travis
• Mocha Execution in Travis

Code Coverage

• Codecov Implementation

Requirements

Pull Request Validation

• Clean Build
• Passing Unit Tests
• Clean Static Code Analysis

Release Validation

• Pull Request Validation + Packaging Validation of supported platforms
• Further requrements T.B.D.

Versioning

• http://semver.org/
• node-semver Implementation

Release Planning

• Waffle.io

Docker Build

• See Set up Docker #15

Homebrew Support

• See Create homebrew cask for easy installation on Mac #77

Package Distribution

• Alpha Builds - Binary packages added to tagged GitHub Release

Continuous Delivery Stages

T.B.D. Based on CI Platform and desired tooling

[joshwiens]

@G07cha @ShockOne - Very high level ops plan.

@jcgertig - You expressed interest in #28, I would be interested in your opinions as well.

[vlad-shatskyi]

@joshtoo, that looks awesome. I'm fine with any CI server as long as it's free. Also, wanted to show you yet another one: https://www.solanolabs.com/. I'm not suggesting it, just for your information.

Perhaps you know it, but just in case: we already use gulp, chai and mocha.

Is there anything required from me to make it happen?

[joshwiens]

@ShockOne - I believe I already read that the project is going to adopt standard gitflow which is really necessary for CI & CD imo.
I am going to proof out all of the configuration on my fork adding all of the linting and build automation. Once I have it working in a useful manner as a proof of concept, one of two things will need to happen.

• You will need to implement the CI configuration in whichever CI offering we choose
• I will need repo access sufficient to modify the CI configuration and approve the web hooks as they all run off of github oauth.

There will be at least two pull requests that accompany the CI configuration while will need to merge in before the build will run and report results.

I should be able to get started on this around 20:00 GMT.

[G07cha]

@joshtoo, do you already have exact workflow model for this? If not, my workflow suggestion is:

• TravisCI - for testing and deployment
• Codecov - for coverage measurement
• Waffle.io - for release planning

[joshwiens]

@G07cha - The list is far from final. Travis would be my first choice for CI as well. I'm not partial to any particular coverage tools so Codecov is just fine by me and I'll add Waffle to the list.

[G07cha]

List it's just suggestions, for completing this issue you need to make decisions. Which CI use, how connect it's all together, etc. So I would like to see your point of view about workflow model.

[G07cha]

Btw, for release planning we can use build-in milestones or external Trello board

[jcgertig]

this looks good I am testing out configuration for both travis ci and codeship.io to see which one is the best for the needs of this project

[joshwiens]

@jsgertig The decision has already been made to go with Travis for CI / CD.

[jcgertig]

That works

[jcgertig]

you can see what I m working on @joshtoo here https://github.com/jcgertig/black-screen/tree/add-auto-build

[joshwiens]

@jcgertig - Keep at it. I'm into test execution / linting / code quality this evening. As of now we are not duplicating effort.

[jcgertig]

do you already have a travis ci yaml on a branch?

[joshwiens]

@jcgertig Next task. If you are ready I will take codecov and semver and roll that into what you stick in the Travis.yml

[joshwiens]

@jcgertig - Shared feature branch to poc everything you and I have coming it.

PR => https://github.com/black-screen/black-screen/tree/63_travis-ci