Pipeline - build depends on another development package in a different repo

Patrick Farren

How do i setup and build a dependency maven package within a pipeline.

Issue:

I would like to create a pipeline to build(maven) a new java app package but this package depends on another 'common' package held in a different bitbucket repo.

Within my local development environment the build process is straightforward 

step 1. within common package folder run : mvn clean install

step 2. within the new java app package run : mvn clean package

This successfully places the common jar file into local maven repo and is available during the build of the new java app.

Question:

How do I perform similar steps in a pipeline? Do I assume that I will have a local maven repo in the docker image during the build pocess?

 

Thanks for your help

Philip Hodder

Hi Patrick,

I have two possible solutions for you here.

--------------

First option. If you want to replicate what you are doing on your own machine, you will need to clone the common package into your pipeline as well. As we will only clone the main java application repository.

You'll need to set up access keys and ssh keys for your repository and pipelines:

• Create a key-pair with this documentation on your main java app repository: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html
• Add the public key as an access key to your common package repository: https://confluence.atlassian.com/bitbucket/use-access-keys-294486051.html

You'll then want something like the following in your bitbucket-pipelines.yml for your main java repository:

image: java:8
pipelines:
  default:
    step:
      - apt-get update -y
      - apt-get install -y git
      - git clone git@bitbucket.org:username/common.git
      - cd common
      - mvn clean install
      - cd ..
      - mvn clean package
      - # Whatever else you need.

--------------

Second option. If you want a more idiomatic pipeline, you can instead have two pipelines. One to build you common package and one to build you main java repository.

You will need to configure your common package to have the maven release plugin: http://maven.apache.org/maven-release/maven-release-plugin/

This will allow you to release the common package as its own package, which you can then use as a regular dependency in your main java repository.

In your common package, once configured in the pom.xml properly, your pipeline should look like:

image: java:8
pipelines:
  default:
    step:
      - mvn clean package
      - mvn release:prepare
      - mvn release:perform

And then in your main java application repository, your pipeline will simply look like

image: java:8
pipelines:
  default:
    step:
      - mvn clean package
      - # Whatever else you need.

Hope this helps!

Thanks,

Phil