Tag: Bitbucket Pipeline Configuration

How to configure Bitbucket Pipeline

  1. Create a Self Signed Digital Certificate first
  2. Create a Connected App. Upload the Digital Certificate while creating it. Keep the Consumer Key and Consumer Secret handy.
  3. Encrypt the server key.
    • Go to your Command Prompt again and execute the following command to generate a key and initializtion vector (iv) to encrypt the server.key file locally. The key and iv are used by Bitbucket Pipeplines to decrypt the server key in the build environment. Keep the key and iv handy. 
//Generate key and iv

openssl enc -aes-256-cbc -k MY_PASS -P -md sha1 -nosalt

//Encrypt the server key

openssl enc -nosalt -aes-256-cbc -in /Bitbucket/JWT/server.key -out /Bitbucket/JWT/server.key.enc -base64 -K GENERATED_KEY_IN_LAST_STEP -iv GENERATED_IV_IN_LAST_STEP

Inside the Bitbucket

  1. Enable Two Step Verification
  2. Create a Repository, entering a Project Name and Repository Name
  3. Go to Repository settings -> Settings -> Enable Pipelines
  4. Go to Repository variables and set KEY and IV
  5. Go to Deployment and set the Deployment Variables
    • ENDPOINT – Sandbox / Production Instance url
    • CONSUMER_KEY – From Connected App
    • USER_NAME – Username of the Deployment Admin

Create a Project in VS Code

  1. Go to VS Code
  2. Create an empty project
  3. Create a folder called assets as shown in the screenshot
  4. Keep the server.key.enc file inside the assets folder
  5. Keep the bitbucket-pipelines.yml and SpecifiedTest.txt files inside the project folder as shown in the screenshot
  6. Connect the VS Code with the Bitbucket repository
  7. Checkout a feature branch in VS Code
  8. Commit and Push the project