Solano Labs

FAQ

Frequenty Asked Questions about Solano Labs and Solano CI

What does Solano CI do? How does Solano CI work?

Solano CI is a continuous integration and deployment solution, and is available both as a hosted SaaS solution and private virtual appliance. Solano CI automatically and intelligently parallelizes automated software tests to deliver results 10 to 80 times faster than existing solutions. This automated parallelization of a test suite occurs through Solano CI's proprietary schedule-optimizing technology, which uses multiple inputs from test files to calculate the best run time. Solano CI integrates into an existing deployment workflow to deliver faster releases.

What types of languages and test frameworks does Solano CI support?

Solano CI seamlessly supports popular languages including C, C++, Clojure, Go, Java, Javascript, Node.js, PHP, Python, R, Ruby, Scala and the Command Line. The complete language support guide can be found here. In addition to the languages listed, Solano CI also supports any UNIX commands. Documentation on how to run arbitrary commands can be found here.

Can I use Solano CI as a private installation?

Solano CI is available as a private virtual appliance. It is most commonly deployed in a private installation using Amazon's Virtual Private Cloud and secured so that it is accessible only through desired networks. Other deployment models are also available.

The Solano Appliance provides the same performance benefits as the SaaS, but with the ability to implement privately. It is best suited for customers that need strong IP protection, but want to take advantage of Solano CI's blazingly fast automated test infrastructure. This option provides full account management and results in controlled access to different projects within the same appliance instance. The Solano Appliance also automatically handles resource scaling so a development team can have complete control of Solano parallelization while avoiding large infrastructure costs.

What types of performance increases can I expect with Solano CI? How is this performance achieved?

Solano CI will improve the speed of a build length by a factor of 10 to 80 times. The main driver behind this speed up is the Solano CI automated parallelism. Solano is able to dynamically and intelligently distribute tests amongst the resources of your plan to achieve the most efficient execution of a build.

How does Solano CI automatically parallelize my tests?

This automated parallelization of a test suite occurs through Solano CI's proprietary schedule-optimizing technology, which uses multiple inputs from test files to calculate the best run time.

Do I need to provide access to all of my repositories?

Solano CI allows you to control what repositories will be used by the system, so you can customize the permissions for your organization as you see fit.

Can I still use Solano CI if my code cannot leave my firewall?

Yes you can! Many of our current customers have this requirement today.

How do I deploy from Solano CI? Where can I deploy?

Solano CI supports first-class deployment into many commonly-used platforms including AWS, Engine Yard, and Heroku. Learn more about post build tasks here.

How does Solano CI integrate with my development workflows?

Solano CI easily and seamlessly fits into your current development workflow. Solano's ease of implementation and multiple third party integrations allow engineering teams to quickly insert Solano CI as their primary build tool.

How Solano CI measures code coverage?

Solano CI has integrated with CodeClimate to provide code coverage for Ruby on Rails, Javascript, and PHP.

What does it take to backup Solano CI?

Nothing! Solano CI automatically creates daily backups for all our customers.

How is Solano CI better than Jenkins?

Solano CI's main differentiator is its performance over Jenkins CI. Solano's automated test parallelization makes performance speed ups easier to achieve than Jenkins. A majority of Solano CI customers switched from a Jenkins build system to Solano CI because it reduced their build times from hours to minutes. Here are some examples of performance increases:

  • A 15 minute Ruby build in Jenkins CI was reduced to 41 seconds in Solano CI
  • A 1.5-hour Java build in Jenkins CI was reduced to only five minutes in Solano CI
  • A five hour queue time for commits in Jenkins CI, reduced to five minute queue time in Solano CI with multiple parallel builds

Another strong differentiator between Jenkins CI and Solano CI is the amount of maintenance and support required to optimize the systems. Jenkins CI can require a full team to implement, support, and maintain. Solano CI, on the other hand, requires zero maintenance. Much of the Solano CI system is automated and the items that do require attention are maintained and updated by the Solano CI team. As a result, there is no more CI downtime due to plugin updates or additional time spent administering backups.

Further, in comparing technical assets between Jenkins CI and Solano CI, the Solano CI solution excels in the following:

  • Safe parallel execution and dynamic task distribution
  • Painless, revision-controlled setup: fast self-service setup for new projects and branches, compact YAML configuration file that lives in the code repository
  • Easily scalable system with optional 24/7 support