Storybook Continuous Delivery #105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Only on the master branch
jaronheard
approved these changes
May 6, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This sets up the framework for doing continuous delivery of our various artifacts as well as fills out the deployment steps for Storybook CD.
The way Storybook gets deployed is by building the static assets, committing them to the
gh-pagesbranch, then pushing that change. From there, Github handles all the web servery bits.To get Travis to push to our git repo, a personal access token for a privileged user has to be added to the Travis environment.
I didn't want to attach a personal PAT, so I created a bot user (hacko-deploy) and granted that user write access and whatnot.