My instance of Jenkins is on windows. I am using the debian-pbuilder-plugin

When use the plugin to build a deb on a Ubuntu 20.04 Linux agent, the plugin uses a command that tries setting the config file to a C: directory which does not exist on the Linux slave OS causing failure of the build.

in the following command that the plugin invokes on the linux agent, notice that the workspace directory looks correct, however the --configfile reference and --homedir values are somehow looking for it in C:\ directory which does not exist in linux.

forking: pbuilder create --debootstrap debootstrap --debootstrapopts --arch --debootstrapopts amd64 --debootstrapopts --variant=buildd --configfile C:\home\jenkins\workspace\TEST-CSS-LCOMP-UPDATE\pbuilderrc2614078528463966760.tmp --hookdir C:\home\jenkins\workspace\TEST-CSS-LCOMP-UPDATE\hookdir --buildplace /home/jenkins/\var\cache\pbuilder\base-focal-amd64 --mirror http://us.archive.ubuntu.com/ubuntu/ --architecture amd64 --distribution focal --no-targz --extrapackages cowdancer

01:02:51 E: Config file C:\home\jenkins\workspace\TEST-CSS-LCOMP-UPDATE\pbuilderrc2614078528463966760.tmp does not exist

01:02:51 E: pbuilder create failed
Config file C:\home\jenkins\workspace\TEST-CSS-LCOMP-UPDATE\pbuilderrc2614078528463966760.tmp does not exist

If i go into my Ubuntu Jenkins Slave machine, i can see that /home/jenkins/workspace/TEST-CSS-LCOMP-UPDATE/pbuilderrc2614078528463966760.tmp DOES exist. it doesnt exist above because the plugin is specifying the wrong path.