BitBucket Pipelines for Customer Projects

This guide is intended for partners and customers who want to use their own BitBucket as their Git repository and CI/CD tool instead of GitLab.

Make sure you have sufficient rights in BitBucket.

Select the right Git repository.
Navigate to Repository settings > Pipelines > Repository
Click Variables and create variables PFX_USER and PFX_PASS:
- Add the variable PFX_USER and set its value to pfx.deploy and click OK.
- Add the variable PFX_PASS and set its value to be a strong password (at least 14 characters, at least 1 digit, at least 1 capital letter). Select Keep this value secret and click OK.

Select Starter Pipeline and replace the existing editor content with the following:

image: maven:3.6-jdk-11

pipelines:
  branches:
    dev:
      - variables:
          - name: URL
            default: "https://qa.pricefx.com"
          - name: PARTITION
            default: "sandbox-qa"
      - step:
          name: Deploy
          image: pricefx/pfxpackage
          trigger: manual
          script:
            #PFX_USER: should be set as masked variable in project's settings on BitBucket -> Settings -> CI/CD -> Variable
            #PFX_PASS: the same applies to PFX_PASS do not ever put it here
            - pfxpackage -import -timeout 120 -url $URL -user $PFX_USER -password $PFX_PASS -partition $PARTITION -from . $OPTIONS

Click Save. This will create azure-pipelines.yml file in the root directory of your project.
Create a user account pfx.deploy in the target partitions (QA, PROD) and assign this user the General Admin privileges in each of the partitions where you want to enable deployment and set the password to be identical to the PFX_PASS variable.

Notes:

You should set name to correspond to your partition, eg. Deploy QA or Deploy PROD.
You must set the PARTITION and URL variables to the right values of your environment.
You must set which branch to use for the source under the trigger section.