• State Not Answered
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 2022 views
  • Users 0 members are here
Options
Related

CI/CD with SVN and Jenkins

Franz-Josef Knelangen

Trying to automate L10N with PSLcmd. Running the Batch from CMD is fine.

Our sources are stored in SVN, our CI/CD tool is Jenkins.

Running the batch from a Jenkins job fails.

Opening the LPU in the Jenkins workspace Passolo complains about the file being read-only.

The folder is set to read/write - as far as I can tell looking at the folders properties in Windows Explorer.

Do I have to set some special access rights to make Passolo work with SVN and Jenkins?

Greetings,
Franz-Josef

Passolo 2018 (18.0.171.0) on Windows Server 2012 R2, VisualSVN Server 4.3.2, Jenkins (latest LTS version)
Rate translation
×
Suggest better translation
×
Parents
  • 0

    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"?
Reply
  • 0

    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"?
Children
No Data