On Wed, Oct 9, 2013 at 10:24 AM, D Soa <[email protected]> wrote:
> 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?
Normally that would be controlled by the options for your VCS
checkout. At least with subversion you get some choices about how
much to keep/update between runs. If you have multiple slaves,
Jenkins will normally use the one where the job was built previously
but various circumstances can make it pick a different on.
--
Les Mikesell
[email protected]
--
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.
