Configuring Test Repository - dogtagpki/pki GitHub Wiki
By default the CI will perform the tests using @pki/master repository. Sometimes itβs necessary to perform the tests using a different repository (e.g. to test dependency changes).
Prior to PKI 11.4 the repository can be configured by creating a GitHub secret called BASE64_REPO to store the base64-encoded value of the test repository name. To reset the test repository simply remove the secret.
In PKI 11.4 or later the repository can be configured by creating a GitHub variable called COPR_REPO to store the repository name. To reset the test repository simply remove the variable.
For example, to test using edewata/pki repository prior to PKI 11.4, base-64 encode the repository name with the following command:
$ echo "edewata/pki" | base64 ZWRld2F0YS9wa2kK
Then create the secret:
-
Go to Settings β Secrets and variables β Actions β Secrets.
-
Click New repository secret.
-
Enter
BASE64_REPOas the secret name. -
Enter the base64-encoded value as the secret value.
-
Click Add secret.
In PKI 11.4 or later create a variable:
-
Go to Settings β Secrets and variables β Actions β Variables.
-
Click New repository variable.
-
Enter
COPR_REPOas the variable name. -
Enter
edewata/pkias the variable value. -
Click Add variable.
Sometimes old versions of packages in COPR can get selected instead of the test packages, so it is a good idea to delete any non-relevant builds from your test repo before starting.
To reset the test repository prior to PKI 11.4, remove the secret:
-
Go to Settings β Secrets and variables β Actions β Secrets.
-
Click Remove next to
BASE64_REPO. -
Click Yes, remove this secret.
To reset the test repository in PKI 11.4 or later, remove the variable:
-
Go to Settings β Secrets and variables β Actions β Variables.
-
Click Remove next to
COPR_REPO. -
Click Yes, remove this variable.