Hi James
On Sun, Jan 12, 2025 at 4:29 PM James Nord wrote:
>
> I Michael,
>
> if the reason you are needing to clone / checkout via sh is due to passing
> some flags like ` --filter=tree:0` then I thought you would be able to
> implement that by extending
> https://javadoc.jenkins.io/plugin/g
I Michael,
if the reason you are needing to clone / checkout via sh is due to passing
some flags like ` --filter=tree:0` then I thought you would be able to
implement that by extending
https://javadoc.jenkins.io/plugin/git/jenkins/plugins/git/traits/CloneOptionTrait.html
and creating a special tr
Hi James
On Sun, Jan 12, 2025 at 10:47 AM James Nord wrote:
>
> Take a little ok at the clone and checkout traits
> https://javadoc.jenkins.io/plugin/git/jenkins/plugins/git/traits/package-summary.html
>
> It would appear that you should be able to do this with a new trait.
>
I miss here a bit.
Take a little ok at the clone and checkout
traits
https://javadoc.jenkins.io/plugin/git/jenkins/plugins/git/traits/package-summary.html
It would appear that you should be able to do this with a new trait.
Regards
/James
On Saturday, 11 January 2025 at 14:52:31 UTC mic...@amarulasolutions.com
Hi Mark
On Sat, Jan 11, 2025 at 3:16 PM Mark Waite wrote:
>
>
>
> On Saturday, January 11, 2025 at 4:22:58 AM UTC-7 Michael wrote:
>
> Hi all
>
> Is it possible to use git clone from sh context but then populate as I
> had clone using gitscm?
>
>
> Not really. Maybe you could approximate it by c
On Saturday, January 11, 2025 at 4:22:58 AM UTC-7 Michael wrote:
Hi all
Is it possible to use git clone from sh context but then populate as I
had clone using gitscm?
Not really. Maybe you could approximate it by calling checkout scm with
parameters that try to duplicate your git clone p
