VexorContinuous integration

Vexor updates for last 12 month

New Vexor features added during last 12 months
26 May 2017   1641

Creating an arbitrary number of companies

The ability for users to create an arbitrary number of their companies and invite new users to them;

Billing changes

Vexor

Cloud Continuous Integration service.

  • Monthly free 100 minutes are now canceled;
  • 5$ bonus when payment card is binded;
  • Added "Wizard" during the installation process; 
  • Payment card binding is now mandatory;

Changes in the language pack collector

Abandoned aptly (deb package collector) in favor of deb-s3

PHP support:

  • Latest version of PHP is now supported;
  • Language is now added to Settings and interface;
  • Language support is now added at the task launch level (linking the startup script);

Service versioning

The ability to connect different versions of third-party services (postgresql, mongodb, elasticsearch etc ...) is now added

Possiblity to sign up for a technical interview 

When adding a project, it is now possible to sign up for a technical interview via the service calendly.com.

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?

Vexor
37% (11 votes)
CircleCI
23% (7 votes)
Jenkins
17% (5 votes)
TravicCI
10% (3 votes)
GitlabCI
7% (2 votes)
Teamcity
3% (1 vote)
Atlassian Bamboo
3% (1 vote)
Apache Maven
0% (0 votes)
CodeShip
0% (0 votes)
Semaphore
0% (0 votes)
Total votes: 30
Vexor

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   4557

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: IoT, Blockchain, Neural networks, Artificial 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.