Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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.

Before you start, make sure you have sufficient rights in BitBucket.

  1. Select the right Git repository.

  2. Navigate to Repository settings > Pipelines > Repository variables.

  3. 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.

  4. Navigate to Repository settings > Pipelines > Deployments.

    1. Create required environments

    2. For each environments create variable for URL with partition url.

  5. Navigate to Repository settings > Pipelines > Settings.

    1. Enable Pipeline

    2. Click on “Configure bitbucket-pipelines.yml”

    3. Commit the yml file.

    4. Create a feature branch for Pipeline and fetch the yml file in intellij.

    5. Replace the existing code with following:

      image: maven:3.6-jdk-11
      
      pipelines:
        branches:
          dev:
            - step:
                name: dev
                script:
                  - mvn clean test -e --batch-mode
       
            - step:
                name: Deploy DEV
                deployment: DEV
                image: pricefx/pfxpackage
                script:
                  - pfxpackage -import -timeout 120 -url $URL -user $PFX_USER -password $PFX_PASS -partition {parition name} -from . $OPTIONS
      
    6. Replace the {parition name} with dev partition name.

    7. Create the similar pipeline for other partitions if required.

    8. Commit the file and create the Pull request.

  6. 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.

  7. After merging the pull request for Pipeline branch with dev branch, Pipeline should start

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.

See also: https://support.atlassian.com/bitbucket-cloud/docs/bitbucket-pipelines-configuration-reference/

  • No labels