Hi, That's the point. Even I chose to NOT clean workspace it was happened. See the log below: --- [go] Keeping folder pipelines\xxx\workspace [go] Start to update materials.
[go] Start updating workspace at revision dd9b36482ca1d2a73e032e75770c34f3d0134146 from http://xxxx.git [GIT] Fetching changes STDERR: From http://xxx/mainline STDERR: - [deleted] (none) -> origin/xxx STDERR: 3fc491a5..dd9b3648 xxx -> origin/xxx STDERR: 59726306..3bc01051 xxx -> origin/xxx STDERR: * [new branch] xxx -> origin/xxx [GIT] Performing git gc [GIT] Reset working directory pipelines\xxx\workspace [GIT] Cleaning all unversioned files in working copy [GIT] Cleaning submodule configurations in .git/config [GIT] Updating working copy to revision dd9b36482ca1d2a73e032e75770c34f3d0134146 HEAD is now at dd9b3648 [xxx]:xxx [GIT] Removing modified files in submodules [GIT] Cleaning all unversioned files in working copy [go] Done. --- So I cannot benefit from incremental build behavior :( Regards, Denis Le mardi 1 septembre 2020 à 17:39:05 UTC+2, Aravind SV a écrit : > Hello Denis, > > It depends. GoCD just does a git clean as I mentioned, which shouldn’t > change modified times of your codebase, I mean, of files which haven’t > changed, right? > > If you’ve asked it to clean working directory, it will remove and > re-clone. Otherwise, it shouldn’t change. Of course, if you have multiple > agents, you can’t guarantee that the same agent will pick up your job > across days without using GoCD’s job resources. > > Cheers, > Aravind > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/bae49b12-47fe-49e0-8374-8730bf1bedf1n%40googlegroups.com.
