continuous deployment

[chadwhitacre]

When tests pass on a certain branch.

Suggested by @SimonSapin on Twitter.

We'd need to review who has what permissions on the repo.

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

[jeromegn]

We could actually do it directly with Travis CI, with their after_scripts and environment variables.

[joealcorn]

@jeromegn No need anymore, http://about.travis-ci.org/docs/user/deployment/

[jeromegn]

@buttscicles Neat! Has been a long time since I looked that up.

[chadwhitacre]

IRC convo

[hashar]

I would not use a third party to deploy on a production site. Much less whenever a change is merged in master unless that is severely controlled. The problems are:

• anyone with merge access can potentially become root on your infrastructure
• travils getting owned : gittip is owned.

[chadwhitacre]

Besides the security concerns, there's the less severe but more common case of GitHub and/or Travis going down. We don't want that to hold up deployment for us.

[jeromegn]

@whit537 hopefully the CI will use the same script we'd use to deploy. Therefore we could manually deploy. Would be cool to mirror the repo somewhere else, but might be overkill ;)

[chadwhitacre]

+1 from @wyze in IRC (I think).

[mvdkleijn]

We could also run our own Jenkins server and trigger it through a github web hook. If its a commit on a preconfigured branch by a preconfigured github user(s), the jenkins server would deploy on live...

Also, I wouldn't have a problem with deployment straight from GitHub provided only trusted people have access to the branch or repo.

Automated deployment should never stand in the way of manual updates either. Then the automated system was setup wrong.

[chadwhitacre]

Dropping from Infrastructure. This is advanced infrastructure.

[chadwhitacre]

... as a Service: http://dploy.io/

[chadwhitacre]

See also #1133.

[Changaco]

Tagging as "blocked", because we'd need to automate DB migrations first, see #2360.

[nobodxbodon]

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