Metacello load in code vs. Iceberg menu install? Can you automate remote loading?
Hi - Iâm trying to automate the deployment of a seaside image to Digital Ocean. I was following the Enterprise Pharo booklet - and its a bit out of date, but I wanted to do the bit about taking a clean image and then loading in my project which Iâve stored in Git using Iceberg. So on the command line I am trying to eval â Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'PagerDuty'; repository: 'git@gitlab.com:macta/WillowPagerDuty.git'; load.â But I get retry errors and a walkback, so Iâve tried to do the same in the playground in a fresh image and its true - I get an error because ZnClient is trying to connect to a url like "http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O%3DD <http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O=D>â (so it interprets that git@ specification strangely). But what is weird, is that if I use Iceberg - connected to the same repo (and specified the same way) - and then use the Metacello - Install baseline menu (right click on the BaselineOfXXX package) it then works perfectly. So whatâs the difference? It looks like the latter is mapping down to a "repository: 'gitlocal://', packageDir;â whereas the above is trying to read it over the wire? I then tried using an access token for gitlab, so its an https variant - but that gave me an error as well? Does this mean to automate I have to bring down the initial BaseLine - but then if that baseline refers to others - that seems to work, so Iâm a bit confused about what is going on? Tim
I think you can use: Metacello new baseline: 'PagerDuty'; repository: 'gitlab://macta/WillowPagerDuty:master/source'; load. or something like that On Wed, May 9, 2018 at 8:44 PM Tim Mackinnon <tim@testit.works> wrote:
Hi - Iâm trying to automate the deployment of a seaside image to Digital Ocean. I was following the Enterprise Pharo booklet - and its a bit out of date, but I wanted to do the bit about taking a clean image and then loading in my project which Iâve stored in Git using Iceberg.
So on the command line I am trying to eval â Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'PagerDuty'; repository: 'git@gitlab.com:macta/WillowPagerDuty.git'; load.â
But I get retry errors and a walkback, so Iâve tried to do the same in the playground in a fresh image and its true - I get an error because ZnClient is trying to connect to a url like " http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O%3DD <http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O=D>â (so it interprets that git@ specification strangely).
But what is weird, is that if I use Iceberg - connected to the same repo (and specified the same way) - and then use the Metacello - Install baseline menu (right click on the BaselineOfXXX package) it then works perfectly.
So whatâs the difference? It looks like the latter is mapping down to a "repository: 'gitlocal://', packageDir;â whereas the above is trying to read it over the wire?
I then tried using an access token for gitlab, so its an https variant - but that gave me an error as well? Does this mean to automate I have to bring down the initial BaseLine - but then if that baseline refers to others - that seems to work, so Iâm a bit confused about what is going on?
Tim
This was indeed the answer - use the gitlab protocol and specify a branch e.g. Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'PagerDuty'; repository: âgitlab:// <mailto:git@gitlab.com>macta/WillowPagerDuty:master/src'; load. Thanks Gaby Tim
On 10 May 2018, at 01:26, Gabriel Cotelli <g.cotelli@gmail.com> wrote:
I think you can use: Metacello new baseline: 'PagerDuty'; repository: 'gitlab://macta/WillowPagerDuty:master/source'; load.
or something like that
On Wed, May 9, 2018 at 8:44 PM Tim Mackinnon <tim@testit.works> wrote: Hi - Iâm trying to automate the deployment of a seaside image to Digital Ocean. I was following the Enterprise Pharo booklet - and its a bit out of date, but I wanted to do the bit about taking a clean image and then loading in my project which Iâve stored in Git using Iceberg.
So on the command line I am trying to eval â Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'PagerDuty'; repository: 'git@gitlab.com <mailto:git@gitlab.com>:macta/WillowPagerDuty.git'; load.â
But I get retry errors and a walkback, so Iâve tried to do the same in the playground in a fresh image and its true - I get an error because ZnClient is trying to connect to a url like "http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O%3DD <http://:80/git@gitlab.com:macta/WillowPagerDuty.git/?C=M;O=D>â (so it interprets that git@ specification strangely).
But what is weird, is that if I use Iceberg - connected to the same repo (and specified the same way) - and then use the Metacello - Install baseline menu (right click on the BaselineOfXXX package) it then works perfectly.
So whatâs the difference? It looks like the latter is mapping down to a "repository: 'gitlocal://' <>, packageDir;â whereas the above is trying to read it over the wire?
I then tried using an access token for gitlab, so its an https variant - but that gave me an error as well? Does this mean to automate I have to bring down the initial BaseLine - but then if that baseline refers to others - that seems to work, so Iâm a bit confused about what is going on?
Tim
participants (2)
-
Gabriel Cotelli -
Tim Mackinnon