Replies: 2 comments 2 replies
-
|
Check this section If this VM's machine id is changed, it need CI license. If it's stable, Pro License is OK, but you need make sure machine id is fixed in each run. |
Beta Was this translation helpful? Give feedback.
-
|
About upgrading issue, refer to And https://pyarmor.readthedocs.io/en/latest/licenses.html#how-to-upgrade-pyarmor-licenses Just as the doc, In short, if it could be upgraded successfully by the guide in the documentation, it’s OK. If something is wrong, this license can’t be upgraded. Pyarmor Team doesn’t handle this kind of request, there may be no any reply. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a Pyarmor Basic license which works with pyarmor 8.5. But we have been facing issues trying to make it work with pyarmor 9, detailed here: #2329
Since we have not been able to find direct documentation links addressing our specific issues, I assume our current license won't work with pyarmor 9. So, we are considering buying a new license. But we're a bit confused as to whether we need a Pro license or a CI license.
The thing is, we mainly use our license in Azure DevOps Microsoft-hosted agents.
As per documentation:
CI license doesn't work in the runner which has its own disk. If the runner is not docker container, use Pro license instead.Per my knowledge, Microsoft-hosted agents run on VM's (unless you explicitly specify you want to run on containers), which would have their own disk. According to that, I assume we need a Pro license. Could you please verify if my understanding is correct.
Beta Was this translation helpful? Give feedback.
All reactions