Just want to share our final outcomes
1. Use snapshot build during development phase
2. At release candidate phase, switch jenkinsfile to release mode
* For small projects, use version less Maven continuous deliver
friendly,
* For large projects, use versions-maven-plugin to change version in
all poms at pre-build
* Automate the process to tag the final RC (we deploy a
build.properties to maven repo at each build, use its info to tag the SCM)
Whenever, the startup performance issue for large project is fixed, we will
switch to full version less build
-Dan
On Sun, May 14, 2017 at 7:23 PM, Dan Tran <dant...@gmail.com> wrote:
> I also noticed it takes about a minute for the build to roll after this
>
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
>
> This is not a good news for local dev build
>
> here are 2 time summaries running 250+ modules with skipTests and 4 thread
> smart builder. The first one does not use <version>${revision}</version>
>
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 04:05 min (Wall Clock)
> [INFO] Finished at: 2017-05-14T19:16:32-07:00
> [INFO] Final Memory: 680M/2078M
>
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 05:56 min (Wall Clock)
> [INFO] Finished at: 2017-05-14T19:11:00-07:00
> [INFO] Final Memory: 1726M/3561M
>
>
> -D
>
