Closed pramodk closed 1 week ago
✔️ 52e0dd93a518e90e4bc247cb6adc5699539212ba -> Azure artifacts URL
Logfiles from GitLab pipeline #221597 (:white_check_mark:) have been uploaded here!
Status and direct links:
✔️ 52e0dd93a518e90e4bc247cb6adc5699539212ba -> Azure artifacts URL
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 67.28%. Comparing base (
df21c81
) to head (da8d5f1
). Report is 5 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Logfiles from GitLab pipeline #221702 (:white_check_mark:) have been uploaded here!
Status and direct links:
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
✔️ da8d5f187b1afa4cee3d89a277670c19fcab3cdd -> Azure artifacts URL
Logfiles from GitLab pipeline #221889 (:no_entry:) have been uploaded here!
Status and direct links:
Closest is checking out branches with git clone --branch <branch_name>
, but they really do mean branch, not tag, and not commit, only branches.
--depth
This option is valid for add and update commands
Why don't we init submodules with update
i.e. git submodule update --init --recursive --depth N
?
We already use git submodule update --init
, see here:
execute_process(
COMMAND ${GIT_EXECUTABLE} submodule update ${UPDATE_OPTIONS} --init -- ${path}
COMMAND ${GIT_EXECUTABLE} submodule update ${UPDATE_OPTIONS} --init -- ${path}
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
RESULT_VARIABLE ret)
RESULT_VARIABLE ret)
From what Pramod posts, it's plausible that he's running on BB5 without loading a non-ancient version of git
.
Without this, if I try to use these options, I get: