Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to set up continuous deployment using free hosted tools

simonwillison.net

Post reply on HN
Print view View original

31–40 of 92 posts

Re: How to set up continuous deployment using free hosted tools

#31

Post by helb »

oneweekwonder wrote: post #4

> Need more? Pay for it! or be willing to move vendor and re-implement the stuff. For comparison my magic combination(and not all free or realistic for everyone): - gitlab - jenkins/looking into gl ci - linode/cloudafrica(ah-hah hosting is not free) - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution - irc(fine I will take your slack and use the irc-bridge pfftt)

> - jenkins/looking into gl ci

Yup, definitely look into it. We just killed our last Jenkins instance last week after we found out that everyone eventually moved to the GitLab CI.

> - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution

Why a tough one? I found Sentry easy to self-host. They have pretty good docs: https://docs.sentry.io/server/installation/

> - irc(fine I will take your slack and use the irc-bridge pfftt)

We ditched Slack for Mattermost. It's not entirely up to par (yet), but works for most use-cases. And there's an IRC bridge for it, too (https://github.com/42wim/matterbridge). Oh, and Mattermost comes bundled with GitLab in their omnibus.

Re: How to set up continuous deployment using free hosted tools

#32

Post by geofft »

stephengillie wrote: post #2

Did Travis replace Jenkins? Thanks for posting this. I'm looking to get any application and start deploying through a CI/CD process, to learn how this process works. Any application suggestions for a CI "Hello World"?

Travis is a third-party service. Jenkins is (usually) software you run yourself. Travis will run the infrastructure for you and will not charge you if your project is public on GitHub. So that makes it an extremely popular choice for open-source projects: sign into Travis with your GitHub credentials, click a checkbox on your repo, and add and commit a .travis.yml file, and now you have CI that is well-integrated with GitHub and you don't have to run any infrastructure or pay for any server hosting.

Of course, you have much less control over Travis than Jenkins. Two cases where Jenkins remains obviously better are when you need custom environments that aren't easily portable to Travis (Windows support is a big one, although there is a company called AppVeyor that is something like a Travis for Windows; licensed software is another big one), or if you have strong security/confidentiality requirements (e.g., you're in a regulated industry) and using random cloud services isn't a good option.

Re: How to set up continuous deployment using free hosted tools

#33

Post by oneweekwonder »

helb wrote: post #31
oneweekwonder wrote: post #4

> Need more? Pay for it! or be willing to move vendor and re-implement the stuff. For comparison my magic combination(and not all free or realistic for everyone): - gitlab - jenkins/looking into gl ci - linode/cloudafrica(ah-hah hosting is not free) - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution - irc(fine I will take your slack and use the irc-bridge pfftt)

> - jenkins/looking into gl ci Yup, definitely look into it. We just killed our last Jenkins instance last week after we found out that everyone eventually moved to the GitLab CI. > - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution Why a tough one? I found Sentry easy to self-host. They have pretty good docs: https://docs.sentry.io/server/installation/ > - irc(fine I will take your slack and use t…

> Why a tough one? I found Sentry pretty easy to self-host.

your right, sentry! It was tough thinking of alternatives.

Re: How to set up continuous deployment using free hosted tools

#34

Post by simonw »

milancurcic wrote: post #29

> Once you’ve set up Travis, it will automatically test every commit to every branch Small correction: It will automatically test the latest commit on every push to every branch

Thanks - I updated that sentence to say push instead of branch.

Re: How to set up continuous deployment using free hosted tools

#35

Post by oneweekwonder »

icebraining wrote: post #12
oneweekwonder wrote: post #4

> Need more? Pay for it! or be willing to move vendor and re-implement the stuff. For comparison my magic combination(and not all free or realistic for everyone): - gitlab - jenkins/looking into gl ci - linode/cloudafrica(ah-hah hosting is not free) - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution - irc(fine I will take your slack and use the irc-bridge pfftt)

- sentry is a tough one. We rolling a custom mqttwarn/zabbix solution Sentry is open source, you can self-host it...

A tough one, in the sense of suggesting a better/other alternative. so sentry... gogogofireintehole

Re: How to set up continuous deployment using free hosted tools

#37

Post by stickfigure »

For Java/Postgres/React/Google App Engine, here's a skeleton project using CircleCI:

https://github.com/stickfigure/gstrap-skeleton/

Deployments are git checkout production; git merge master; git push. I love being able to use git log to see what changes are live.

Re: How to set up continuous deployment using free hosted tools

#38

Post by IgorPartola »

Does anyone have a solution for a situation where I have a Django backend and a VueJS front end and want to run the Vue build step before deploying? Currently doing this with Git hooks and committing the resultant build, but that is bad for a number of reasons. This is running on Heroku. Would their release phase allow for this without significantly slowing things down? Would it deal with npm installs?

Re: How to set up continuous deployment using free hosted tools

#39

Post by dasil003 »

mholmes680 wrote: post #21

In my world, its not world-class if i don't get some SOX compliance around it. Its a cool example though.

So you equate "world-class" with "enterprise"? I disagree. Tools that scale down can also be world-class, and in fact that ability to run cheaply is a big part of what allows startups to get off the ground and bootstrap their way to eventually challenge the big boys. Heck, even if they stay small, they can still have world-class tech. Once you get big and purchasing decisions are made far from the front lines I'd argue it gets harder to really have the best tech.
Post reply on HN