You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We upgraded the git plugin from 2.2.7 to 2.2.9 and symlinks stopped working. Previously when cloning a repository that contained symlinks they'd be checked out as symlinks, now they are checked out as files.
I think this may be related to this commit which updated jgit version:
The filesystem support to determine if a filesystem supports symlinks is in a separate module which isn't used by the git plugin but the code to determine if symlinks are supported (which writes that info to the local .git/config) is in the main jgit module. What we're seeing is that when hudson clones the reposiotry it sets core.symlinks to false in .git/config.
The text was updated successfully, but these errors were encountered:
Same issue here with plugin 2.2.14. Had to downgrade to 2.2.7 to make it work again. 90% of our projects use symlinks. Sticking to 2.2.7 is no long-term option for us. Didn't want to migrate to Jenkins (where this specific bug is fixed for a long time now). May have to reconsider...
We upgraded the git plugin from 2.2.7 to 2.2.9 and symlinks stopped working. Previously when cloning a repository that contained symlinks they'd be checked out as symlinks, now they are checked out as files.
I think this may be related to this commit which updated jgit version:
46a614e
Between jgit 3.2.0 and 3.3.1 some sort of symlink support was added in these commits:
https://github.com/eclipse/jgit/commit/078a9f60664fee1f7e85f0c3ab3fd067c0f674cc
https://github.com/eclipse/jgit/commit/dd3181603e0a42c46299c25cede66fdbd67da518
The filesystem support to determine if a filesystem supports symlinks is in a separate module which isn't used by the git plugin but the code to determine if symlinks are supported (which writes that info to the local .git/config) is in the main jgit module. What we're seeing is that when hudson clones the reposiotry it sets core.symlinks to false in .git/config.
The text was updated successfully, but these errors were encountered: