Skip to content
This repository has been archived by the owner on Feb 9, 2021. It is now read-only.

Release & deployment process #15

Closed
9 of 13 tasks
saiichihashimoto opened this issue Jul 13, 2016 · 1 comment
Closed
9 of 13 tasks

Release & deployment process #15

saiichihashimoto opened this issue Jul 13, 2016 · 1 comment
Labels
development

Comments

@saiichihashimoto
Copy link
Member

saiichihashimoto commented Jul 13, 2016 •
edited
Loading

Having an automated and informative release process.

Deploying, versioning, releasing, having meaningful release notes... it's a huge pain. And a waste of our time. This way, when we make changes, they move their way to production on their own and inform everyone properly of what happened.

  • Automatically deploy development environments (pull requests)
  • Automatically determine version
  • Automatically generate release notes
    • github release
    • landing page
    • within the chrome (and others) extension
    • chrome (and others) webstore
    • within our subreddit/twitter/etc?
  • Automatically deploy production environments
    • Have travis run release
    • Have release run build && deploy and have deploy run all deploy:* scripts
    • Change deploy:extension from upload to upload --auto-publish
    • Have master go straight to production and removing hovercards-staging

Blocked by #16 & #79.
https://github.com/semantic-release/semantic-release
https://developer.chrome.com/extensions/autoupdate
https://developer.chrome.com/extensions/hosting
https://devcenter.heroku.com/articles/nodejs-support#heroku-specific-build-steps
https://github.com/commitizen/cz-cli
https://github.com/kentcdodds/validate-commit-msg
@saiichihashimoto saiichihashimoto added this to the Backlog milestone Jul 13, 2016
@saiichihashimoto saiichihashimoto mentioned this issue Jul 13, 2016
Closed
@saiichihashimoto saiichihashimoto changed the title Full pipeline Continuous Deployment Jul 14, 2016
@saiichihashimoto saiichihashimoto modified the milestone: Backlog Jul 14, 2016
@saiichihashimoto saiichihashimoto changed the title Continuous Deployment Continuous deployment Jul 14, 2016
@saiichihashimoto saiichihashimoto removed this from the Backlog milestone Jul 19, 2016
This was referenced Jul 20, 2016
Closed
Open
@saiichihashimoto saiichihashimoto changed the title Continuous deployment Release/Deployment Jul 20, 2016
@saiichihashimoto saiichihashimoto added this to the Backlog milestone Jul 20, 2016
@saiichihashimoto saiichihashimoto changed the title Release/Deployment Better release & deployment process Jul 20, 2016
@saiichihashimoto saiichihashimoto changed the title Better release & deployment process Release & deployment process Aug 4, 2016
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
fix(build): manifest.json receives package version
605462e 
#15
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
chore(release): Travis runs release script
4e1f0e8 
#15
saiichihashimoto referenced this issue Aug 5, 2016
@saiichihashimoto
Merge pull request #91 from teamkogg/release-#15
5a67814 
GitHub releases
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
fix(release): Use last-release-github for semantic-release
29eebb1 
The other last-release plugin didn't work, but this one will (hopefully). It finds the version
locally, anyways.

#15
@saiichihashimoto
Copy link
Member Author

This was automatically generated.

Yes!

saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
chore(build): Builds always use NODE_ENV=production
7f84dbd 
#15
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
chore(release): Travis uploads extension to chrome webstore
8d74ffb 
Currently, it JUST uploads it, but doesn't publish it. @cameronrohani needs to finish #79, then we
can start being confident in our code changes.

#15, #16
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
chore(release): Travis builds and runs deploy script
7ae8b89 
As per #15, the deploy script doesn't ACTUALLY deploy yet.
@saiichihashimoto saiichihashimoto self-assigned this Aug 5, 2016
saiichihashimoto added a commit that referenced this issue Aug 5, 2016
@saiichihashimoto
chore(release): Release www on build
f1d9920 
We can wait on the extension for #79, but we don't have to for the website.

#15
@saiichihashimoto saiichihashimoto removed their assignment Aug 23, 2016
@saiichihashimoto saiichihashimoto removed this from the Backlog milestone Sep 1, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@saiichihashimoto