3 ms·

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

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"?

oneweekwonder 9y ago
Have a look at gitlab ci[0], the quick start was easy. Got it working online and self-hosted. https://about.gitlab.com/features/gitlab-ci-cd/ https://about.gitlab.com/features/gitlab-ci-cd/
aaronbrager 9y ago
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.
- stephengillie 9y ago
  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.
korzun 9y ago
You should use Jenkins instead. There is no guarantee that Travis will remain free or remain at all.
lmm 9y ago
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)
geofft 9y ago
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.

oneweekwonder 9y ago

Have a look at gitlab ci[0], the quick start was easy. Got it working online and self-hosted. https://about.gitlab.com/features/gitlab-ci-cd/ https://about.gitlab.com/features/gitlab-ci-cd/

aaronbrager 9y ago

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.

stephengillie 9y ago
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.

korzun 9y ago

You should use Jenkins instead. There is no guarantee that Travis will remain free or remain at all.

lmm 9y ago

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)

geofft 9y ago

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.