Need advice about which tool to choose?Ask the StackShare community!
IntelliJ IDEA vs Travis CI: What are the differences?
IntelliJ IDEA: Capable and Ergonomic IDE for JVM. Out of the box, IntelliJ IDEA provides a comprehensive feature set including tools and integrations with the most important modern technologies and frameworks for enterprise and web development with Java, Scala, Groovy and other languages; Travis CI: A hosted continuous integration service for open source and private projects. Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
IntelliJ IDEA can be classified as a tool in the "Integrated Development Environment" category, while Travis CI is grouped under "Continuous Integration".
Some of the features offered by IntelliJ IDEA are:
- Smart Code Completion
- On-the-fly Code Analysis
- Advanced Refactorings
On the other hand, Travis CI provides the following key features:
- Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.
- Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.
- Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.
"Fantastically intelligent", "Best-in-class ide" and "Many languages support" are the key factors why developers consider IntelliJ IDEA; whereas "Github integration", "Free for open source" and "Easy to get started" are the primary reasons why Travis CI is favored.
According to the StackShare community, IntelliJ IDEA has a broader approval, being mentioned in 815 company stacks & 1065 developers stacks; compared to Travis CI, which is listed in 670 company stacks and 624 developer stacks.
UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.
I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?
Pycharm is great for python development, but can feel sometimes slow and community version has Somme very annoying restrictions (like they disabled jupyter notebooks plugin and made it premium feature). I personally started looking into VS Code as an alternative, and it has some very good potential. I suggest you take it into account.
The Community version of PyCharm is free and should give you what you need to get started with Python. Both PyCharm and IntelliJ are made by JetBrains. IntelliJ is initially focused on Java but you can get plugins for lots of other things. I subscribe to JetBrains' Toolbox: https://www.jetbrains.com/toolbox-app/ and have access to all of their great tools.
Hi, I will give my opinion based on my experience. I have used PyCharm, both community and Professional version. The community has limited functions, like you can't use a Jupyter notebook whereas it's available in the Professional version. PyCharm is slower compared to Visual Studio Code. Also Visual Studio Code is an editor which supports various languages. I myself have used both Visual Studio Code and PyCharm. I feel Visual Studio Code would be better choice. You may as well decide based upon your requirements.
I couldn't imagine using a development tool other than the IntelliJ IDEA Ultimate All Products Pack. A single license allows me to work directly on my server running Ubuntu and/or my workstation running Windows 10 Pro simultaneously. My current project uses HTML, W3CSS, JavaScript, Java, Groovy, Grails, C, GO, Python, Flask, and Rust. For me it's worth every penny of the $150 license fee. And you can try it for free.
I'd personally recommend Visual Studio Code as it gives you the flexibility of working in any language, so long as there are extensions to support it. It gives you the flexibility to learn Python, venture into Java, Javascript, and eventually AngularJS, and potentially mobile applications. It's also free and you can install it on your personal computer. I think Visual Studio Code would serve your intended use case best.
Visual Studio code is easy to use, has a good UI, and a large community. Python works great with it, but unlike some other editors, it works with most languages either by default or by downloading a plugin. VS Code has built in linting, syntax coloring, autocompletes (IntelliSense), and an api for plugins to do there own tooling.
If you starting with Python then PyCharm is better. For Java I would suggest to go with IntelliJ IDEA but people also prefer eclipse so I would say try both and then decide. For JS/Angular/React I would suggest go with VSCode. I personally use it and prefer as its light weight and have good integration with chrome for frontend development.
PyCharm, IntelliJ IDEA are both products of JetBrains. They have a free (limited feature) and paid edition. Eclipse is free. VSCode is also free.
IntelliJ really is the best for Java, I switched from eclipse years ago and never looked back. As for javascript, python and angular either using the standalone products from jetbrains (pycharm for python, webstorm for js) or installing the relevant plugins for InteliJ will be your best bet. Pycharm etc. are really just InteliJ with some additional plugins installed.
All three are great, however, I believe that IntelliJ IDEA's multiple IDE's are slightly more straight-forward and more up-to date than Eclipse. If I had to choose one specifically for Python projects I would go with PyCharm.
Pycharm is all you need to get start coding in python or any of its framework. Its an awesome tool you should give it a try :)
Easy to learn and everything you need
This is a very easy to use tool and gives you the opportunity to start coding right after the installation with almost everything setup automatically by the tool.
From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"
We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.
As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !
I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.
I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.
One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.
Feel free to checkout an example: Cloudbuild Example
I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.
You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.
I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.
If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).
Jenkins is a friend of mine. 😀
There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.
When choosing a tool to help automate our CI/CD, the decision came down to GitHub Actions (GA) or TravisCI. Both are great, but the team has more experience with GA. Given GAs broad support of languages and workflows, it's hard to go wrong with this decision. We will also be using GitHub for version control and project management, so having everything in one place is convenient.
Lightweight and versatile. Huge library of extensions that enable you to integrate a host of services to your development environment. VS Code's biggest strength is its library of extensions which enables it to directly compete with every single major IDE for almost all major programming languages.
I originally chose IntelliJ over Eclipse, as it was close enough to the look and feel of Visual Studio and we do go back and forth between the two. We really begin to love IntelliJ and their suite of IDEs so we are now using AppCode for the IOS development because the workflow is identical with the IntelliJ. IntelliJ is super complex and intimidating at first but it does afford a lot of nice utilities to get us produce clean code.
My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage
file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage
file from my docker container and get the coverage report with #Codecov.
We were long time users of TravisCI, but switched to CircleCI because of the better user interface and pricing. Version 2.0 has had a couple of trips and hiccups; but overall we've been very happy with the continuous integration it provides. Continuous Integration is a must-have for building software, and CircleCI continues to surprise as they roll out ideas and features. It's leading the industry in terms of innovation and new ideas, and it's exciting to see what new things they keep rolling out.
Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.
CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.
And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.
Pros of IntelliJ IDEA
- Fantastically intelligent301
- Best-in-class ide242
- Many languages support190
- Java158
- Fast121
- Code analysis82
- Reliable79
- Out of the box integration with maven, git, svn76
- Plugin architecture64
- Integrated version control61
- Code refactoring support12
- Best java IDE11
- Local history7
- Code Completion6
- Kotlin6
- Integrated Database Navigator6
- Built-in terminal/run tools6
- All5
- Free for open-source development, students and teacher5
- Base for Android Studio5
- Free If you're a Student5
- ERD Diagrams4
- Free4
- Cross platform4
- IDE4
- Database/Code integration4
- Out Of The Box features3
- Column Selection Mode3
- Server and client-side debugger3
- More than enough languages for any developer3
- Typescript support3
- Multicursor support3
- Reformating Code3
- Intuitive3
- Command-line tools3
- Android Integration3
- Vim support3
- Special icons for most filetypes in project list3
- Supports many frameworks3
- Built-in web server3
- Live Templates3
- Scala support3
- Works fine with mac os catalina2
- A lot of plugin2
- Just works2
- Integrated Ssh/Ftp Managers2
- Full support2
- Task managers2
- Diff tools2
- File Watchers2
- Support for various package managers2
- Integrated Code Linting2
- Clean UI2
- Open source2
- So modernised2
- Efficient, one Stop solution2
Pros of Travis CI
- Github integration506
- Free for open source388
- Easy to get started271
- Nice interface191
- Automatic deployment162
- Tutorials for each programming language72
- Friendly folks40
- Support for multiple ruby versions29
- Osx support28
- Easy handling of secret keys24
- Fast builds6
- Support for students4
- The best tool for Open Source CI3
- Hosted3
- Build Matrices3
- Github Pull Request build2
- Straightforward Github/Coveralls integration2
- Easy of Usage2
- Integrates with everything2
- Caching resolved artifacts1
- Docker support1
- Great Documentation1
- Build matrix1
- No-brainer for CI1
- Debug build workflow1
- Ubuntu trusty is not supported1
- Free for students1
- Configuration saved with project repository1
- Multi-threaded run1
- Hipchat Integration1
- Perfect0
Sign up to add or upvote prosMake informed product decisions
Cons of IntelliJ IDEA
- Large footprint required to really enjoy (mem/disc)20
- Very slow16
- Bad for beginners8
- UI is not intuitive7
- Not nearly as many tools to integrate as vs code5
- Constant reindexing5
- Needs a lot of CPU and RAM power4
- Built in terminal is slow3
- Doesn't work that well with windows 10 edu3
- Ruby is a plug in1
- Pesky warnings increase with every release1
- AAD0
Cons of Travis CI
- Can't be hosted insternally8
- Feature lacking3
- Unstable3
- Incomplete documentation for all platforms2