Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37496

Git sub-modules having a similiar, lengthy path/name as the previous one are silently not initialized/checkedout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • git-plugin
    • Jenkins 2.17, Git Plugin 3.0.0-beta2

      Out build gets prebuilt openssl supplied using git sub-modules, as we build for different architectures we have more than one prebuilt openssl, the first openssl sub-module is setup fine, the second regarding the log output also, but its directory stays completely empty, not even a .git is created, copy pasting the command into a git-shell sets the submodule correctly up. FYI, this project contains 14 sub-modules, each of then is setup correctly, even after the openssl sub-modules, only this second openssl sub-module fails silently.

       > C:\Program Files\Git\bin\git.exe config --get submodule.thirdpartyproducts/openssl/nse/ssl.url # timeout=10
 > C:\Program Files\Git\bin\git.exe remote # timeout=10
 > C:\Program Files\Git\bin\git.exe config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials Jenkins Account Info for http access to git from slave nodes
 > C:\Program Files\Git\bin\git.exe submodule update --init --recursive thirdpartyproducts/openssl/nse/ssl # timeout=45
 > C:\Program Files\Git\bin\git.exe config --get submodule.thirdpartyproducts/openssl/nsx/ssl.url # timeout=10
 > C:\Program Files\Git\bin\git.exe remote # timeout=10
 > C:\Program Files\Git\bin\git.exe config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials Jenkins Account Info for http access to git from slave nodes
 > C:\Program Files\Git\bin\git.exe submodule update --init --recursive thirdpartyproducts/openssl/nsx/ssl # timeout=45

          [JENKINS-37496] Git sub-modules having a similiar, lengthy path/name as the previous one are silently not initialized/checkedout

          Vadym Shkil added a comment -

          Hello, Florian

          Please provide information about Git version that was used for the plugin

          Vadym Shkil added a comment - Hello, Florian Please provide information about Git version that was used for the plugin

          Florian Manschwetus added a comment -

          I tried to find it by checking windows event log, but no trace, maybe some one could give a hint here.
          I just checked for the installer presumably used when installing git last time on the system, it was 2.7.2-64-bit.

          Florian Manschwetus added a comment - I tried to find it by checking windows event log, but no trace, maybe some one could give a hint here. I just checked for the installer presumably used when installing git last time on the system, it was 2.7.2-64-bit.

          Florian Manschwetus added a comment -

          Was caused by an outdated git version installed on the node

          Florian Manschwetus added a comment - Was caused by an outdated git version installed on the node

            manschwetus Florian Manschwetus
            manschwetus Florian Manschwetus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: