Smalltalk › Pharo › Pharo Smalltalk Developers

Using Metacello scripting API with non-github repo

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Sven Van Caekenberghe-2

Using Metacello scripting API with non-github repo

Hi,

My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ?

Metacello new
repository: 'ssh://[hidden email]: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

Sven Van Caekenberghe-2

Re: Using Metacello scripting API with non-github repo

I can add that Iceberg _can_ clone from my URL, it just seems that Metacello doesn't understand it.

> On 19 Feb 2019, at 14:56, Sven Van Caekenberghe <[hidden email]> 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://[hidden email]: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
>
>

CyrilFerlicot

Re: Using Metacello scripting API with non-github repo

In reply to this post by Sven Van Caekenberghe-2

On Tue, Feb 19, 2019 at 2:57 PM Sven Van Caekenberghe <[hidden email]> 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://[hidden email]: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 ?

Hi,

I think non default ssh port will not be supported by Metacello.

I had to add it for gitlab to be able to reference repositories from a
self hosted gitlab with non default ssh port. I guess the same can be
done for bitbucket but it I doub it's already done.

For Gitlab I added it in MCGitlabRepository for the Metacello part and
in the Iceberg extensions of this class to use the new infos in
Iceberg. (Method scpUrl)

>
> Sven
>
>
>

--
Cyril Ferlicot
https://ferlicot.fr

Paul DeBruicker

Re: Using Metacello scripting API with non-github repo

In reply to this post by Sven Van Caekenberghe-2

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

Sven Van Caekenberghe-2

Re: Using Metacello scripting API with non-github repo

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 <[hidden email]> 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

Paul DeBruicker

Re: Using Metacello scripting API with non-github repo

Oh. Hmm.

Seems like the url for Metacello should point right to the "repository"
directory in the git repo.

so

ssh://[hidden email]: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://[hidden email]: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