Vexor: a fresh view on the continuous integration

Vexor overview
13 June 2017   2230

There are a lot of cloud-based continuous integration service for developers, allowing them to test projects. Let's take a look at Vexor, interesting CI service.


Cloud Continuous Integration service. Unlimited parallelism

Continuous integration

Practice of merging all developer working copies to a shared mainline several times a day

Every day developers use CI services, however, most of them are expensive, slow, inefficient and impose greater restrictions on use.

Vexor will suit for those who:

  • Tired of wasting time and money on maintaining a test infrastructure;
  • Haven't got enough resources for a local server for a long time;
  • Don't dare to use cloud CI because it is expensive;
  • Tired of waiting for a queue for the calculation of tests in the usual cloud CI;
  • Really need speed.

Vexor have a fair price (per minute) and unlimited power for everyone. Solution have great russian-speaking support. 

The beginning

Continuous integration is the practice of software development, which consists in performing frequent automated project assemblies to identify and solve integration problems as quickly as possible. Usually this also includes automatic start of tests after each commit.

Why did you need to develop one more, if there is a lot of solutions at today's market? Let's talk about them.

Vexor as an alternative for local testing

Most developers write tests (unit tests or integration tests) and run them locally on their computer, but this approach has several problems. First, the resources of the computer itself are limited, so the tests will start to slow down as their number increases. Secondly, at some point you can simply forget about the tests and stop running them, especially if the tests take more than 10 minutes.

As a result, you make mistakes and bugs fall into production. Vexor also runs tests automatically at each commit: you do not need to remember about the tests, they just work. And if you make a mistake, Vexor will tell you about it. By using the service of continuous integration, you'll improve the quality of your work.

Vexor advanatages over open-source solutions

Some developers use open-source CIs.

Well, let's consider and calculate.

So, for an open-source solution installed on your hardware, you need a good server. Also, the server needs to be administered and your developers will spend time on it or you will have to hire a system administrator.

All this costs can be even greater than the cost of a cloud solution.

In addition, you will spend quite a lot of time installing the solution. In the case of Vexor, you just need to configure your project under CI, then in other cases you will need to configure not only your project, but CI itself.

An open-source solution installed on your hardware needs to be serviced. Once a month, it will fall and you will encounter a lack of support. You will be forced to spend a minimum of 2 to 4 hours of developer time per month. As soon as your team leaves the person who used to be engaged in maintenance, there will be no one to do his work. Usually with an open-source solution, the user gets a headache and extra costs.

Financial side

For some reason, it turns out that for all Continuous integration services need to be paid, even if you did not use them.

When using CI you have to buy a server and pay for it monthly. Or buy a subscription in a cloud solution for a limited amount of allocated resources.

Even if you were on vacation and did not commit anything - you pay for a month, and pay for equipment around the clock. Think, do you work at night? And on weekends? But you pay for a server or resources, which will "spin" your CI.

vexor interface
vexor interface
vexor interface

Vexor is payed per minute for the real use of resources. You pay for only for the minutes that we use to run your tests. There were no commits during the month - the account is zero. You will also be able to see the information about the average check.

You are always limited by the power of your local server, and at some point you start to miss the speed.

Vexor is a cloud service that can simultaneously allocate as much power as you need. In the event that you make 10 consecutive commits, your open-source CI will execute them sequentially. Vexor will immediately allocate 10 servers to you and will do everything in parallel. In this case, you pay only for the minutes that we really spent working with your tests.

Issues, that users of other CI face:

  • limited in resources;
  • experiencing speed problems;
  • pay for a subscription even if you do not use the service;
  • pay to much if your project is still at the stage of growth.

Use Vexor and get rid of these restrictions and unfair price. Connect and receive $ 5 on your account to check out Vexor.

Which CI do you use?

In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day. There are a lot of different continious integration solutions with strong and weak sides.
Take part in the survey of our portal. Which Continuous integration system do you use?

37% (11 votes)
23% (7 votes)
17% (5 votes)
10% (3 votes)
7% (2 votes)
3% (1 vote)
Atlassian Bamboo
3% (1 vote)
Apache Maven
0% (0 votes)
0% (0 votes)
0% (0 votes)
Total votes: 30

Vexor at HighLoad++ 2017

Alexandr Kirillov reported about how to build a cluster to calculate thousands of high-CPU / high-MEM tasks at one of the biggest Russian IT conferences
12 December 2017   5074

The HighLoad++ is professional conference for developers of high-load systems is the key professional event for everyone involved in the creation of large, heavily-frequented, and complex projects.

Main purpose of the event is to exchange knowledge and experience among leading developers of high-performance systems, which support millions of users simultaneously.

Agenda consists of all crucial web development aspects, such as:

  • Large scale architectures,
  • databases and storage systems,
  • system administration,
  • load testing,
  • project maintenance, etc.

This year the conference program will be dazzled with current trends: IoTBlockchainNeural networksArtificial Intelligence, as well as Architecture & Front-end performance.

The 11th HighLoad++ conference took place on the 7th and 8th of November 2017. 

  • 66% of participants work in large companies (of 30+ employees), 
  • 60% earn above the market, 
  • 55% hold leadership positions and have subordinates. 
  • 9% of conference visitors work as technical directors,
  • 12% work as heads of technical departments, and 29% work as lead developers and team leads.

Alexandr Kirillov, CTO at Evrone, had a speech at HighLoad++ 2017 "How to build a cluster to calculate thousands of high-CPU / high-MEM tasks and not go broke"

Alexandr Kirillov at HighLoad++ 2017
Alexandr Kirillov at HighLoad++ 2017
Alexandr Kirillov at HighLoad++ 2017
Alexandr Kirillov at HighLoad++ 2017
Alexandr Kirillov at HighLoad++ 2017
Alexandr Kirillov at HighLoad++ 2017

Our project is a cloud-based CI-service, where users run tests of developed projects.
This year the system of auto purchase of our project purchased 37218 machines (Amazon Instances). This allowed us to process 189,488 "tasks" (test runs) of our customers.

Tests are always resource-intensive tasks with the maximum consumption of processor capacities and memory. We can not predict how many parallel computations and at what point in time it will be. Before us was the task of building the architecture of the system, which can very quickly increase, as well as rapidly reduce the power of the cluster.

All this was complicated by the fact that the resource-intensive calculations did not allow us to use the classic tools AWS or GoogleComputeEngine. We decided to write our own system of automatic scaling, taking into account the requirements of our subject area.

Alexandr Kirillov
CTO, Evrone

At his report, Alexandr told about how they designed and built the architecture of the service, which is the system of automatic procurement of machines.

Additionally, he told more about the main architectural blocks of projects that solve similar problems.