Dale Henrichs writes:
> On 09/21/2015 10:46 AM, Dale Henrichs wrote:
>>
>>
>> On 09/21/2015 06:31 AM, Damien Cassou wrote:
>>> Yuriy Tymchuk writes:
>>>
Can you simply define symbolic version as a normal one?
>>>
>>> when I tried I got an error message. Metacello was trying to parse
>>> 'd
On 09/21/2015 10:46 AM, Dale Henrichs wrote:
On 09/21/2015 06:31 AM, Damien Cassou wrote:
Yuriy Tymchuk writes:
Can you simply define symbolic version as a normal one?
when I tried I got an error message. Metacello was trying to parse
'development' as a semantic version number
You can i
On 09/21/2015 06:31 AM, Damien Cassou wrote:
Yuriy Tymchuk writes:
Can you simply define symbolic version as a normal one?
when I tried I got an error message. Metacello was trying to parse
'development' as a semantic version number
You can implement #versionNumberClass in your configurati
Yuriy Tymchuk writes:
> Can you simply define symbolic version as a normal one?
when I tried I got an error message. Metacello was trying to parse
'development' as a semantic version number.
> I think that you need a baseline with a code of your symbolic version,
> then you reference this ba
Hi,
Can you simply define symbolic version as a normal one? I think that you need a
baseline with a code of your symbolic version, then you reference this baseline
with the #development version and in v1_0_0 you override repository to
“…pharo-jenkins:v1.0.0/src”. I think that for me that was th
Hi,
I have a BaselineOfJenkins on github and I would like to add a
ConfigurationOfJenkins in the catalog. For the #stable versio, I wrote:
stable: spec
spec for: #common version: '1.0.0'
v1_0_0: spec
spec
for: #'common'
do: [
spec
baseline: 'Jenkins'
wit
