Add support to --depth option to our Git clone StepGroup with Build Type as Git Commit SHA
pending feedback
A
Aesthetic Gecko
When trying to use the Git clone Step, we're trying to use the combo with Build Type as Git Commit SHA and define Depth as 1, but for some reason when we execute the fetch Harness ignore the --depth flag, but if we change the build type to Branch for example, we can see the --depth flag in the logs.
I want to request that the depth option be used when the build type is also Git Commit SHA.
Log In
Canny AI
Merged in a post:
Add commitSha to the list of Run Pipeline Built Type options
M
Minimum Stork
Currently Run Pipeline form allow specifying "Git Branch", "Git Tag" and "Git Pull Request" options. We need to run pipelines from non-HEAD commits for certain scenarions. It's possible later in the pipelines, but makes things messy. Having the possibility to choose "Git Commit SHA" directly would make it much cleaner.
Canny AI
C
Cooing Rook
I will add that this is critical for supply chain security and validating reproducible builds for release engineering
Pranav Rastogi
pending feedback