I have a repo on bitbucket, checked out in Sourcetree via ssh with an alias (~/.ssh/config). Bitbucket pipelines are enabled and working.
In Sourcetree, I see a white plus sign on a blue background. On click, I am asked to 'migrate now'. Clicking asks to 'create a remote repository', which I obviously already have.
Am I misunderstanding something, or might the reason be that this new feature does not recognize the ssh alias as Bitbucket?
1) There is a `bitbucket-pipelines.yml`
2) The origin remote is a Bitbucket Cloud repository, i.e., an ssh alias to Bitbucket Cloud
3) I see what I described
2a) push and fetch works
My question was, why do I see what I described, which is not the build status? Am I doing something wrong, or are ssh aliases NYI?
# See https://confluence.atlassian.com/x/14UWN for more examples
- export NODE_ENV="ci"
- echo 'node:' `node --version`
- echo 'npm:' `npm --version`
- npm install
- echo 'branch:' `git rev-parse --abbrev-ref HEAD`
- echo 'tags:' `git name-rev --tags --name-only $(git rev-parse HEAD)`
- echo 'sha:' `git rev-parse --verify HEAD`
- echo $NODE_ENV
- npm test
- git tag build/$BITBUCKET_BUILD_NUMBER
- npm run legalReport
#- git push origin --tags MUDO doesn't work yet - need ssh key
>git remote get-url origin
# --- SourceTree Generated ---
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events