Marg Travis CI

Marg ERP 9+

Travis CI is a free and open source Continuous Integration tool that provides support for many built configurations, including Node.js, Java, and PHP. It is built for teams and projects of all sizes and supports more than 20 languages by default. The tool uses virtual machines to build the application and allows for parallel tests. Users get notifications via email, Slack, or HipChat. Travis CI is considered to be a very powerful API and also a command line tool. It has pre-installed database services and allows for a very quick setup. Using Travis CI is simple and effective. Users can login via GitHub, run Travis CI to test a project, and reports are generated. The tool can even scale up depending on the number of developers using it, be it 10 or even 1000.

Pricing of Marg ERP-Pharmaceutical Industry Software

Pricing plans

Introduce pricing plans

Simple, transparent pricing that grows with you. Try any plan free for 30 days.

Bootstrap

USD 69.00 //Month

USD0.00

Perfect for your business requirements and platform usage.

BOOK A DEMO
WHAT YOU WILL GET
  • 1 Concurrent job
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators
  • 1 Concurrent job
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators

Startup

USD 129.00 //Month

USD0.00

Perfect for your business requirements and platform usage.

BOOK A DEMO
WHAT YOU WILL GET
  • 2 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators
  • 2 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators

Small Business

USD 249.00 //Month

USD0.00

Perfect for your business requirements and platform usage.

BOOK A DEMO
WHAT YOU WILL GET
  • 5 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators
  • 5 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators

Premium

USD 489.00 //Month

USD0.00

Perfect for your business requirements and platform usage.

BOOK A DEMO
WHAT YOU WILL GET
  • 10 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators
  • 10 Concurrent jobs
  • Unlimited build minutes
  • Unlimited repositories
  • Unlimited collaborators

Key Specification

Other Categories:
Deployment: Cloud Hosted
Customer Support: Business Hours,Online (Ticket)
Customization: No
Languages Support: English

Who uses Travis CI

SMEs
SMEs
Enterprises
Enterprises

Company Details

  • Company Name: Travis CI
  • Headquarter: Berlin , Berlin Germany

Travis CI Description

Key Features & Specifications

  • Reporting and Visualization
  • VCS Integrations
  • Scheduled Deployment
  • Automated Deployment
  • Automated Integration
  • Multi Programming Languages
  • Auto Scaling
  • Plugin Support

Travis CI Video

Keka HR Payroll Platform Screenshots

User Reviews

WRITE A REVIEW
quotes

What do you like best?

Easy to use and and free for open-source projects.

Can test across a wide magnitude of versions/technologies by using Travis Matrices.

Saves developers time by running large test suites on a remote system so developers can continue doing what they do best without halting to wait for their own machinery to run the test suite.

What do you dislike?

Builds can take a while to start however their new container-based infrastructure is aiming to fix this issue.

Limited to just GitHub repositories.

What problems are you solving with the product? What benefits have you realized?

Testing software in accordance to GitHub Flow to check pull-requests before merging into the master branch. Assures quality and in accordance with code coverage and maintainability monitoring services can accelerate software development.

- Ben E

quotes

What do you like best?

Travis really shines on their language support as well as capabilities. Its UI is nice, very nice, with a dashboard that allows you to check the status of 6 or 7 projects at the same time (depending on your screen size and resolution) and their status.

What do you dislike?

The real downside of Travis is that you need to add a file to your project to start using it. This is mandatory today and this file can be quite complex. This leads to some "useless" commits just to correct some configuration in this file and check if it works on the Travis dashboard. Once you tweak the file correctly, you don't have problems anymore with it.

Recommendations to others considering the product:

Travis is being used in many open source projects already which is a very good sign. I really like it but today I would prefer to used something like Drone.io for my CI. I haven't introduce CI or CD into my workflow as to take time from my development schedule and Travis fits quite nice (once you configure it correctly).

Travis is very well suited for open source projects as it has direct Github support with a simply click so, if you are it the open source community, give it a try.

What problems are you solving with the product? What benefits have you realized?

I use Travis in my open source personal projects as my main CI workflow. I mainly use it in the most common way: to check unit tests that I have on the project every time I made a push to Github and feel sure that I haven't broken anything.

- Mario C

quotes

What do you like best?

Travis really shines on their language support as well as capabilities. Its UI is nice, very nice, with a dashboard that allows you to check the status of 6 or 7 projects at the same time (depending on your screen size and resolution and their status.

What do you dislike?

The real downside of Travis is that you need to add a file to your project to start using it. This is mandatory today and this file can be quite complex. This leads to some "useless" commits just to correct some configuration in this file and check if it works on the Travis dashboard. Once you tweak the file correctly, you don't have problems anymore with it.

Recommendations to others considering the product:

Travis is being used in many open source projects already which is a very good sign. I really like it but today I would prefer to used something like Drone.io for my CI. I haven't introduce CI or CD into my workflow as to take time from my development schedule and Travis fits quite nice (once you configure it correctly.

Travis is very well suited for open source projects as it has direct Github support with a simply click so, if you are it the open source community, give it a try.

What problems are you solving with the product? What benefits have you realized?

I use Travis in my open source personal projects as my main CI workflow. I mainly use it in the most common way: to check unit tests that I have on the project every time I made a push to Github and feel sure that I haven't broken anything.

-

quotes

What do you like best?

It has integration with Github's web hooks and with Slack. It's very ease to use and the builds are fast.

What do you dislike?

The service has been very intermittent in the last couple of months and that affects our development workflow.

Recommendations to others considering the product:

You should consider that this service can be very unstable.

What problems are you solving with the product? What benefits have you realized?

Running tests and developing to stage automatically whenever a commit or a merge is done in Github.

- User in Education Management

quotes

What do you like best?

I have been using it for only for a few weeks and the best thing is the ease of use of the travis.yml file, my framework/language is well supported, mind you. It works very well with my ruby projects and good enough with c++. The web-ui is nice enough that builds can be tracked easily. Also a good thing, the badge that can be included anywhere (most commonly in github readme.md) to track most recent build status. Another good thing is the github hook, as with every push build is triggered automagically.

What do you dislike?

Language support. One, it did not support vala projects so that was it. Two, for c++ projects to use c++11 with g++ or clang, you have to jump through a lot of hoops, change your travis.yml file and wait for something to break. Another big problem is the wait time, it takes a LOT of time for the build to start after making the latest push, this is where appveyor is better. So, if you are using travis as your only test system, don't. Windows support is also not present currently so that's a problem for VS projects.

Recommendations to others considering the product:

Travis is one of the most popular CI systems out there. Although not as easy as one click, one can easily set up a project to use travis in well under an hour, for well supported systems. I recommend setting up a small test project to try it. If travis meets your specs, then go for it as it is well integrated.

What problems are you solving with the product? What benefits have you realized?

The need to state build status explicitly in every push is gone. I can simply push to github and it will let others browsing my project know if this version is usable or if they have to revert to a previous release.

- Tauseef R

Keka HR Payroll Platform Key Clients

Frequently asked questions

Everything you need to know about discovering, comparing, and choosing the right AI software for your business.

Travis CI has 4 plans,

  • Bootstrap USD 69.00 /Month
  • Startup USD 129.00 /Month
  • Small Business USD 249.00 /Month
  • Premium USD 489.00 /Month

Travis CI is the Continuous Integration Software used for the below functionalities.

Top 5 Travis CI features

  • Reporting and Visualization
  • VCS Integrations
  • Scheduled Deployment
  • Automated Deployment
  • Automated Integration

Travis CI provides Business Hours,Online (Ticket) support.

Travis CI is allowed 0 Days Free Trial.

Travis CI provides Help Guides,Blogs for the software training.

Need Help Selecting
the Right AI Solution?

Speak with our team for tailored recommendations and insights to accelerate your AI adoption.

ai-help-img