
When used in conjunction with GIT and any IDE that supports it is very easy to automate tasks of the continuous development pipeline and with that free mental resources to actually work in the idea that you want to implement thru code since you can get notifications whenever something relevant for you is getting changed. Review collected by and hosted on G2.com.
In a perfect world, Travis will work on its own without minimal human interaction, and with experienced teams that is usually the case but when dealing with new developers or with those that are not accustomed to the CI/CD pipeline it is kind of not intuitive and takes some time to get used to it. Review collected by and hosted on G2.com.
Travis CI is easy to use and save much time for configuration . Travis CI is suitable for the open source , private projects and supports private builds . I used Travis for testing and developing environments . It helped me avoid unexpected issues , encounter and handle the problems such as : bugs and crash.
Especially , Travis is easy to interact all information with Github platform .
I saved much time with Travis . All is smooth . Review collected by and hosted on G2.com.
It sometime takes more time to build . I don't like product design on Travis CI . Review collected by and hosted on G2.com.
Travis works great for CI/CD pipelines. It's easy to configure and has great integrations with tools you are probably already using like github. It's also compatible with many popular languages. Review collected by and hosted on G2.com.
Travis has had some outages and strange behavior in the past. Occasionally builds break due to aggressive caching - there might be a way to disable that though. Review collected by and hosted on G2.com.
It automate the build process and handle test cases. You can run test cases on mac and linux both at the same time. Configuring travis is easy using lightweight YAML file. We don't need to setup our own server to run it. It also provide free support for public repos. Review collected by and hosted on G2.com.
When it comes to private repos the pricing is bit high compared to other providers like CircleCI. Third party integration is needed for configuring customization such as linter etc. Review collected by and hosted on G2.com.
Ready and easy to use, you don’t need any extra configuration like other CI tool like Jenkins. simply integrate GitHub or version control system, when ever you push the code its tested and integrated. Multiple jobs allow you to run and test simultaneously on different environment and OS. Free for your public projects, you don’t have to pay for your test and open source projects. You don’t have to maintain hosting server, Travis CI handle and maintain updates and hosting server. Plugin and integration with third party tools are available but its limited. Review collected by and hosted on G2.com.
Travis CI is not extensible and high customizable like Jenkins because of its limited plugins and third-party integration. You have to pay for private repositories unlike Jenkins which provide unlimited private repositories. Its not open source which is not good for highly sensitive projects whereas Jenkins is a open source. Review collected by and hosted on G2.com.
-Travis Continuous Integration is a tool for developers to test their pre-released Android or iOS application in possible every environment and device compatibility.
- Travis Continuous Integration is open source and also available in paid version.
- Travis Continuous Integration help you deploy your test application in various devices compatible with
various hardware configurations.
- Basically Travis Continuous Integration is testing your test application stored in GitHub Repository
doesn't matter that repository is Private or Public and gives you best possible results and help you a
lot for solving bugs. Review collected by and hosted on G2.com.
- For using Travis Continuous Integration, one should have GitHub account. Person can only sign up in
Travis CI using GitHub only.
- Travis CI is taking very long time to test application which can be sometime very irritating. Review collected by and hosted on G2.com.
Integration with github open source projects. Every time a push or merge takes place in a git repo that has a travis configuration, tests a run automatically. When the tests complete travis can automatically generate a built and / or deploy the project to a live server depending on your travis configuration. Review collected by and hosted on G2.com.
Travis is only free for public github projects, will require a payment plan for private repos. Review collected by and hosted on G2.com.
It "just works". The build logs can be viewed in real time (live tail). Lots of useful integrations. travis-ci.org is very popular for open source projects so many fellow developers will already be familiar with it. Review collected by and hosted on G2.com.
The documentation could be better; there's no reference for the travis.yml file so you have to read/search the full docs to find what you're looking for. The pricing is on the high side. Review collected by and hosted on G2.com.
I really liked using Travis CI when I wanted to deploy changes to the open-source project I was working on - it was very easy to pinpoint which exact tests failed and where I had to go back to fix them before deploying. Review collected by and hosted on G2.com.
It takes a very long time to run through the tests for some reason - the project I worked on was fairly small so I wasn't sure why it took 2 - 3 minutes just to run tests (this also slowed down our productivity in general, although I know there were other ways to run tests running it on Travis was visually the best to see what the outputs were). Additionally, even if the tests did all pass, there were still many moments that the tests didn't catch which made our website go down. Review collected by and hosted on G2.com.
I knew the tool thanks to the Github platform, it seemed extraordinary the integration that these two platforms have, just by doing 'push' to my repository I could automate validation, integration and deployment tasks with only 1 command. In addition to this you can integrate the tool with Telegram Bot to be aware of the status of the deployment of the application. This is a good tool to use next to github. Review collected by and hosted on G2.com.
when you want to do mass deployment process, the configuration becomes a bit complex, since it does not provide tools to perform these processes from the web interface, you must have advanced technical knowledge if you want to achieve good results. Review collected by and hosted on G2.com.
Integrating Travis into a project is essentially painless. Create a simple config file and Travis takes care of the rest, even if your app needs to be built via Docker containers or other modern delivery mechanisms. Review collected by and hosted on G2.com.
If you have a lot of devs and a lot of projects, sometimes builds will get held up in a queue. Review collected by and hosted on G2.com.
I like that it is an environment where you can essentially set anything up like you would locally via your terminal. Using Travis CI also keeps everyones code constant with the linter rules in place, and in the beginning helped with learning what in the code needs to be done before deploying it. Review collected by and hosted on G2.com.
I dislike that if a Pull Request was not properly merged with the master branch that Travis CI uses to check against it will fail. So if the references don't match it just breaks, but maybe its just my works setup with Travis. Sometimes Travis feels like it takes longer than it should, but I think this is situational. Review collected by and hosted on G2.com.
It integrates well with GitHub, automatically running tests for new commits, so we don't have to manually ourselves. Forces users to ensure their code is tested before merging with master. The integration is fairly simple with just a configuration file. Granted, if you have a more complex build, this integration can be more complex. Their documentation is fairly extensive though which is good. Review collected by and hosted on G2.com.
The UI can be a bit clunky to use and the view for builds could load faster. It also can get pricey for the paid versions for a startup. If you have multiple team mates collaborating, the list of builds waiting can queue up meaning you're waiting potentially hours (if each build takes 30min). Review collected by and hosted on G2.com.
Awesome to run unit and integration tests after each commit and can be used with Github easily with few configurations. Review collected by and hosted on G2.com.
Don't have thing to dislike just learn how to configure. Review collected by and hosted on G2.com.
Most of the open source libraries use TravisCI - that's what makes TravisCI pretty - love how they support open source community. Review collected by and hosted on G2.com.
Had some troubles time ago to set up a private repository - not sure how it's working for private one now on - but it was so complicated awhile ago. Review collected by and hosted on G2.com.
Travis has been a very good experience to me compared to using other CI. We went from CircleCI to this because of it's simplicity, the config is very easy and the documentation is really good for the newcomers to using CI's. Review collected by and hosted on G2.com.
The UI I think is the weakest part of Travis, compared to some other CI's, it'd lacking in that front, but not in very wide gap though. Something clean and really modern would do. Review collected by and hosted on G2.com.
It's straightforward to integrate with GitHub. Generally all documentation is clear and easy to understand. Review collected by and hosted on G2.com.
Sometimes (4/10 builds) will be stuck on the queue for an extremely long time. Review collected by and hosted on G2.com.
Travis CI makes it easy to setup Continuous Integration services for projects hosted on Github. For open-source, public projects on Github, the service is completely free (travis-ci.org is for open-source projects, travis-ci.com for commercial).
The service allows building and testing with a large variety of supported languages.
Using a "build matrix" the code can be tested under different language versions.
After a successful build, the code can be directly deployed. Travis works well together with Heroku (heroku.com) for this purpose. Review collected by and hosted on G2.com.
With very large test suites or very complex dependencies, builds can sometimes take some time. However, this is in inherent problem with Continuous Integration services, not limited to Travis. Review collected by and hosted on G2.com.
It has integration with Github's web hooks and with Slack. It's very ease to use and the builds are fast. Review collected by and hosted on G2.com.
The service has been very intermittent in the last couple of months and that affects our development workflow. Review collected by and hosted on G2.com.
I love the integration with Github, when it adds visual information to a pull request to let you see how a build is progressing and what problems it has (if any).
I love that it's very easy to configure without any hassle.
I love the badge you can put on a website or in your readme to show whether the build is passing or not.
I love the fact that it has built-in support to deploy to other vendors, like Heroku Review collected by and hosted on G2.com.
Difficult to build native .Net projects without using Mono, but that's more of a disappointment with the .Net build ecosystem and not a fault of Travis as such.
Also, pricing - I've only had need to use the free open-source tier, as all the projects I've worked with are open source, but the price of the first paid tier ($129 per month!) is, for me, quite prohibitive and really puts me off making the leap to pay for it.
If there was an even cheaper tier, for example one which was say $30 per month with 1 concurrent job and limited minutes per month, but allowed private repositories, then I would probably make that jump. I just feel there's a big gap in the entry-level pricing tiers. Review collected by and hosted on G2.com.