On 03-10-15 16:09, Esteban Lorenzano wrote:
well… I’m with Marcus here: the real problem is that we shouldn’t use the CI as
a repository for download images.
Hey, it's just an URL. Nobody said it always has to point at the CI.
Just fake it :)
Stephan
well… I’m with Marcus here: the real problem is that we shouldn’t use the CI as
a repository for download images.
Yes I understand but now I have to edit my scripts and find what it not
working.
Instead, I would keep them in a public file server (pretty much the same we do
with Pharo, we d
well… I’m with Marcus here: the real problem is that we shouldn’t use the CI as
a repository for download images.
Instead, I would keep them in a public file server (pretty much the same we do
with Pharo, we do not keep all builds (or versions) in the CI, but all history
is available at files.p
On 03-10-15 09:16, stepharo wrote:
So let us archive it but now my scripts are broken.
If we want the old scripts to continue working, instead of creating a
new (old) job for it we would need some mechanism to tell the build
matrix in more detail what should happen to which build: only build
s now permanently broken)
From: Stephan Eggermont <mailto:step...@stack.nl>
Sent: 10/1/2015 9:47 AM
To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>
Subject: Re: [Pharo-users] Pillar for 30 gone the way of the dodo on
We removed the Pillar job for Pharo 3 because we introduced an new
feature not backward compatible.
Why is that a reason to remove the build? You have a configuration,
don't you?
I would suggest: move to a separate job that is run much less often
and doesn't keep so many old artifacts. That
Stephan Eggermont writes:
> On 01-10-15 10:05, Peter Uhnak wrote:
>> In Jenkins you specify configuration matrix (versions of pharo versus type
>> (development, stable, ...)).. So it will run development for all versions,
>> even pharo 30 (which is now permanently broken)
>
> Shouldn't #'devel
You can exclude some of the combinations from matrix. E.g. exclude build for 30
& development.
> On 01 Oct 2015, at 14:04, Stephan Eggermont wrote:
>
> On 01-10-15 10:05, Peter Uhnak wrote:
>> In Jenkins you specify configuration matrix (versions of pharo versus type
>> (development, stable,
On 01-10-15 10:05, Peter Uhnak wrote:
In Jenkins you specify configuration matrix (versions of pharo versus type
(development, stable, ...)).. So it will run development for all versions, even
pharo 30 (which is now permanently broken)
Shouldn't #'development' for Pharo3.x then point to #'sta
p...@highoctane.be writes:
> Which is a pain as when I copy/paste a shell script full of those, I won't
> do that.
I agree that's a pain. But you have to do it.
> Is this also doing the same thing in blocks like:
>
> [[[label=.bashrc|caption=Ajouts à .bashrc|language=bash
>
> ${SOMEVAR:-}
>
p...@highoctane.be writes:
> Downloaded the book-skeleton, patched the download script so that it gets
> the centos things right and the Pharo4VM.
>
> Now, changes in Pillar made my books unsuable, namely the introduction of
> things like this:
>
> ${tag:parameter=value|parameter2=value2}$
>
>
>
p...@highoctane.be writes:
> Ok, where?
in Pharo 3, open the Catalog Browser, choose Pillar, and click "Install
Stable Version". You will get 2 warnings you can safely ignore. You can
run the unit tests to check everything works fine (Pillar contains 2198
unit tests, in this version, covering 9
t: 10/1/2015 9:47 AM
>> To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>
>> Subject: Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI
>>
>> On 01-10-15 09:41, Stephan Eggermont wrote:
>> > On 30-09-15 19:57, Ferlicot D.
> From: Stephan Eggermont <mailto:step...@stack.nl>
> Sent: 10/1/2015 9:47 AM
> To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>
> Subject: Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI
>
> On 01-10-15 09:41, Stephan Eggermont wr
uot;pharo-users@lists.pharo.org"
Subject: Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI
On 01-10-15 09:41, Stephan Eggermont wrote:
> On 30-09-15 19:57, Ferlicot D. Cyril wrote:
>
>> We removed the Pillar job for Pharo 3 because we introduced an new
&g
On 01-10-15 09:41, Stephan Eggermont wrote:
On 30-09-15 19:57, Ferlicot D. Cyril wrote:
We removed the Pillar job for Pharo 3 because we introduced an new
feature not backward compatible.
Why is that a reason to remove the build? You have a configuration,
don't you?
I would suggest: move to
On 30-09-15 19:57, Ferlicot D. Cyril wrote:
We removed the Pillar job for Pharo 3 because we introduced an new
feature not backward compatible.
Why is that a reason to remove the build? You have a configuration,
don't you?
Stephan
Which is a pain as when I copy/paste a shell script full of those, I won't
do that.
Is this also doing the same thing in blocks like:
[[[label=.bashrc|caption=Ajouts à .bashrc|language=bash
${SOMEVAR:-}
]]]
I am not gonna escape those things as what happens is copy/pasting code.
That there are
Le 30/09/2015 22:32, p...@highoctane.be a écrit :
> Downloaded the book-skeleton, patched the download script so that it
> gets the centos things right and the Pharo4VM.
>
> Now, changes in Pillar made my books unsuable, namely the introduction
> of things like this:
>
> ${tag:parameter=value|par
Downloaded the book-skeleton, patched the download script so that it gets
the centos things right and the Pharo4VM.
Now, changes in Pillar made my books unsuable, namely the introduction of
things like this:
${tag:parameter=value|parameter2=value2}$
made contents with bash shell scripts unparsa
Ok, where?
Phil
On Wed, Sep 30, 2015 at 7:57 PM, Ferlicot D. Cyril wrote:
> Le 30/09/2015 18:38, p...@highoctane.be a écrit :
> > Hello,
> >
> > It may have been a long time without it but still...
> >
> > I ran the doc job on my CI and got this that wasn't working:
> >
> >
> https://ci.inria.f
Le 30/09/2015 18:38, p...@highoctane.be a écrit :
> Hello,
>
> It may have been a long time without it but still...
>
> I ran the doc job on my CI and got this that wasn't working:
>
> https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=30,VERSION=stable,VM=vm/lastSuccessfulBuild/artifact/Pi
Hello,
It may have been a long time without it but still...
I ran the doc job on my CI and got this that wasn't working:
https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=30,VERSION=stable,VM=vm/lastSuccessfulBuild/artifact/Pillar.zip
Hum, yes, but ... why remove the doc tools as this is
23 matches
Mail list logo
