after bitbucket pipeline push to Heroku, Heroku overrides it with it's own process

This is my config for the bitbucket pipeline for deploying to heroku 

image: node:7.8.0

pipelines:
  default:
    - step:
        script: # Modify the commands below to build your repository.
          - node -v
          - curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version 0.21.3
          - export PATH=$HOME/.yarn/bin:$PATH
          - yarn
          - git config --global push.default simple
          - git push -f https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git

I have node 7.8.0 here, but after the `git push -f...` command, heroku starts installing it's own node (version 6), so I fixed it by updating my package.json to specify the node version in the engines object.

My question, is what is the point of setting up the pipeline to node 7.8.0 and yarn and all that, when after I push to heroku, heroku installs node and yarn anyways on its own. 

Thank you.

 

0 answers

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Agile

How Davin Studer gets Confluence to do everything he wants it to do...except dishes

  @Davin Studer holds many interests, including but not limited to health tech and Star Trek. Read on to discover more about Davin, from his favorite Confluence macros to his favorite lit...

201 views 1 9
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