Help Center/ CodeArts Build/ User Guide (Ally Region)/ FAQs/ Fetching Code/ Failed to Pull a Submodule and Obtain Its Revision Version By Git
Updated on 2026-01-08 GMT+08:00
Failed to Pull a Submodule and Obtain Its Revision Version By Git
Symptoms
The following error is displayed.
1 2 3 4 5 6 7 8 9 | [2019-07-02 08:29:23.179] ERROR: Command "git submodule update --init --recursive --remote asae-feign" returned status code 1: [2019-07-02 08:29:23.179] stdout: Cloning into 'asae-feign'... [2019-07-02 08:29:23.179] [2019-07-02 08:29:23.179] Error: ERROR: Needed a single revision [2019-07-02 08:29:23.179] Unable to find current origin/develop revision in submodule path 'asae-feign' [2019-07-02 08:29:23.179] [2019-07-02 08:29:23.202] [INTERNAL] : [pluginFrame] step run failed, errorMessage: Could not perform submodule update [2019-07-02 08:29:23.250] [INFO] [Code checkout]: StagePostExecution started [2019-07-02 08:29:23.251] [INFO] [Code checkout]: StagePostExecution finished |
Cause Analysis
The original directory is incorrect. In this example, the directory is asae-feign. This is a Git bug.
Solution
Delete the directory from the code repository, run the git submodule update command again, and run the build task again.
Parent topic: Fetching Code
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot