In the case where you want to copy a collection of jobs from one Jenkins server to another, here’s a process you can use to make the migration. This guide assumes you have two different remote Jenkins instances to copy jobs from.
SSH into the source server to determine where the /jobs directory is for Jenkins. Example would be in /
Use scp (on your local machine) to copy the jobs from the remote Jenkins instance with the jobs:
If you are looking to improve performance on your website, this will automatically convert the images on your site to the more efficient WebP format. This will help with Google Lighthouse scores (especially in solving the “Serve images in next-gen format” issue).
When trying to copy a database with Always Encrypted data (say, to a different environment), you’ll generally want to recycle the Column Master Key used to match the vault stored in the same Azure resource group. This takes a little bit of work to do:
You’ll need to have the following software installed:
You’ll also need to make sure the database you’re copying from has a key that already exists. Run the following query on your newly copied database:
select * from sys.column_master_keys
And then check to see if the key exists in the appropriate vault:
az keyvault key show --id KEY_PATH
If it exists, you’ll be able to copy the database over without issue.
Create a new key in the Key Vault:
az keyvault key create --name Always-Encrypted-Auto1 --vault-name VAULT_NAME
Next, create a new Column Master Key, using the created key above.
With two CMKs, rotate and then cleanup the initial CMK.
Normal OrderCreated 27s cert-manager Created Order resource "tls-secret-3300974441"
Normal CertIssued 3s (x2 over 20m) cert-manager Certificate issued successfully
Normal OrderComplete 3s cert-manager Order "tls-secret-3300974441" completed successfully