search

MarkusGerhart / spray

Automatically exported from code.google.com/p/spray
0 stars 0 forks source link

Split CI builds #92

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
With build#185 we have exceeded the maximum build time of 2000 minutes per 
month for our builds. A build already takes 40 minutes now.

We have to find ways to reduce the build time again, presumably by splitting 
the builds.

For example, the building of the Spray repository takes quite a while, since 
the repository is already > 170 MB large.

Next problem is long startup time, since resolution of the target platform is 
slow. We should consume a local built target platform instead of the remote 
repositories.

Original issue reported on code.google.com by karsten....@googlemail.com on 25 Nov 2011 at 11:34

GoogleCodeExporter commented 8 years ago

Original comment by karsten....@googlemail.com on 25 Nov 2011 at 11:39

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by de.abg.r...@gmail.com on 27 Nov 2011 at 8:22

GoogleCodeExporter commented 8 years ago 
see also 
http://groups.google.com/group/spray-dev/browse_thread/thread/fee6a584d9b51374

things to do:
 * create extra branch (in future own repository) to hold the P2 repository project containing own the 3rd library dependencies
 * introduce new parent pom for P2 repository project and old parent pom
 * switch old parent pom to use build P2 repository from Jenkins build job artifact URL
 * introduce Maven profiles to be able switch between remote P2 repository and local P2 repository (to be able to work off-line locally)
 * investigate means how to configure Git and/or Jenkins to build only the changed Maven projects and their dependent projects (and when found the means apply them)
 * update documentation if necessary

Original comment by de.abg.r...@gmail.com on 27 Nov 2011 at 8:32

GoogleCodeExporter commented 8 years ago 
 * spray-ci-targetplatform: takes 32 minutes, runs midnight and only then when there are changes in the target platform  
 * spray-ci-build: takes 14 minutes, runs when there are changes in the plug-in projects, checks this every 45 minutes           
 * spray-docs-build: takes 5 minutes, runs midnight and only then when there are changes in the docs projects
 * spray-assembly-build: takes 25 minutes, runs midnight and only then when there are changes

For more details to the build jobs the this message:
http://groups.google.com/group/spray-dev/browse_thread/thread/481cee877019fb28

Original comment by de.abg.r...@gmail.com on 13 Apr 2012 at 9:39

GoogleCodeExporter commented 8 years ago 
Good job!

How did you configure that builds are only triggered on changes to specific 
subpaths in the repository?

Original comment by karsten....@googlemail.com on 16 Apr 2012 at 8:53

GoogleCodeExporter commented 8 years ago 
I did not configure that yet, but it is possible - see the attached screenshot.

Original comment by de.abg.r...@gmail.com on 16 Apr 2012 at 11:38

Attachments:

GoogleCodeExporter commented 8 years ago 
Will you configure this later?

Original comment by karsten....@googlemail.com on 16 Apr 2012 at 11:40

GoogleCodeExporter commented 8 years ago 
Yes, this would be reasonable.

Original comment by de.abg.r...@gmail.com on 16 Apr 2012 at 11:45