search

hackoregon / devops-17

deployment tools for Hack Oregon projects
4 stars 3 forks source link

Enable a minimal CI deploy pipeline for front-end developers (to their own personal S3 bucket) #2

Closed MikeTheCanuck closed 7 years ago

MikeTheCanuck commented 7 years ago

The front-end teams have a basic set of NPM scaffolding for building a working front-end dev environment.

To that we will add minimal devops scaffolding that is demonstrated in the DevOps 2017 class Assignment 2: https://github.com/hackoregon/hacku-devops-2017/wiki/Assignment-2---Travis-CI-Introduction

The result of this work will provide a tested example of the code necessary to automatically run TravisCI tests included in each Hack Oregon project, upon commit to the project repo.

MikeTheCanuck commented 7 years ago

I spent some time working on this tonight. I believe I've conquered the basic .travis.yml configuration, but I've been chasing down a number of deployment bugs that only show up when TravisCI attempts the build. I've documented my trials and tribulations here, and the associated repo has all the code changes I've made to date: https://github.com/MikeTheCanuck/hackoregon-frontend-starter/issues/1

I would LOVE if anyone else could try to reproduce the signature mismatch issue I'm seeing. If not, then I'll kill my repo and TravisCI associated build history, and try over. If you can, then we can continue to chase the various suggestions and workarounds documented here: https://github.com/travis-ci/travis-ci/issues/4776

MikeTheCanuck commented 7 years ago

At this point in the season, it's time to switch over to automated builds of the NPM packages for frontend teams, so this work (if any) is now moot. Maybe next season!