Re: Issue 205 in any23: The Plugin Manager tests are failing on Apache Jenkins

[Michele Mostarda <mi...@gmail.com>]

Hi Lewis,

On 30 November 2011 15:54, Lewis John Mcgibbney
<le...@gmail.com>wrote:

> Hi Michele,
>
> Excuse my ignorance, however I'm guessing that when you are referring to
> the {bq}old name{bq} you are referring to Any 23 e.g. space between Any and
> 23? If this is build specific e.g. changing some Jenkins configuration and
> it is trivial then we should simply revert it to the old name. However I'm
> guessing that this might not be the case!
>

The issue was the following:

to perform its usual build operations Jenkins defines a workarea which path
contains the name of the project under building.
The original Any23 Jenkins project was called 'Any23 trunk'.
The issue [1] caused some Any23PluginManager test failures, so to bypass
the issue we renamed the project from 'Any23 trunk'
to 'Any23-trunk'.
Now that the issue [1] has fixed I was figuring out if it would be the case
to return to the original 'Any23 trunk' name.

I will revert the name and check that everything is ok.

The best.

Mic

[1] http://code.google.com/p/**any23/issues/detail?id=205<http://code.google.com/p/any23/issues/detail?id=205>

>
> Can you please expand to comment on the portability issues you briefly
> mentioned? I am interested.
>
> Thank you
>
>
> On Tue, Nov 29, 2011 at 10:21 AM, Michele Mostarda <
> michele.mostarda@gmail.com> wrote:
>
>>
>>
>> On 28 November 2011 10:09, Michele Mostarda <mi...@gmail.com>wrote:
>>
>>>
>>>
>>> On 28 November 2011 01:32, <an...@googlecode.com> wrote:
>>>
>>>>
>>>> Comment #1 on issue 205 by lewis.mc...@gmail.com: The Plugin Manager
>>>> tests are failing on Apache Jenkins
>>>> http://code.google.com/p/**any23/issues/detail?id=205<http://code.google.com/p/any23/issues/detail?id=205>
>>>>
>>>> Hi Michele,
>>>>
>>>> This has now been sorted out right?
>>>>
>>>
>>> Hi Lewis, not yet, ATM we just bypassed the issue.
>>> But is is scheduled with high priority.
>>>
>>
>> Hi Lewis,
>>
>>   the issue preventing the usage of spaces in the Jenkins work-dir has
>> been solved [1].
>> Do you suggest to revert the the Jenkins Any23 project configuration to
>> the old name
>> or just we keep the current one?
>>
>> The best
>>
>> Mic
>>
>> [1] http://code.google.com/p/any23/issues/detail?id=205
>>
>>
>>> Mic
>>>
>>>
>>>> Lewis
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "any23-dev" group.
>>>> To post to this group, send email to any23-dev@googlegroups.com.
>>>> To unsubscribe from this group, send email to any23-dev+unsubscribe@**
>>>> googlegroups.com <an...@googlegroups.com>.
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/any23-dev?hl=en <http://groups.google.com/group/any23-dev?hl=en>.
>>>>
>>>>
>>>
>>>
>>> --
>>> Michele Mostarda
>>> Senior Software Engineer
>>> skype: michele.mostarda
>>> twitter: micmos
>>> mail: me@michelemostarda.com
>>> site : http://www.michelemostarda.com
>>>
>>>
>>
>>
>> --
>> Michele Mostarda
>> Senior Software Engineer
>> skype: michele.mostarda
>> twitter: micmos
>> mail: me@michelemostarda.com
>> site : http://www.michelemostarda.com
>>
>>
>
>
> --
> *Lewis*
>
>


-- 
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com

Re: Issue 205 in any23: The Plugin Manager tests are failing on Apache Jenkins

[Lewis John Mcgibbney <le...@gmail.com>]

Hi Michele,

The original naming was purely random and conformed to no particular
preference. Please feel free to change to anything you would like to build
to be named.

For clarification, from my own experience you will also experience
something similar to this if you try to use some tools with some of the
Solaris/Ubuntu slaves. Sometimes the path *as is written* affects the build
environment and needs some work.

Anyway, hopefully this is now sorted out.

Lewis

On Thu, Dec 1, 2011 at 10:14 AM, Michele Mostarda <
michele.mostarda@gmail.com> wrote:

> Hi Lewis,
>
> On 30 November 2011 15:54, Lewis John Mcgibbney <lewis.mcgibbney@gmail.com
> > wrote:
>
>> Hi Michele,
>>
>> Excuse my ignorance, however I'm guessing that when you are referring to
>> the {bq}old name{bq} you are referring to Any 23 e.g. space between Any and
>> 23? If this is build specific e.g. changing some Jenkins configuration and
>> it is trivial then we should simply revert it to the old name. However I'm
>> guessing that this might not be the case!
>>
>
> The issue was the following:
>
> to perform its usual build operations Jenkins defines a workarea which
> path contains the name of the project under building.
> The original Any23 Jenkins project was called 'Any23 trunk'.
> The issue [1] caused some Any23PluginManager test failures, so to bypass
> the issue we renamed the project from 'Any23 trunk'
> to 'Any23-trunk'.
> Now that the issue [1] has fixed I was figuring out if it would be the
> case to return to the original 'Any23 trunk' name.
>
> I will revert the name and check that everything is ok.
>
> The best.
>
> Mic
>
> [1] http://code.google.com/p/**any23/issues/detail?id=205<http://code.google.com/p/any23/issues/detail?id=205>
>
>>
>> Can you please expand to comment on the portability issues you briefly
>> mentioned? I am interested.
>>
>> Thank you
>>
>>
>> On Tue, Nov 29, 2011 at 10:21 AM, Michele Mostarda <
>> michele.mostarda@gmail.com> wrote:
>>
>>>
>>>
>>> On 28 November 2011 10:09, Michele Mostarda <mi...@gmail.com>wrote:
>>>
>>>>
>>>>
>>>> On 28 November 2011 01:32, <an...@googlecode.com> wrote:
>>>>
>>>>>
>>>>> Comment #1 on issue 205 by lewis.mc...@gmail.com: The Plugin Manager
>>>>> tests are failing on Apache Jenkins
>>>>> http://code.google.com/p/**any23/issues/detail?id=205<http://code.google.com/p/any23/issues/detail?id=205>
>>>>>
>>>>> Hi Michele,
>>>>>
>>>>> This has now been sorted out right?
>>>>>
>>>>
>>>> Hi Lewis, not yet, ATM we just bypassed the issue.
>>>> But is is scheduled with high priority.
>>>>
>>>
>>> Hi Lewis,
>>>
>>>   the issue preventing the usage of spaces in the Jenkins work-dir has
>>> been solved [1].
>>> Do you suggest to revert the the Jenkins Any23 project configuration to
>>> the old name
>>> or just we keep the current one?
>>>
>>> The best
>>>
>>> Mic
>>>
>>> [1] http://code.google.com/p/any23/issues/detail?id=205
>>>
>>>
>>>> Mic
>>>>
>>>>
>>>>> Lewis
>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "any23-dev" group.
>>>>> To post to this group, send email to any23-dev@googlegroups.com.
>>>>> To unsubscribe from this group, send email to any23-dev+unsubscribe@**
>>>>> googlegroups.com <an...@googlegroups.com>.
>>>>> For more options, visit this group at http://groups.google.com/**
>>>>> group/any23-dev?hl=en <http://groups.google.com/group/any23-dev?hl=en>
>>>>> .
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Michele Mostarda
>>>> Senior Software Engineer
>>>> skype: michele.mostarda
>>>> twitter: micmos
>>>> mail: me@michelemostarda.com
>>>> site : http://www.michelemostarda.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Michele Mostarda
>>> Senior Software Engineer
>>> skype: michele.mostarda
>>> twitter: micmos
>>> mail: me@michelemostarda.com
>>> site : http://www.michelemostarda.com
>>>
>>>
>>
>>
>> --
>> *Lewis*
>>
>>
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
>


-- 
*Lewis*