Re: I need help, and I have paypal cash available.
Re: I need help, and I have paypal cash available.
- Subject: Re: I need help, and I have paypal cash available.
- From: David Avendasora <email@hidden>
- Date: Thu, 08 Mar 2012 18:27:23 +0800
On Mar 7, 2012, at 12:24 PM, James Cicenia wrote:
> I am on a mini deadline to show progress so far. Unfortunately, ever since I got wonder source, I have been stopped at every turn pushing to the server.
>
> So... I decided to go the Jenkins route as it seems like a good thing and with a half dozen projects now with various dependencies I thought it would be perfect.
> Plus all the cool kids are using it.
>
> Early this morning I got the job to build and it duly put all the frameworks,both wonder and webobjects in its Jenkins directory. And this is where I lose all sense of what I am supposed to do.
Okay, it sounds like you've got the InstallWOAndWOnder job up and running, but I'm sure it's still set to clone the Project Wonder wonder repository, and not your modifications.
> I have a project that works perfectly on my dev machine via Eclipse/Wolips. This project is not under source control because my client still hasn't setup git on teamforge for me.
You can create a Git repository right on your own computer, then once they get Git setup on a server somewhere for you, you can just create a new "remote" and "push" the repository up. If you don't have SourceTree yet, go get it (it's free) from the App Store (http://itunes.apple.com/us/app/sourcetree-git-hg/id411678673?mt=12) and it gives you a nice, simple UI to 90% of what you need to do with Git.
> I wrote them with urgency to get me git. I think this might be the problem.
>
> Anyway, this project needs the latest Ajax/Protaculous builds for drag and drop etc. So that is my first issue. What do I do with Jenkins? I imported these frameworks from my original git pull of wonder into Eclipse.
>
> This all works. But now what?
It sounds like you haven't created a job to actually build *your* App.
> What triggers Jenkins?
Normally, you'd set up the job to watch your SCM for changes and build whenever it sees new code.
> How does it know anything about eclipse?
It _doesn't_. They are two COMPLETELY different things. They both work with your source code but Jenkins knows nothing of Eclipse/WOLips and Eclipse/WOLips knows nothing about Jenkins! NOTHING!
> Can I set up a job to not use a SCM temporarily? Of course I am learning git at the same time.
Yes. You won't get a lot of the "automated" coolness, but it will build just fine. But FIRST you need a job to build your App.
1) Start here: http://wiki.wocommunity.org/display/WO/Single-Project+Jobs+using+WOJenkins,
2) Modify the job configuration and remove the first SCM task (the one that would normally checkout your code from your repository)
3) Run the job once, it will fail, but it will setup some directories you need
4) Copy your Eclipse project directory into the Jenkins job's workspace/Projects directory (probably /Users/Shared/Jenkins/Home/jobs/YourJob/workspace/Projects)
5) Change the ownership of the directory you just copied in and all it's contents with: sudo chown -R daemon:daemon /Users/Shared/Jenkins/Home/jobs/YourJob/workspace/Projects/MyProject
5) Run the job again.
This should normally work…
> So....
>
> I have a project PI and I am have a ERModern frameworks imported into Eclipse as I need to modify them a bit.
> <Screen Shot 2012-03-06 at 10.17.40 PM.png>
> The three frameworks came from the original wonder git pull. Then I stupidly started messing around with the wolips.properties and PI now can't seem to see all the other frameworks.
No problem, just reset back to the previous commit that was work… oh wait. Umm, yeah. No SCM. Sorry.
> This is really where my confusion reigns. Wolips.properties is obviously still relevant. So do I point those to Jenkins?
Uhg. Oh.. just wow. I don't know where to start. There's so many places that you probably have gone _way_ wrong with what you're describing, and you've left out all the details.
Eclipse/WOLips and therefor the wolips.properties file should know NOTHING of Jenkins. Normally you wouldn't have them on the same machine.
If you want Jenkins to build your modified version of the WOnder source code, you'll have to somehow give that modified source code to Jenkins to build. You could modify the InstallWOAndWOnder job similar to how I outlined above by
1) Remoe the SCM task that clones Wonder and then
2) Copy the changes you made to Wonder into /Users/Shared/Jenkins/Home/jobs/InstallWOAndWonder/workspace/Wonder/
3) sudo chown -R daemon:daemon /Users/Shared/Jenkins/Home/jobs/InstallWOAndWOnder/workspace/
4) Run the job again
That should build _your_ version of WOnder into the WOFrameworksRepository so that when Jenkins builds YourApp, it will use those modified versions of the frameworks.
Good luck James!
I'm living in Borneo right now and it's GMT +8, so I'm sending this off at 6:30 pm and finishing up for the day.
If you still can't get this working, contact me off list and we'll figure something out.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden