How to use artifactes from another step?

When reading the documentation I thought artifacts from previous steps would be available for the following ones.

    docker: true

            - step:
                image: golang:1.9
                name: Build and test
                    - PACKAGE_PATH="${GOPATH}/src/${BITBUCKET_REPO_SLUG}"
                    - mkdir -pv "${PACKAGE_PATH}"
                    - tar -cO --exclude-vcs --exclude=bitbucket-pipelines.yml . | tar -xv -C "${PACKAGE_PATH}"
                    - cd "${PACKAGE_PATH}"

                    - go get -v
                    - go build -v
                    - go test -v ./...
                    - MYAPPLICATION

            - step:
                image: debian/jessie:latest
                name: Deploy
                    - ls -la

In this configuration I expected to have the MYAPPLICATION file from "Build and test" step available to use on the "Deploy" step.

However, the "ls -l" command show only my source code and not the MYAPPLICATION file.

1 answer

1 accepted

0 votes
Accepted answer

My mistake. When I first changed the work dir on the first step I created the artifacts outside BITBUCKET_CLONE_DIR. It was just add a copy line to the end of the step:


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,916 views 7 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you