Mark Waite edited a comment on Bug JENKINS-23694

The job I had defined (initially running on Linux), including the "Clean before checkout" added to the git SCM "Additional behaviour" section of the job definition. With that added to the job definition, I see:

git submodule foreach --recursive git clean -fdx

Full console output:


Started by user anonymous
Building remotely on jessie64a (Debian amd64-Debian linux testing Debian-testing amd64-Debian-testing amd64) in workspace /var/lib/jenkins/wheezy64b-slave/workspace/JENKINS-23694-clean-fails-with-submodules-present
 > git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
 > git config remote.origin.url git://github.com/boostorg/boost.git
Cleaning workspace
 > git rev-parse --verify HEAD
Resetting working tree
 > git reset --hard
 > git clean -fdx
 > git submodule foreach --recursive git reset --hard
 > git submodule foreach --recursive git clean -fdx
Fetching upstream changes from git://github.com/boostorg/boost.git
 > git --version
 > git fetch --tags --progress git://github.com/boostorg/boost.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit}
Checking out Revision 85b8813a1cf348ea84a0f99ed5319f39c140900f (origin/master)
 > git config core.sparsecheckout
 > git checkout -f 85b8813a1cf348ea84a0f99ed5319f39c140900f
 > git rev-list 85b8813a1cf348ea84a0f99ed5319f39c140900f
 > git remote
 > git submodule init
 > git submodule sync
 > git config --get remote.origin.url
 > git submodule update --init --recursive
[JENKINS-23694-clean-fails-with-submodules-present] $ /bin/sh -xe /tmp/hudson1079411972338520157.sh
+ date
+ date
Finished: SUCCESS
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.

Reply via email to