itminds/pipeline-tools repository overview

⁠README

⁠pipeline scripts

This image is used to supply pipeline scripts to other Docker images. It is currently used in the following images:

• sonar-runner - for building javascript/typescript projects⁠
• aspnetcore-sonar-build - for building .NET Core projects⁠

⁠Supported CI pipelines

• Bitbucket pipeline⁠

⁠How to add it to a build image

Simply add it to the top of your Dockerfile where you require the pipeline scripts, and then copy them into the image where you need them. This example shows how it is used in the sonar-runner image that we use to build javascript projects.

FROM itminds/pipeline-tools AS pipeline-tools
FROM node:8-alpine

ENV TOOLS_HOME /opt/tools
...
# Install other pipeline tools
COPY --from=pipeline-tools ${TOOLS_HOME}/* ${TOOLS_HOME}/
RUN ln -s ${TOOLS_HOME}/* /usr/local/bin/

⁠Scripts

All the scripts are added to the image PATH, and are accessible through bash script-name

• node-coverage is used to run npm or yarn test and install in all directories containing a package.json, it will prefer yarn if available. Make sure to enable code coverage and specify the coverage report paths in the project yml
• git-merge-master is used on Bitbucket to merge master into the current branch that is being build. This is meant to be used in combination with is-pr to build and test on the result of the pull request.
• is-pr is used on Bitbucket to check if there is an open pull request for the current branch being build. See the PR Example.

⁠Who do I talk to

• Eskild Diderichsen - [email protected]⁠
• Lean Randlev - [email protected]⁠