We have a jenkins server setup in AWS on an ubuntu machine.

Created two machines on windows server 2012 and each having visual studio enterprise edition installed and license using single signon on those machines.

And on second machine we have installshield installed and that is a nodelocked license.

For every build these machines are used and at the end installshield will be used to create a setup file and synced to onedrive.

How to migrate this setup to GitHub actions and use onetime runners(every time) instead of fixed runners.

Issue is, how the license will be managed with these runners and the visual studio installation also.

Please suggest.

CodePudding user response：

Here is a link to the Github Actions wiki for migrating from jenkins.
Github actions also has support for self-hosted runners, and there is also the security hardening guidelines for managing signing keys.

If the software you need isn't preinstalled, you can always use apt or setup scripts since you're already using Ubuntu on your current machine.

apt also doesn't require sudo on runners:

- name: Install Dependencies
  run: |
       apt-get update && apt-get install -y ...

On the subject of visual studio, use the build tools instead of the full enterprise version - AFAIK there aren't any licensing issues with that, but you can find
On that note, I did find some interesting discussion about the license for using the full visual studio build tools on the VSCode github, including a pretty good breakdown of exactly where and how you can use them according to the license.

CodePudding user response：

This is one of the reasons why I switched from InstallShield to WiX. While you could have a step to install InstallShield (assuming you have admin) you'd have to go to concurrent licensing instead of node locked. All that ugliness goes away when you use FOSS tools instead of properietary DRM locked tools.