What automated build systems do you use? How long are your builds?

In my current project, there are 5 separate automatic assemblies that start after each registration:
Unit tests (exits from the database): ~ 6 minutes
Integration tests (only for the database): ~ 40 minutes
Website 1 UI (Selenium, from UI to DB ): ~ 80 minutes
Website 2 UI1 (Selenium, from UI to DB): ~ 90 minutes
Website 2 UI2 (Selenium, from UI to DB): ~ 100 minutes

We use Maven2, JUnit and Selenium.

One of the strategies that I think will significantly reduce integration testing time is to get as many integration tests as possible in Unit Tests and just use the integration project to test database stability.

I wonder what strategies you found that helped reduce the build time of large projects.

+3
source share
8 answers

We have about the same build time, maybe a little less in selenium (I would say about 3x50 minutes of run time, the same site tests on firefox, i.e. for opera). Our solution was to release more CPU on it, and we have a bamboo cluster environment with a total of 7 dual-core nodes.

We found that running selenium-rc and a browser in a separate box from the web-container / selenium test significantly improves the battery life of selenium.

+2
source

GNU make . 2 30 .

+1

: 1

0

, . , , . , , , , , .

0

Hudson #, Windows, - . 800 MSTest.exe 12-15 . , MSTest - slooow.

, , MSTest, , , .

: env, -, Windows, .

0

Erlang - , .

0

Team City.

, , - , , . 20000 , , . , RAM- ( ) .

, , 4 , NCover, . , . , , .

RAM-RAM . . CVS , , " ". , , , .

"" , . ( ) . , - . , . , " ", "" , , , , . , .

For the future, the longest automatic build we have (for another project) sometimes takes more than a day, although, fortunately, this is not one that needs to be run regularly.

0
source

My current client, unfortunately, has BuildForge (from ClearCase SCC): one to three days. Seriosuly. I really don't know what they are doing in the assembly or why it takes so long.

0
source

Source: https://habr.com/ru/post/1703004/


All Articles