我们在Ubuntu机器上的AWS中设置了Jenkins服务器。
在Windows Server 2012上创建了两台机器,并且每台机器都安装了Visual Studio Enterprise Edition并使用这些机器上的单个Signon使用许可证。
在第二台计算机上,我们已经安装了安装罩,这是一个结节的许可证。
对于每个构建,这些计算机都使用,并且在末端安装罩将用于创建设置文件并同步到OneDrive。
如何将此设置迁移到github动作并使用Oneime跑步者(每次)而不是固定的跑步者。
问题是,如何使用这些跑步者和Visual Studio安装来管理许可证。
请建议。
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.
发布评论
评论(2)
这是从Jenkins迁移。
GitHub Action还支持 self forse主持跑步者,还有安全硬化管理签名密钥的指南。
如果您不需要的软件不是预先安装,您可以随时使用
apt
或设置脚本,因为您已经在当前计算机上使用了Ubuntu。apt
也不需要sudo
在跑步者上:在Visual Studio的主题上,使用构建工具代替完整的企业版本 - AFAIK没有任何许可问题这样,但是您可以找到
在这一点上,我确实发现了有关使用完整Visual Studio构建工具的许可证的一些有趣的讨论。 > vscode github ,包括一个很好的
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 requiresudo
on runners: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.
这就是我从installshield转换为Wix的原因之一。虽然您可以有一个步骤来安装安装shipshield(假设您有管理员),您必须转到并发许可而不是节点锁定。当您使用FOSS工具而不是适当的DRM锁定工具时,所有这些丑陋都消失了。
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.