All geek questions in one place

Delphi Build Server: Find out which projects are affected by commit

I am currently trying to improve the performance of our assembly. A standard assembly queued after each commit (svn) takes about 40 minutes. If we already have an assembly in the queue, we are not adding another one. Thus, each assembly has changes in 1+ commit. Since the commit (s) probably did not make any changes to all projects, the build time can only be reduced by restoring the affected projects.

I have no idea how to find out what projects need to be built. Is there a way to reliably find out what affected the commit (s) that triggered the assembly? At first I thought about going through .dpr files and checking for changes in the files referenced, but not all files are listed there, since we also use the search path ...

If this does not happen, is there at least a way to find out if the project is not appropriate ? I honestly don’t know how to approach the problem ...

+4
source share
2 answers

The following is not an “answer” to your problem, but may be help in further thoughts.

, (,.RC .Inc ), , , , , , " ". .

, , , , , DCU, .

, .Pas .DCU, , DCU.

, , X% .Pas .

, , , . , , A, Z, , A , Z . , , , , .

, .Pas USES-, , .Pas , . DCU .

Btw, , , , Prolog ( Amzi Prolog Delphi, ).

+2

, RAM-, . Ant . , x4 ( ).

. :

  • , (.dpr) .pas , . . .

  • dcc32.exe commit. , . - , , .

+1

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

More articles:


All Articles