Continuous integration with Trados plugin

Hello all. Apologies if this has been answered before; I couldn't find anything relevant.

I am developing a plugin for Trados Studio. I started with the "SDL Trados Studio (2021)" template in Visual Studio.

I am wondering what the story is for continuous integration of such a project?

Specifically I would like to be able to run tests on a CI service like CircleCI to ensure that the project always compiles and tests pass. However I note that the project links against files supplied by my local installation of Trados Studio, namely things like this inside the .csproj file:

    <Reference Include="Sdl.Desktop.IntegrationApi">
      <Private>True</Private>
      <HintPath>$(ProgramFiles)\SDL\SDL Trados Studio\Studio16\Sdl.Desktop.IntegrationApi.dll</HintPath>
    </Reference>

It seems as though I would need to either

  • Set up a private CI runner with Trados Studio installed, or preferrably
  • (Since our CI runners are primarily Docker images) set up a Docker image with Trados Studio installed

Is that correct?

In either of these cases (particularly the Docker case) what is the licensing story? Do we need to purchase a full additional license in order to make use of CI with a Trados plugin project?

Parents Reply
  • Thanks for your reply.

    > This approach could work if you are looking only to build and run unit tests for your plugin code as part of the build.

    Yes, this is all we're aiming to do in CI.

    Could you address the licensing portion of my question, given that we're not trying to run Trados in CI but merely build against it?

    > In either of these cases (particularly the Docker case) what is the licensing story? Do we need to purchase a full additional license in order to make use of CI with a Trados plugin project?

    Also does SDL provide any Docker images for build/test purposes, or would we need to build our own?

Children