jenkinsci / jenkinsci/workflow-scm-step-plugin
[JENKINS-67059] git lfs checkout log info improvement
- Dominant language
- Java
- Stars
- 43
- Forks
- 72
- Avg merge
- 10h 35m
- Merged PRs (30d)
- 2
Description
We have a Git Repo with Git LFS running but in the checkout step we didn't included the GitLFSPull extension.
The log information was like a timeout:
git checkout -f 2681d96540445a86776443542a2ea3c6ad16cd81 # timeout=10
ERROR: Timeout after 10 minutes
After adding the extension it was possible to make the checkout without a problem.
I suggest a change in the logs if it is possible because checkout was done, only the files with LFS were not.
After including the GitLFSPull extension log info was:
> git checkout -f 2681d96540445a86776443542a2ea3c6ad16cd81 # timeout=10
> git config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials xxxx
> git lfs pull origin # timeout=10
Suggestion:
Log like "ERROR: Timeout after 10 minutes. Check GitLFSPull extension if it is activated"
---
Originally reported by harryssuperman, imported from: git lfs checkout log info improvement
Raw content of original issue
We have a Git Repo with Git LFS running but in the checkout step we didn't included the GitLFSPull extension.
The log information was like a timeout:
git checkout -f 2681d96540445a86776443542a2ea3c6ad16cd81 # timeout=10
ERROR: Timeout after 10 minutes
After adding the extension it was possible to make the checkout without a problem.I suggest a change in the logs if it is possible because checkout was done, only the files with LFS were not.
After including the GitLFSPull extension log info was:
> git checkout -f 2681d96540445a86776443542a2ea3c6ad16cd81 # timeout=10
> git config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials xxxx
> git lfs pull origin # timeout=10
Suggestion:
Log like "ERROR: Timeout after 10 minutes. Check GitLFSPull extension if it is activated"
- environment:
Jenkins 2.249 , Git 2.26, Git Plugin 4.3.0 , Pipeline: SCM Step 2.11
Contributor guide
Research direction
Start at the checkout step and the GitLFSPull extension handling, focusing on where the checkout timeout is reported. Reproduce or inspect the described Git LFS checkout scenario and update the logging so it distinguishes missing LFS retrieval from a checkout timeout; verify the resulting message with the relevant plugin tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100