Jenkins isn't designed to build from scratch. From what you describe, Jenkins should actually already do what you like by default. If available, Jenkins will launch new builds on the same previously used slave.
In this case, you should find a workspace where there's no reason what you are currently doing with would not work. Le 9 oct. 2013 17:25, "D Soa" <[email protected]> a écrit : > I have an existing Ant build that uses the <depend> task to keep track of > dependencies and compile source files if depenencies have changed from the > previous build. This works great for incremental builds and speeds up the > build considerably. > > Jenkins appears to be designed more for "build from scratch", creating a > new build output directory each time. > > How can I accomplish an incremental build with Jenkins where the output > directory is reused? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
