When triggered using Jenkins pipeline sfdx-git-delta is not recognized but recognized using Git Bash / Visual Studio Code / CMD

[shrishrimal-swapnil]

Hello,

I am trying to integrate sfdx-git-delta plugins in my Jenkins CI / CD Pipeline. I have installed sfdx-git-delta plugin using below command.

sfdx plugins:install sfdx-git-delta

Post installation I have confirmed the same with sfdx plugins and I see the latest version has been installed.

I am able to get package/package.xml when I execute below command using either Visual Studio Code or Git Bash or CMD,

sfdx sgd:source:delta --to "HEAD" --from "HEAD^" --output .

However, when I use same commands in Jenkins pipeline, I get error message as mentioned below,

To debug the issue, I tried to echo installed plugins using "sfdx plugins" in Jenkins pipeline script and I see below message stating that "no plugins are installed"

I tried to navigate in Jenkins workspace using git bash and execute command to list sfdx plugins and I see the that latest plugin is installed.

Can anyone help me to understand what I am missing here ? As Jenkins is installed on the same machine on which SFDX CLI and sfdx-git-delta plugin is installed. Also, I have added path of SFDX CLI in Jenkins custom tool configuration.

Any help / suggestions are highly welcomed.

Thanks!

[scolladon]

Hi @shrishrimal-swapnil

Thanks for raising this issue !

This issue looks like a duplicate of this one right ?

[shrishrimal-swapnil]

Hi @scolladon

Thank you for your response.

I don't think this issue is duplicate of this one.

The plugin is installed on the same machine where Jenkins is installed and there is no Docker in the picture. Through Jenkins, I am just triggering command which should get sfdx plugin, but that is not the case. Using simple Git Bash or Visual Studio Code terminal the sfdx plugin shows list of plugins installed whereas if executed through Jenkins pipeline, it says no plugins installed.

[shrishrimal-swapnil]

Hi @scolladon

Just an update. I tried below workaround and it did worked out for me.

Even though, the plugin is installed on my machine I installed it again through Jenkins pipeline and for subsequent execution it did not required plugin installation again.

Thanks!