Re: Permissions for Startup Script

Yeah, I agree it's strange. I'm using the Jenkins Git Plugin version 1.1.15. I'm pretty sure it doesn't use a special version of Git. I'm working around the issue by running the two scripts through fromdos before executing them - yeah, I

Re: Permissions for Startup Script

Oh, and I'd love to get some Github pull requests with any improvements. These work for me. I tried to make them general-purpose, but I don't believe that there is any such thing as a "standard" build process with WO. Everyone has some weird stuff that they do. A lot of the stuff that the jobs

Re: Permissions for Startup Script

That is strange. What git plugin are you using, is it using a different version of Git than the command-line does? Dave On Jan 25, 2012, at 10:24 AM, David LeBer wrote: > Weird, > > Doing a manual git clone of WOJenkins gives me good versions of those two > scripts. > > The git clone from

Re: Permissions for Startup Script

Hi David, David, Okay, Okay! You have pulled me out of my hiding in darkest Borneo. Yes, I have some completely updated scripts / job configs for building Git-based projects & frameworks in my Github repository. The job config repositories assume that you will be using the Git for Wonder, but

Re: Permissions for Startup Script

Weird, Doing a manual git clone of WOJenkins gives me good versions of those two scripts. The git clone from within Jenkins results in the weird line ending problem. D -- David LeBer Codeferous Software On 2012-01-24, at 7:38 PM, prob...@macti.ca wrote: > Strange, it's working fine on CentO

Re: Permissions for Startup Script

Strange, it's working fine on CentOS. I will try on a Ubuntu 11 VM that I have. Envoyé de mon iPhone Le 2012-01-24 à 19:35, "David LeBer" a écrit : > More info, > > It looks like the installWebObjects.sh and setupWonderWorkspace.sh scripts > have ^M's in them. > > Not sure how that is happe

Re: Permissions for Startup Script

More info, It looks like the installWebObjects.sh and setupWonderWorkspace.sh scripts have ^M's in them. Not sure how that is happening, the Jenkins box is ubuntu and git doesn't have anything set for autocrlf. D -- David LeBer Codeferous Software On 2012-01-24, at 5:52 PM, David LeBer wrote

Re: Permissions for Startup Script

Thanks Pascal, So, that's important to note, make sure you have the git plugin (had it) and the Mutiple SCM plugin (didn't have it) installed BEFORE you create the job from that config.xml file (otherwise the git checkout stuff will silently get dropped from the job). My current problem: ...

Re: Permissions for Startup Script

I got Wonder to build with this config. Note that you will need the Git and Multiple SCM plugins. config.xml Description: XML document Cool tip: you can create a new Jenkins job with curl: curl -v --user youruser:yourpassword -H "Content-Type: text/xml" -s --data "@config.xml" http://yours

Re: Permissions for Startup Script

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.co

Re: Permissions for Startup Script

Hi David, I believe the newer stuff is on his GitHub account. https://github.com/avendasora David On 2012-01-24, at 10:21 AM, David LeBer wrote: > Does anyone have details on migrating from David's original scripts (that use > SVN) to using git for Wonder? > > D > > -- > David LeBer > Codef

Re: Permissions for Startup Script

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

Re: Permissions for Startup Script

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 R

Re: Permissions for Startup Script

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 > demon

Re: Permissions for Startup Script

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 i

Re: Permissions for Startup Script

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

Re: Permissions for Startup Script

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 softwar

Re: Permissions for Startup Script

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

Re: Permissions for Startup Script

Le 2012-01-24 à 07:51, Gino Pacitti a écrit : > 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 t

Re: Permissions for Startup Script

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 (http://www.sparrowmailapp.com/?sig) On Tuesday, January 24, 2012 at 7:51 AM, Gino Pacitti wrote: > Currently builds from ec

Re: Permissions for Startup Script

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

Re: Permissions for Startup Script

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 >