The -C option changes the Git working directory and it is used in GitFileTree on general level. The main question that we need to answer is what version of Git (or libgit) will be supported and then take decision if we should update slaves or modify our code. The main problem are the long-term supported Linux distributions like Debian or CentOS. -- Pavel 2016-10-21 15:39 GMT+02:00 Nicolas Passerini <npasserini@gmail.com>:

So what is the path to go? Shall we update the slaves to use the newer version or should we see how to remove that option?

BTW, the -C option is in which git command?

2016-10-21 11:20 GMT+02:00 Pavel Krivanek <pavel.krivanek@gmail.com>:

...

Hi,

we have a problem with current MonticelloFileTree (and Iceberg) on our CI slaves because it requires option -C that was introduced in version 1.8.5 or something like so but our slaves have older Git versions (1.7).

-- Pavel

On 21/10/2016 15:04, Damien Pollet wrote:

On 21 October 2016 at 15:47, Pavel Krivanek <pavel.krivanek@gmail.com <mailto:pavel.krivanek@gmail.com>> wrote:

The main problem are the long-term supported Linux distributions like Debian or CentOS.

Even Debian stable has git 2.1 so I'd say it's a non-problem.

See git's release dates (albeit via wikipedia) https://en.wikipedia.org/wiki/Git Both 1.7 and 1.8 are unsupported as is 2.1 Current version is 2.10 -- Mark