On 9/6/23 13:21, Uwe Schindler wrote:
The idea is that jenkins runs it after the builds to figure out if something changed in the working copy. At ANT times this was implemented exactly like this, we failed build on Jenkins when the working copy changed. This was especially important before we used SecurityManager to prevent tests writing outside their temporary dirs. We had tests touching files in working copy.
That makes sense, and for Jenkins it sounds like a very good idea. I think that Jenkins should probably explicitly request that check ... having it enabled by default for everyone is not the best idea IMHO.
Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
