Additional info:

I run Jenkins a service and changed the service user to be the Jenkins user. That solved similar problems with other tools ins the past, not with Passolo.

Hi Franz-Josef,

I run my automation via Jenkins and Ant scripts but the principle is the same. I tend to run Passolo via this command "C:\Program Files (x86)\SDL\SDL Passolo\SDL Passolo 2018\psl.exe" and use the options I need afterwards, e.g. /openproject:project\location.lpu /generate". It's always worked for me (my Jenkins service user is the same as the user I would normally log on to the server as).

Mark

Hi Mark

thank you for your reply. Is there a reason to use psl.exe instead pof pslcmd.exe?

Franz-Josef

Hi Franz-Josef,

No, and to be honest I've been doing it that way for so long that if there was a reason then I've forgotten it!

Mark

After running and registering PSL as administration user once, as suggested in another thread, the project is working with Jenkins.

We stumbled upon 2 drawbacks related to the fact that PSL uses absolute paths:

1. The path to the key file is absolute so I hade to set it to the jenkins workspace folder in order to sign the satelletie assemblies correctly.
   This is annoying,but set and forget as long as the SVN/Jenkins setup doesn't change.
2. The path to the translation packages is absolute, too. So I also had to "export" the packages to the Jenkins workspace folder and after that copy it over to the SVN working folder to commit it.
   And I have to do this every time I add new files to the translation package.

This feels all wrong. Is there a way to avoid this "hack"?