You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because Pyarmor License is paid once in Pyarmor 8, but online verification for using Pyarmor License in CI/CD pipeline will continue consuming a lot of Pyarmor Server resources.
So Pyarmor 9 has a big change about using Pyarmor in CI/CD pipeline:
Pyarmor Pro License couldn't be used in CI/CD pipeline since Pyarmor 9
Pyarmor CI License is right for CI/CD pipeline case
Pyarmor Basic still could be used in CI/CD pipeline, but it need request one extra CI regfile
In a short
If not use Pyarmor License in CI/CD pipeline, almost nothing changed If not upgrade to Pyarmor 9, but still use Pyarmor 8, nothing changed Pyarmor Pro License purchased after 2024-10-20 could not be used in CI/CD pipeline even use it with Pyarmor 8 Pyarmor CI License is paid each year, and couldn't be used in local machine
Fair use
Pyarmor Pro License still could be used in CI/CD pipeline for low volume, 100 runs per month
Upgrade Basic or Pro License to Pyarmor 9
If Pyarmor License has been registered in this device
First upgrade to Pyarmor 9
$ pip install -U pyarmor
When first time to obfuscate scripts, it will show hints
$ pyarmor gen foo.py
...
Pyarmor 9 has big change on CI/CD pipeline
If not using Pyarmor License in CI/CD pipeline
Press "c" to continue
Otherwise press "h" to check Pyarmor 9.0 Upgrade Notes
Continue (c), Help (h), Quit (q):
Just press c to continue, there is no prompt later
If Pyarmor License isn't registered in this device
First use activation file to generate new registration file
$ pip install -U pyarmor
# Please replace XXX with real product name
$ pyarmor reg -p XXX pyarmor-regcode-xxxx.txt
Save and backup new registration file pyarmor-regfile-xxxx.zip
Use this new regfile to register Pyarmor in other new device
Because Pyarmor License is paid once in Pyarmor 8, but online verification for using Pyarmor License in CI/CD pipeline will continue consuming a lot of Pyarmor Server resources.
So Pyarmor 9 has a big change about using Pyarmor in CI/CD pipeline:
In a short
If not use Pyarmor License in CI/CD pipeline, almost nothing changed
If not upgrade to Pyarmor 9, but still use Pyarmor 8, nothing changed
Pyarmor Pro License purchased after 2024-10-20 could not be used in CI/CD pipeline even use it with Pyarmor 8
Pyarmor CI License is paid each year, and couldn't be used in local machine
Fair use
Pyarmor Pro License still could be used in CI/CD pipeline for low volume, 100 runs per month
Upgrade Basic or Pro License to Pyarmor 9
If Pyarmor License has been registered in this device
First upgrade to Pyarmor 9
When first time to obfuscate scripts, it will show hints
Just press
c
to continue, there is no prompt laterIf Pyarmor License isn't registered in this device
First use activation file to generate new registration file
$ pip install -U pyarmor # Please replace XXX with real product name $ pyarmor reg -p XXX pyarmor-regcode-xxxx.txt
Save and backup new registration file
pyarmor-regfile-xxxx.zip
Use this new regfile to register Pyarmor in other new device
If activation file is used too many times, please first install Pyarmor 8, then upgrade to Pyarmor 9
Upgrade Group License to Pyarmor 9
It need generate device regfile again with Pyarmor 9.0+
First upgrade to Pyarmor 9
Then generate device regfile as before.
For example, generate device regfile
pyarmor-device-regfile-6000.1.zip
for device no. 1Finally, use new one to register Pyarmor in offline device
Refer to
What need to do after upgrading Pyarmor
How to use Pyarmor in CI/CD pipeline
The text was updated successfully, but these errors were encountered: