In my world, its not world-class if i don't get some SOX compliance around it. Its a cool example though.
How to set up continuous deployment using free hosted tools
21–30 of 92 posts
Re: How to set up continuous deployment using free hosted tools
#22The only 'free' tool in the article is Travis CI.
It's important to understand that you are effectively locking yourself in under a promise of a free tier and should plan to make sure you can afford the paid subscription in a couple of months or years.
Some companies may also sell your data to third-party affiliates, with, or without your consent or knowledge.
Re: How to set up continuous deployment using free hosted tools
#23Did 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"?
You should use Jenkins instead. There is no guarantee that Travis will remain free or remain at all.
Re: How to set up continuous deployment using free hosted tools
#24Did 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 lot more user-friendly than Jenkins and they run it for you, whereas Jenkins you usually self-host. (Jenkins is a lot more flexible and has a lot going for it, but Travis is much easier to get up and running)
Re: How to set up continuous deployment using free hosted tools
#25Shameless plug: I wrote an open source incoming webhook server that can run your build & redeployment scripts: https://github.com/adnanh/webhook
Re: How to set up continuous deployment using free hosted tools
#26> 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)
I really wanted to use Gitlab for my next side project, but Circle CI doesn't support them, and I really don't want to pay Travis for my shitty proj. Hopefully this changes some day soon.
We use gitlab's built-in runners and pipelines for continuous deployment to kubernetes and it works very well. We self-host our repos but the same tools are available through the hosted version.
Re: How to set up continuous deployment using free hosted tools
#27Did 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"?
I think you mean CD “Hello World”, not CI. You can make a “hello world” web app (or even just an API endpoint) in your favorite language and set it up to deploy on each commit. CD means each commit that passes tests is deployed CI means your code is regularly integrated (merged) vs having long QA / code review cycles. CI and CD work great together but you can have one without the other.
Yes, I want to better understand the process of committing code to the repository of an application, have it run automated tests, report via a communications tool the result, and automatically deploy if successful. Understanding this efficient process is high in demand and thus highly profitable.
I've created and worked on several projects that have involved APIs, reading from Zendesk, and writing to Slack or HTML, among other places. I've supported Jenkins and related tools multiple times in production. Now I want to fill this gap in my knowledge.
Re: How to set up continuous deployment using free hosted tools
#28> 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)
I really wanted to use Gitlab for my next side project, but Circle CI doesn't support them, and I really don't want to pay Travis for my shitty proj. Hopefully this changes some day soon.
GitLab's built-in CI is very good, and simpler than Travis for some things.
You also have the option (unlike Travis) of registering your own runners in your project settings, and you can do this either on gitlab.com or another deployment, without needing to be an admin of the deployment - you can get a key for it in your own project's settings. I'm using this at work, where we have an internal GitLab that I'm not an admin of (and where the GitLab admins probably have no interest in running a CI system), to do a small bit of CI on some things using one of my team's servers as a runner.
Re: How to set up continuous deployment using free hosted tools
#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
Re: How to set up continuous deployment using free hosted tools
#30Heroku does have a free tier, but it's intended for experiments. It's very limited and wouldn't be acceptable for any serious website, certainly not a 'world class' setup. Unless you're very careful to have one free dyno per account, and avoid using features like staging apps, they will power down your server for several hours a day.
Yeah, the “world-class” hook was more about the quality of these tools than their applicability for use at scale for free - I encourage people to pay real money at various points in the article.
I’m currently running my blog on a single $7/month Heroku Dyno (plus $9/month for Heroku PostgreSQL) behind a free Cloudflare account - with the right caching headers I can easily handle huge amounts of read traffic. I was going to mention Cloudflare in this piece but I decided it didn’t fit the theme of continuous deployment as well as the other tools.