FYI, look like you need the "Multiple SCM" plugin so that you can clone 
WOJenkins in a subdirectory and have Wonder in another directory.

> I'm trying to figure that out… I have tried with 
> 
>       https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder 
> and 
>       https://github.com/avendasora/WOJenkins
> 
> but I'm lost. It look like WOJenkins_Job_InstallWOAndWOnder has to run first, 
> but a step is missing in it (the step being fetching the WOJenkins repository 
> to have the two shell scripts). 
> 
>> Does anyone have details on migrating from David's original scripts (that 
>> use SVN) to using git for Wonder?
>> 
>> D
>> 
>> --
>> David LeBer
>> Codeferous Software
>> 
>> On 2012-01-24, at 1:06 PM, Pascal Robert wrote:
>> 
>>> Look like I forgot to add a link to this presentation on the Screencasts 
>>> page, but it's in the RSS feed. Anyway, direct link:
>>> 
>>> http://www.wocommunity.org/podcasts/wowodc/east09/WOWODC09E-MultipleVersionsWO.mov
>>> 
>>>> Dave Avendasora made a great presentation (available on the podcast) that 
>>>> demonstrates how to set up Hudson(Now Jenkins) to build wonder and your 
>>>> own apps.  It's titled Practical Builds (WOWODC East 2009).
>>>> 
>>>> Ramsey
>>>> 
>>>> On Jan 24, 2012, at 9:05 AM, Gino Pacitti wrote:
>>>> 
>>>>> Sounds cool... is there more info on the wocommunity site wiki as to 
>>>>> implementation etc...
>>>>> 
>>>>> Gino
>>>>> On 24 Jan 2012, at 16:02, Daniel Beatty wrote:
>>>>> 
>>>>>> Greetings Gino,
>>>>>> The benefits I have found with Hudson and its little brother Jenkins is 
>>>>>> one gets a consistent and automated build and installation system.   Its 
>>>>>> integration into the version control repository be it Subversion, Git, 
>>>>>> or whatever is your pick tends to support a wide variety software 
>>>>>> engineering models.
>>>>>> 
>>>>>> Other qualities I have benefited from is the consistency with things 
>>>>>> like permissions and all of the little things that act like weeds if one 
>>>>>> is trying to build these things from the developer's environment to the 
>>>>>> next.   It also frees up a project from the quirks of individual 
>>>>>> development environments which can vary from person to person and 
>>>>>> project to project.
>>>>>> 
>>>>>> In the end, the benefit list is a list of little things.  If those 
>>>>>> little things matter, then the answer is clear.  For my production 
>>>>>> environment, it does and it makes sense.
>>>>>> 
>>>>>> V/R,
>>>>>> 
>>>>>> 
>>>>>> Dan Beatty, ABD
>>>>>> Ph.D. Student
>>>>>> Texas Tech University
>>>>>> [email protected]
>>>>>> http://web.me.com/danielbeatty/My_Home_Page/Welcome.html
>>>>>> (806)438-6620
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Jan 24, 2012, at 5:04 AM, Gino Pacitti wrote:
>>>>>> 
>>>>>>> Hi Paul
>>>>>>> 
>>>>>>> What are the benefits?
>>>>>>> 
>>>>>>> Gino
>>>>>>> On 24 Jan 2012, at 13:04, Paul Yu wrote:
>>>>>>> 
>>>>>>>> Gino
>>>>>>>> 
>>>>>>>> I would highly recommend setting up a Jenkins build server, even if it 
>>>>>>>> is on your development machine to do your production builds.
>>>>>>>> 
>>>>>>>> -- 
>>>>>>>> Paul Yu
>>>>>>>> Sent with Sparrow
>>>>>>>> 
>>>>>>>> On Tuesday, January 24, 2012 at 7:51 AM, Gino Pacitti wrote:
>>>>>>>> 
>>>>>>>>> Currently builds from eclipse result in the startup script being non
>>>>>>>>> executable unless changed to appserver user...
>>>>>>>>> 
>>>>>>>>> I am moving from xcode to eclipse and just wanted a convenience method
>>>>>>>>> of not having to keep manually changing the owner to appserver and
>>>>>>>>> instead making the startup script the same as I had it on xcode...
>>>>>>>>> 
>>>>>>>>> Gino
>>>>>>>>> On 24 Jan 2012, at 12:47, Pascal Robert wrote:
>>>>>>>>> 
>>>>>>>>>> But why do you need to do that? Execute permissions is already set
>>>>>>>>>> for the owner and the group. I guess you want to give "other"
>>>>>>>>>> execute permissions too? Don't forget that it can be a security
>>>>>>>>>> risk...
>>>>>>>>>> 
>>>>>>>>>>> Hi All
>>>>>>>>>>> 
>>>>>>>>>>> I got some great advice on ANT replacement for a permission
>>>>>>>>>>> variable that was in XCode...
>>>>>>>>>>> 
>>>>>>>>>>> It was:
>>>>>>>>>>> 
>>>>>>>>>>> <chmod file="${dest.dir}/${build.app.name}" perm="ugo+rx"/>
>>>>>>>>>>> 
>>>>>>>>>>> But I am not an expert in where it would go in the build.xml file...
>>>>>>>>>>> 
>>>>>>>>>>> Can anyone point me in the right direction?
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Gino
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>>>>> Webobjects-dev mailing list ([email protected])
>>>>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>>>>>>>>>>> 
>>>>>>>>>>> This email sent to [email protected]
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>>> Webobjects-dev mailing list ([email protected])
>>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com
>>>>>>>>> 
>>>>>>>>> This email sent to [email protected]
>>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/danielbeatty%40mac.com
>>>>>>> 
>>>>>>> This email sent to [email protected]
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/ginokris%40me.com
>>>>>> 
>>>>>> This email sent to [email protected]
>>>>> 
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list      ([email protected])
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
>>>>> 
>>>>> This email sent to [email protected]
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list      ([email protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>>>> 
>>>> This email sent to [email protected]
>>> 
>>> 
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/dleber_wodev%40codeferous.com
>>> 
>>> This email sent to [email protected]
>>> 
>> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to