Oh. Hmm. Seems like the url for Metacello should point right to the "repository" directory in the git repo. so ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo/repository but when I use scp to copy a file over ssh I always have to add an extra colon (:) before the path, after the domain/port combo. So maybe its ssh://git@bitbucket.somehost.be:8899:/xxx/t3-pharo/repository Sven Van Caekenberghe-2 wrote
But it is not just private, it runs on our own servers.
Maybe MCBitbucketRepository has to be extended like the MCGitlabRepository as Cyril suggested ...
On 19 Feb 2019, at 19:08, Paul DeBruicker <
pdebruic@
> wrote:
Does
Metacello>>#bitbucketUser:project:commitish: path:
do what you want?
You can set your bitbucket username/password with
MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword
Which should let you access your private repo
Sven Van Caekenberghe-2 wrote
Hi,
My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ?
Metacello new repository: 'ssh://
git@.somehost
:8899/xxx/t3-pharo.git'; baseline: 'BetaNineT3'; load: #('core' 'gb').
IOW, what is the correct URL ?
Is that even possible, if not what is the alternative ?
I created/used this repo before, using keys as authentication.
Could one also use username/password authentication, like when deploying ?
Sven
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html