lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uwe Schindler <>
Subject Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Date Wed, 17 Feb 2016 20:38:13 GMT
No nitpicking, please. I just wrote that it resets checkout to pristine state. In fact the
option in Jenkins does what it should. We don't need to discuss what it does behind scenes.
I don't care about Gits horrible command line. :)

In fact Policeman uses Eclipse JGit to do the same. You don't see any command line in log
outputs - that's the best to me. ASF Jenkins prints tons of gitshit, just look into logs!


Am 17. Februar 2016 20:59:25 MEZ, schrieb Dawid Weiss <>:
>> I will check the Jenkins Config of this Job, maybe it is missing the
>extra GIT checkout option ("git reset").
>git reset actually only resets the tracked files that differ from the
>head. What you're looking for is two things:
># resets any staged changes (not that there should be any on jenkins,
>but for local repos there may be)
>git reset --hard
># clean ANY files not tracked in the repo -- this effectively restores
>pristine state.
>git clean -xfd .
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
View raw message