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

deploy branches to heroku automatically #1133

Closed
chadwhitacre opened this issue Jul 13, 2013 · 17 comments
Closed

deploy branches to heroku automatically #1133

chadwhitacre opened this issue Jul 13, 2013 · 17 comments

Comments

@chadwhitacre
Copy link
Contributor

We need this to turbo-charge our development workflow (@corytheboyd and @warreng called it; props). The idea is that any branch in GitHub gets its own public deployment, with its own database with fake data. This should be a subcommand of gittip.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@chadwhitacre
Copy link
Contributor Author

Note that Heroku deploys master, so you have to do git push -f heroku HEAD:master.

Or possibly git push staging staging:master.

@chadwhitacre
Copy link
Contributor Author

It's git push <remote-repo> <local-branch>:master.

@chadwhitacre
Copy link
Contributor Author

Yeesh. I just hand-rolled another Gittip instance on Heroku. That was ... something that could be optimized.

@chadwhitacre
Copy link
Contributor Author

+1 from @jeromegn in IRC.

@chadwhitacre
Copy link
Contributor Author

I wonder whether we can leverage Heroku buildpacks to do this. Circle back here after #1257.

@chadwhitacre
Copy link
Contributor Author

Dropping from Infrastructure. This is advanced infrastructure.

@chadwhitacre
Copy link
Contributor Author

@clone1018 found http://prune.io/ for this. IRC

@seanlinsley
Copy link
Contributor

Assuming each branch gets deployed to a brand new Heroku instance, is there a limit to the number of free Heroku instances you can have?

@rummik
Copy link
Contributor

rummik commented Dec 6, 2013

@seanlinsley I'm pretty sure it's fine so long as you're not using the extra instances to get around paying for extra dynos

@chadwhitacre
Copy link
Contributor Author

cc: @patcon

@chadwhitacre
Copy link
Contributor Author

+1 from @techtonik at #3718 (comment).

Should we have a dev.gratipay.com with the WIP site version that is automatically pushed on commits from master?

@chadwhitacre
Copy link
Contributor Author

For each new GitHub pull request (“PR”), Heroku will spin up a disposable “Review App” with a unique URL for the development team to review and test. Now, instead of guessing what the new code might do, reviewers — including designers, testers, and PMs — can receive a link and actually try it out in a browser, before the code reaches staging or production environments.

http://blog.heroku.com/archives/2015/9/3/heroku_flow_pipelines_review_apps_and_github_sync#review-apps-in-the-flow

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented Apr 19, 2016

Today, we are happy to announce the graduation of Heroku Review apps from an exceptionally popular beta to being generally available to all Heroku users.

Review apps are the instant, disposable Heroku app environments that can spin up automatically with each GitHub pull request. They allow developers and their teams to automatically build and test any pull request, updated at every push, at a temporary, shareable URL. When the pull request is closed or merged, the Review app is deleted. GitHub users are notified of all this, right in the pull request web interface.

https://blog.heroku.com/heroku-review-apps-ga

@nobodxbodon
Copy link
Contributor

The page in the last comment seems to be pulled back. I guess the service is still beta. Will it be free for our purpose?

@chadwhitacre
Copy link
Contributor Author

Looks like they have a broken redirect on the blog post. Here's the correct link: https://blog.heroku.com/heroku-review-apps-ga.

@chadwhitacre
Copy link
Contributor Author

I've updated the link in my comment.

@nobodxbodon
Copy link
Contributor

As the issue isn't user-oriented, reticket to inside.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants