Does the new build status feature not work with ssh alias?

Jan Dockx December 11, 2017

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?

2 answers

0 votes
Jan Dockx December 13, 2017

Non-sequitur

 

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?

Jan Dockx December 13, 2017

bitbucket-pipelines.yml:

# See https://confluence.atlassian.com/x/14UWN for more examples
image: node:6.10.3

pipelines:
default:
- step:
caches:
- node
script:
- 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

 remote:

>git remote
origin
>git remote get-url origin
git@FarmadBitBucket.org:farmadcode/pharmacy-registrar.git

~/.ssh/config:


# --- SourceTree Generated ---
Host FarmadBitBucket.org
    HostName bitbucket.org
    User j_dockx
    PreferredAuthentications publickey
    IdentityFile /Users/jand/.ssh/j_dockx-Bitbucket
    UseKeychain yes
    AddKeysToAgent yes
# ----------------------------
0 votes
bgannin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 11, 2017

Sourcetree is looking at the remotes (for Bitbucket Cloud) and for the presence of a Bitbucket Pipelines configuration file. If those aren't present then the messaging changes. 

Brian Ganninger
Senior Mac Developer, Sourcetree

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events