How to add go binary as bitbucket pipeline artifact?

rainbowstack

Hello, I am trying to add the output binary of my pipeline to the build-in artifactory.

 

image: golang:1.13

pipelines:
default:
- step:
script:
- PACKAGE_PATH="${GOPATH}/src/bitbucket.org/${BITBUCKET_REPO_FULL_NAME}"
- mkdir -pv "${PACKAGE_PATH}"
- tar -cO --exclude-vcs --exclude=bitbucket-pipelines.yml . | tar -xv -C "${PACKAGE_PATH}"
- cd "${PACKAGE_PATH}"
- go get -v
- env GOOS=windows GOARCH=amd64 go build
- go build -v
- ls
artifacts:
- fx_update.exe

However, the binary does not end up in the artifactory:

So I threw this `ls` command in there to see if the .exe is present and Indeed it is:

Does anyone know why it's not doing what I want?

 

ktomk

Artifacts are given relative to the pipelines "build" directory (environment parameter: BITBUCKET_CLONE_DIR) by a relative path (compare with the docs for more details).

In your specific example it is perhaps most easy to copy the artifact over into that directory:

- cp -v -- fx_update.exe "${BITBUCKET_CLONE_DIR}"

Then it should already work as the file fx_update.exe should then be found for the artifact.

In a further thought you can consider to create a directory in your repository intended to have build artifacts stored into, I normally use build for it in the projects root directory and ignore files and directories in there as they are generated (build) so it's easy to run build scripts as well in the development environment on local machines and it's compatible with builds in a pipeline.

E.g. by creating the file build/go/.gitignore in the repository:

# go build artifacts directory
/*
!/.gitignore

If you consider to do so, you need to adopt the artifacts setting (and the destination path of the cp command):

- cp -v -- "fx_update.exe" "${BITBUCKET_CLONE_DIR}/build/go"
artifacts:
- build/go/fx_update.exe

At the end of the day this is independent to the programming language, what makes go different here is that it has the go-path and/or the build-path.

However IIRC this changed some time ago and you can also run go builds and output to other locations, but I must admit I don't have an example or some more reference at hand right now.